Sage 100

Anyone know what could be causing these on a MAS 200 4.40.8 system? I have one user only that is getting kicked out of MAS while in the middle of screens, several times a day. I setup the tracelog file on the MAS server to see if I can find anything and the .110 system is not his computer (I haven't seen his in the tracelog file). He had been kicked out while printing a PO, entering a PO, doing an inventory adjustment transaction. We replaced his network card, turned off all power save options and replaced his network card and patch cable. Windows 7 computer. Here is an excerpt of the Tracelog file from yesterday: ====================== Apr 19 14:59 [*winproc:1120] [TCP][Winsock]Error status:10054 (348:192.168.1.100) Apr 19 14:59 [SY_ERROR:67] Exceeded TCP read error count - Forcing Auto exit Apr 19 14:59 [SY_ERROR:154] Exceeded TCP read error count - Forcing Auto exit Apr 19 14:59 [SY_ERROR:292] Exceeded TCP read error count - Forcing Auto exit Apr 19 14:59 [SY_ERROR:292] Exceeded TCP read error count - Forcing Auto exit Apr 19 14:59 [<noprog>:0] Exceeded TCP read error count - Forcing Auto exit Apr 19 14:59 [<noprog>:0] Exceeded TCP read error count - Forcing Auto exit Apr 19 15:37 [swquery.xeq:1060] [TCP][Winsock]Error status:10035 (348:192.168.1.110) Apr 19 15:38 [swquery.xeq:1060] [TCP][Winsock]Error status:10035 (348:192.168.1.110) Apr 19 15:39 [swquery.xeq:1060] [TCP][Winsock]Error status:10035 (348:192.168.1.110) Apr 19 16:36 [SY_Launcher.pvc:92] Exceeded TCP read error count - Forcing Auto exit Apr 19 16:36 [SY_ERROR:67] Exceeded TCP read error count - Forcing Auto exit Apr 19 16:36 [SY_ERROR:419] Exceeded TCP read error count - Forcing Auto exit Apr 19 16:36 [SY_ERROR:419] Exceeded TCP read error count - Forcing Auto exit Apr 19 16:36 [<noprog>:0] Exceeded TCP read error count - Forcing Auto exit Apr 19 16:36 [<noprog>:0] Exceeded TCP read error count - Forcing Auto exit Apr 19 17:17 [SY_Launcher.pvc:92] Exceeded TCP read error count - Forcing Auto exit Apr 19 17:17 [SY_ERROR:67] Exceeded TCP read error count - Forcing Auto exit Apr 19 17:17 [SY_ERROR:419] Exceeded TCP read error count - Forcing Auto exit Apr 19 17:17 [SY_ERROR:419] Exceeded TCP read error count - Forcing Auto exit Apr 19 17:17 [<noprog>:0] Exceeded TCP read error count - Forcing Auto exit ======================== Any other ideas?

Appears to be an issue with the network. Have you tried to connect the machine at another location that doesn't have any issues. If you move the machine and plug in the network cable that worked for another user and the issue goes away then you might have some interference on the line. Good test would be to move the one that works to the location of the one that doesn't and see if it fails. Could be a Cat5 trying to do Gigabit. If it still errors out then you know that it must be on the OS since you already replaced the card. In that case I would look again at what software is running on the OS that might cause the issue. Could be Antivirus, virus, Monitoring software, firewall, etc.

If it is network hardware related, it could be the wall jack, or the port in the switch that jack is connected to. Do any of those times correspond to the exact time he was kicked out?

Thanks for the information guys. I am going to check out your recommendations. The times in the tracelog did not correspond with the times the user was kick out though. I also did remove an offline printer that the user had just in case that would kick them from MAS.

I had a 4.4 client with this issue. As soon as they disabled automatic logoff in user maintenance, it stopped. I know Sage was aware auto logoff did not work correctly, but don't know if it got fixed.

Thanks Debbie, I did check that and we don't have that enabled on their system.

Had one like this recently. Was happening on MAS 200 4.40 PU6 on brand new Windows 7 64-bit wkstn during Cash Receipts Entry and/or when printing Cash Receipts Journal. For them, solution was to turn down the DEP setting: Control Panel / System / Advanced System Settings / Advanced tab / Settings button / Data Execution Prevention tab - Make sure workstation is rebooted after the change. Here is a screenshot.

Thanks Alnoor. We are going to try that too. It is still happening on the users workstation even though they changed every network connection on the user's workstation...new nic card, new patch cables, new port on switch. We also disabled all power save options on the computer.