Sage 100

I have a client that has been experiencing system lockups almost every day for months. I just took on their account and have been going over the normal stuff with IT (antivirus exclusions, opp locking, bad printers, etc.). They insist that everything has been modified as requested but I'm waiting on proof anyways. They see ""sy_workstation.m4t"" not found on front end, along with some other generic errors, and I see MULTIPLE error 12's (sy_session, sy_service, sy_constant, etc.) A common resolution is to rename the SY_Console and SY_Workstation. What possible reasons besides antivirus could be causing corruption of these files?

what version of Sage ? there are some product updates that fixed an issue with the sy_workstation getting corrupted.

Sorry - I always forget to list that. They are currently on 4.40.10, and we are in the process of an upgrade to 2014. Hopefully the new server and program files will make a difference, but if the issue is environmental, we may still see the problem.

Make sure the server operating system is on the Sage 2014 matrix - this is HUGE. We've had issues running older software on 2012 server and new Sage on older servers.

Thanks. They're on Server 2008 R2, so they're good for that anyways. They also claim that they had a problem switch some time ago, but it has since been replaced with no improvement in the lockups.

After you do the data migration and conversion, rename sy_console and sy_workstation one more time before going live. That way you will have clean files for sure.

They just reported a brand new set of errors to me, which include the infamous ""unlock region failure"". I will need to have IT focus more on the machines and cabling.

oh yes - definitely. Something is breaking the communication between server and workstation - don't let IT try and blame Sage. I always have to argue with them about this error!

One workaround to the corrupted sy_console and sy_workstation is create a batch file that renames these files. Add the batch file to the Windows task scheduler to run at 3am. This doesn't cure the disease but it will treat the symptoms.

I have also seen a network router with a power sukpply going bad cause this. If on Advanced and many users, run as an application on the server instead of a service

Are they MAS 90 as opposed to MAS 200? I've run into this twice in 2 months. They were on 4.50 both times running Server 2008 R2 and with similar errors and eventually Unlock Region Failure. In each case it was the Microsoft Kerberos Ticketing issue and adjusting this setting worked. You have to increase the value for a server registry setting called ""Maximum lifetime for user ticket"". This article tells you a nice way to do it via Start / Run / gpedit.msc (the Group Policy editor). I would change it from default of 10 hours to at least 48 hrs (2 days) or 72 hrs (3 days).

That is fantastic! Thank you! I've dealt with this resolution only once before, a long time ago, but I never would've thought about it now!

Ran into this as well several years ago on an upgrade where the users on Sage 100 Standard were never shutting down their PC (not logging off either) and when they came in the next morning one or more users were getting a sy_workstation not found type error.