Sage 100

Error 11 record is missing from SY_Workstation MAS 90 Version 4.3.24. We are now getting this error 3 or more times a week. I rename the SY_Workstation and all is well until the next time. The first computer to experience this each time appears, by looking at the activity log, to be the same computer - Windows 7. We have run the second WKsetup and installed the LM_4046 patch. It's getting to be a real pain to get everyone out of MAS and rename the SY_Workstation file several times per day. Does anyone have any idea what could be causing this?

Are you also renaming the sy_console file? If you are and that still isn't resolving the issue, and it seems to always start with the same user, I would setup a new user ID for them and see if that resolves it. I have had instances in 4.x with a user id becoming corrupt. Also, have you looked at their system event log to see if that provides any clue?

Harold Have you tried also renaming SY_Console.M4T? sometime corruption in that file will lead to the same error. You need all users out for this also. as a side note: if you are using MAS200 I don't think this file is automatically re-created. but with MAS90 it is re-created when the first user logs in. so, to be safe, be sure to rename it rather than delete

WAG -- I had similar weird workstation related issues at one customer who had recently upgraded to Windows 7. Turned out they never logged out of MAS90 and at some point that workstation would lose connection and throw a similar cryptic error. The IT guy all but threw us under the bus -- so we had to take ownership of their problem. Eventually the solution was for everyone to log out of their workstation at night (they were small and left all their workstations on and logged in). This made the problem completely disappear. Just an FYI

I agree with Wayne - My guess is that a user is loosing connectivity to the network. I would see if any of the users are reporting problems with their particular computer

@ Wayne - AH yes, the infamous ""Kerberos Ticketing"" issue, We chased our tails on that one at a client for several weeks. @Harold - if you determine that this user is either A) not logging out at night, or B) he is logged into MAS90 for long periods of time (typically more than 10 hours at a time) it could be due to Windows 2008 and Kerberos Ticketing. In either case you may want to check the link below it has several articles on Sy_workstation issues. http://community.sagemas.com/t5/forums/searchpage/tab/message?location=Board%3ATech_Install&q=kerberos#message-list

Thank you all for your help. We will try each suggestion, one at a time, to see what works in this case and then update this post.

Thank you for the posts.

Ironically, I just received a call from a client today with the same issue. They are on 4.3.2 and are having to rename their sy_workstation file 2-3 times a day. I will try some of the above suggestions as well and look forward to hearing if @haroldwestover has any luck with these as well

@haroldwestover and @JenniferChriston, were you able to determine the resolution for your situations?

@BrettZimmerman -I had the client rename the sy_console.m4t as well as the sy_workstation.m4t and that seemed to do the trick. Before they were only renaming the sy_worksation. I also discovered that not all of their users were logging out when they went through this process. I'm sure that contributed to the issue as well.