Sage 100

 View Only
  • 1.  Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 10-05-2017 12:49
    Sage100 Std 2017 SU1 user on new windows 10 pc, getting i/o error in SY_Session.pvc . Intermittent - possibly occurs when Sage is open and idle, and/or when changing companies. Does anyone have any specific advice on this one - - Thanks in advance for any help.


  • 2.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 10-05-2017 12:52
      |   view attached
    Hi Jeff. I have the attached article which says profile could be corrupt.

    Attachment(s)



  • 3.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 11-06-2017 10:43
    I don't have much help to offer, but I have a client getting the same intermittent error. Also Win 10, and only since upgrading the OS 3 weeks ago. Also Sage 100 Std 2017 PU1. Tried updating to PU3, but no improvement.


  • 4.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 12-06-2017 06:34
    Hi Kathryn - do you have any updates ? Our client is still having the issue, going onsite Thursday .... thanks


  • 5.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 12-06-2017 06:44
    Tried a bunch of things, but I think the one that stopped the screenshots and call backs was setting the Compatibility on the shortcut to ""Run this program as an administrator


  • 6.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 12-06-2017 06:49
    Thanks - will try that (and other things) tomorrow - fingers crossed.


  • 7.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 12-06-2017 08:00
    Keep us posted, @JeffFiddelman. I'm battling this error on one workstation.


  • 8.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 12-07-2017 07:08
    Slight possibility that my client's issue may have been related to Fixed Assets Options in Sage 100 pointing to the wrong database.


  • 9.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 12-08-2017 05:14
    Hi - we seem to have narrowed it down to mapped drive shortcuts vs. UNC shortcuts - will post results of user testing next week


  • 10.  RE: Sage100 Std 2017 SU1 user on new windows 10 pc, ge

    Posted 12-15-2017 11:09
    Update: We consider this now resolved. All the errors happened using mapped drive shortcuts to 2017 SU1 (on windows 10) - was fine on Windows 7. Switched all users to UNC shortcuts, (and UNC access to GL data for F9) and problems are gone ! (errors happened many times a day for users, and with UNC have not had an error in 3 + days.