Sage 100

 View Only
  • 1.  Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 08:21
      |   view attached
    Upgrade to Sage 2013 and receiving an Error:200 Line 621 on one workstation. It's a Windows 7 workstation. I've removed and reinstalled workstation setup and still same error. There are some posts regarding this error with a different line number, tried those fixes and still nothing. The error appears on all reports and 2013 is on SP3. Any ideas?


  • 2.  RE: Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 08:30
    I've seen similar errors that went away once the workstation UAC was turned off and the workstation re-installed - have you tried that?


  • 3.  RE: Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 08:32
    Yes, the dreaded UAC. I've done that twice now just to be sure it was off. That seems to be about 95% of the workstation install issues and thought I had it after that, but still the same error.


  • 4.  RE: Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 08:35
    Is this Standard, Advanced or Premium? I've been having a whole bunch of issues with the Sy_Report* files on premium, I keep having to zero-out the page settings from SY_reportsettings. Those errors also referenced SY_reportcommon.pvc... Might be worth trying.


  • 5.  RE: Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 08:36
    Standard, but I will take a look.


  • 6.  RE: Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 08:48
    Is error specific to user ID? Can you log in (to network and MAS) as someone else and try it?


  • 7.  RE: Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 09:13
    @MarkKotyla - Yes, it is user specific. I was able to just get into the pc and tested as another network user and did not receive the error.


  • 8.  RE: Upgrade to Sage 2013 and receiving an Error:200 Li

    Posted 08-19-2013 09:27
    @MarkKotyla - That was the key to find the issue. Changed permissions on the ..x86/Business Objects folder and it took care of the problem. When I tested as Administrator it worked fine, but the local user did not have the proper permissions on that folder for some reason. Thanks for the help everyone.