Upgrade to Windows 10 and Office 2016 Resulting in Error Message

SOLVED

We're using Sage 100 2015 Standard, and we're attempting to upgrade from Windows 7 and Office 2010 to Windows 10 (version 1803 specifically) and Office 2016 but testing is revealing an issue in which if Sage 100 has been left open and inactive for a period of time, the next time we try to open a task (any task at all) we get the following error message:

Input/output error

Program: SY_SESSION.PVC

Statement: 6950

Class: SY_Session

Method: SetLastActivityTime

Sage 100 then will not respond and we have to end the process using the Task Manager. The knowledge base gave me the idea that it might be a printer port issue, and indeed I found that a new Office 2016 printer, "Send To OneNote 16", shares the "nul:" port with the Sage 100 PDF Converter printer. Therefore I changed the port for the Sage 100 PDF Converter printer to a different one (I made a new Local port named Sage), but unfortunately this actually had no effect on the problem, so that's not it. Anyone else experiencing this issue by any chance?

  • 0

    Just as an update, I also tried removing the "Send to OneNote 16" printer and turning User Account Control off, but neither of these made any difference. The only thing that appears to have made a difference is using the Run as administrator option when starting Sage 100; when I do that I don't appear to get the error. However, having everyone run Sage 100 as an administrator is not a feasible option for us.

    This thread from two years ago is reporting the same issue:

    sagecity.na.sage.com/.../sage-100-2015-pu1-crashes-on-windows-10-pro---need-help

    But nobody ever replied with a solution :(

  • +1 in reply to dkantola
    verified answer

    Check that your network card is not set to go to sleep after a period of inactivity.

  • 0 in reply to Kevin M

    Sorry it took me so long to get back to this thread! I tried your suggestion by unchecking the "Allow the computer to turn off this device to save power" Windows setting and, even though it doesn't make any sense to me, it actually appears to have fixed it! Strangely enough though, even after then re-checking the setting the problem remains fixed. In the time since I originally posted this we've deployed several other computers with Windows 10 and have not encountered this particular issue again, so I don't know why this was the case for this computer but in any case thank you again for your help.