Sage 100

Sage100 Standard version 2013 one user is getting input/output error referencing SY_Session.m4t 9sorry, I did not get the exact error message from him) This is only happening to one user, all other users are ok, He can log in, do one action for instance he can go in and enter a purchase order print it through quick print, then if closed PO entry and immediately tries to open Purchase order entry again or any other task the error pops up, he then reboots his computer, logs into Sage and does one task . then, on the next task the error pops up again. we renamed SY_workstation and SY_Console I think we are going to send this to IT dept. but if anyone has seen this and has any ideas, let me know.

Is he on Windows 10?

I did not take the call -I asked my cohort and he was not logged in but the user said the machine was brand new. So if that is important please let me know.

I had a client that received a similar error on several Windows 10 machines. We were never able to determine if the cause was Windows 10 or not, but eventually they started logging on to Sage 100 via a remote desktop connection. In my case the error was followed by an ""unlock region failure"" error.

ok I got confirmation that they are not on windows 10 - they are on windows 8 and they upgraded to 2015 so it is a supported platform.

I would un-install and re-install the workstation, run any executable as administrator and make sure the sage workstation icon to launch MAS90 is set to run as administrator. See if that helps

Agree with @JimSteele - WIN 8 machines are funky. Chances are the UAC was not turned off, the installation was not run as an administrator or some other weird step was overlooked. What PU is v2015 on?

Thanks all! that is what we will do. he has left for the day.

@DavidOverholt, did you ever identify the root cause of this issue? I'm seeing the exact same thing at one of my clients. Sage 100 Standard v2014. Three new workstations, but only affecting 1 user. Intermittent input/output error with SY_Session.

no, we did not, IT looked at the NIC card and hub and reported no issues and the error quit apparently on it's own or the IT is not telling us everything.