Sage 100

Last week, I moved MAS 90 (v4.4.7) from a 2003 Small Business Server to a 2008 Standard server. Both servers are still active. Straight copy, changed the mappings on the icon to point to new destination. Now one user is experiencing major issues (WIN 7 64 OS WS) each afternoon about the same time. It starts blowing all sorts of errors (of course this morning when I logged on, he had about 15 MAS panels open). Error 12 (file not found) with an assortment of tables (sy_user, sy_session, etc). I've searched the KB and community but don't see anything but I know there were some issues with the WIN 2008 timing out if the workstation was left on for more that 24 hours. Can someone post the buzzwords and or links? Of course IT tech is clueless. We adjusted some AV settings to exclude extensions on new drive but that isn't solving the problem.

search on Kerberos Ticketing - if you cant find it I have the links somewhere I can round them up and post them

Please post I am experiencing similar issue....

here are 3 that I have from research I did while trouble shooting at a client - 18 hours seems to be the timeout setting that worked for our client. http://community.sagemas.com/t5/Technical-and-Installation/MAS90-or-MAS-200-Errors-hangs-or-Freezes/m-p/59320#M7773 http://community.sagemas.com/t5/Technical-and-Installation/SY-Workstation-M4T-not-found/m-p/33288#M5223 http://community.sagemas.com/t5/Technical-and-Installation/MAS-90-crashing-with-Sy-Workstation-m4t-not-found/m-p/45316

Jeff, Have you looked at Opportunistic Locking which seems to be an issue with 2008 server.

The symptom that I saw would occur on a customer account roughly the same time each day - when they came in during the morning. They were leaving their computer workstations on overnight and never logging out. Once they started to log out when they left the issue disappeared totally. IT tried to crucify us by swearing it was a MAS90 flaw

Haven't looked at the opportunistic locking yet. Will wait and see with the Kerberos setting works. Is Logging out of MAS the key or is rebooting the WS the trigger for resetting the timer? is it just me now doing the search properly or is there no reference to Kerberos on the KB?

I had something very similar with opportunistic locking - I would definitely check into that: http://www.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=408851

Opportnistic Locking - Alnoor and I go way back on that one. Upgraded a client to v3.71 the same week they started running WIN 2003. Life was a living hell for abut five months until Sage Tech Support figured that one out. And that was when they had giants like Alnoor on the team!!!!!!!

I haven't been able to find any reference to Kerberos on the KB either. Howver, I 'm working with a client who upgraded to mas 200 4.4 recently and are on a windows server 2008/ windows 7 workstations who is experiencing random freezing and timeouts, but always in the afternoon. I'm looking into opportunisitc locking/kerberos now but would be curious to know if you had had any luck Jeff?

Client reported no issues this PM when the system normally tanked. I would suggest either rebooting the workstation mid day or at least exiting out of MAS once or twice a day. If the issue doesn't manifest itself then you've pinpointed it. The opportunistic locking is a bit more difficult to troubleshoot, but it appears that it is one of these two items.

Starting to be the server change from hell. The IT guy doesn't listen - Please change the setting to 18. Ok, I'll change it....... to 14 but I don't know why as the MSFT article indicates that it is for the domain server and the 2003 is the domain.server. Please reboot the workstation. Oh, I just fooled by changing the IP address of the workstation so I didn't reboot. Sigh, guess I'll open a case with Sage on Monday and let them figure out why things aren't working.........

Do they ever listen?

Even our internal network team had struggles with this; and IT people in general seem to instist that it is a problem with MAS90 (apparenlty based on the fact that no other programs have this issue). Well maybe it is and maybe it isn't. But setting the kerberos to a higher time frame seems to fix the problem so I say ""just do it please"" I should mention that the server 2008 has 2 Kerberos settings - one for applications and another for services. during at least one of our struggles we found that we had to change both settings.

Had an IT guy for an end user call me to ask if I was code savy enough to fix whatever file locking problems were causing these issues since he was certain it was not the network. Talk about horror show --- you go into a relationship such as described already having declared that MAS90 is the culprit with no ability to diagnose. I'm sure some other Sage partner will ""luck out""... Also he used ""company is a small business"" three or four times which is code for ""they won't pay for value"" --- and naturally were on 3.71

I'm still having the same issue with a client on 4.4 who moved to 2008 server. We gone through every scenario with their IT that I can think of - still no luck. I have recommended changing their settings to 18 as well, but their IT persion is conviced that's not it. I'll continue to try things, but would love to hear what others come up with....

Jennifer - ""I have recommended changing their settings to 18 as well, but their IT persion is conviced that's not it"" - does this mean they won't even try it? I went down the road of ""I'm sure that can't be it!"".for weeks. Ask them to try it for a few days and see what happens.. What is the harm? They will tell you it is over-riding security in 2008 that keeps hackers out, that may be true but at least give it a try. Make sure they change both settings.

@DavidOverholt - Both settings? What is the second one? Opportunistic locking? The issue that is hanging the IT guy is that the kerberos setting is for WIN 2008 when it is the domain server. In my case, the 2003 server is still th domain server. Any thoughts on the impact here?

I was referring to an earlier post - I'm not an IT guy, but in one case the IT staff informed me that there are 2 Kerberos settings on a 2008 server, one that sets the ticket timeout for applications and another one that sets the ticket timeout for services. even though MAS90 is an application they had to change both settings to timeout at 18 hours to solve the issue. I don't know how 2003 being the domain server would affect that, however what is the harm in trying these settings anyway.

My client's IT person requested instructions for changing ticket times/settings. I'm not an IT person either and don't feel comfortable just guessing. Is there a good Microsoft KB out there, or trusted instructions?

I'll e-mail our internal IT staff and see what I can find for you - they researched it at length, so I'm guessing they can point us to something.

After the client's IT guy finally changed the settings to 18 hours, we haven't had any issues. AMAZINGLY, there is very little in the Sage KB on this topic. One of the issues with my client was that the 2003 server was the domain and the Kerberos issues were always on the 2008 server. So of course, the IT guy didn't think that was the issue. So when he didn't have any ideas to fix the problem, he made the change, rebooted the servers (both of them) as well as all the workstations.

here are 2 links my IT staff provided - http://technet.microsoft.com/en-us/library/cc961966.aspx http://technet.microsoft.com/en-us/library/dd277401.aspx

@JeffSchwenk - Is your screen shot showing the settings before they were changed? I appreciate the info, I'm hoping this will resolve my client's issue as well.

Thanks David - that is much appreciated!

no prioblem, and Thanks @Jeff Schwenk for the visual! It shows the two settings that I was trying to describe in an earlier post; it even helped me (an IT Dummy) understand it better.

Regarding the settings, I asked the IT guy to change the setting to 18 hours. He only changed it to 14 the first time and didn't touch the service ticket setting. I then requested that he change BOTH settings to 18. Client is now happier. Pictures are very helpful when troubleshooting.

Just an update - despite extreme doubt from the IT guy, he finally changed the settings to 18 hours and and have not reported any issues happening this week. Thanks for all the help with this - I'm definitley making a note of this for the future.

Just love the IT folks. If it isn't an OBVIOUS fix, then it CAN't be the solution! Still waiting on my IT ""guru"" to send me an e-mail to express his amazement over my ability to fix HIS problem.................................. Bazinga! That was sarcasm.......