Sage 100

Has anyone run into this issue? - started with upgrade to 4.50.2. System displays File ""\\server\path\MAS_SYSTEM\SY_LockFiles.M4T"" not found. This is followed by ""Potential hardware failure"" Only remedy is to close the entire MAS system and all users reboot. This has happened 4 times in the last 2 weeks.

Sounds somewhat like this issue I had a while back: Technical second opinion wanted -- have a client who sporadically (once or twice a day) is receiving messages about files not being found -- usually SY_Workstation but it can be others (see attached PDF). I've logged in to rename the SY_Workstation and attempted to have their IT staff exclude the typical MAS data files from scanning (they're running Symantec Endpoint and some Malware scanning). The IT staff have basically thrown me under the bus -- and when I've crawled out they kick me in the teeth and give another push to make sure the wheels of the bus hit me again. Am I missing something on my preliminary diagnosis? All I've asked is for the IT staff to exclude the MAS folder from scanning for both AV and Malware. To which they claim they've done so and proceed to broadcast email everyone in the company that this is absolutely a MAS 90 problem -- there's no doubt in their mind.

This may have been related - it's one of the links I stumbled upon while researching the issue: http://community.sagemas.com/t5/Technical-and-Installation/Mas90-crashing-regularly-for-our-staff-Sy-workstation-M4T-not/m-p/10595

Here's what the resolution in this case was: Client was never logging out of network. One of the issues that seemed somewhat related to this was on the Community Forum and mentioned that the workstation may request a renewed connection every x hours. So far the client reports that by logging out of the system at the end of the day has reduced (or stopped) the random lock ups. I'm not sure why we would have only been locking on one file -- and during multiple times of the day. I'll continue to keep an eye on this

Here's a PDF of the error message in case this helps

What OS is the server? These issues sound like they may be related to the Kerberos ticket settings related to WIN 2008. Lots of posts on the topic.