Sage 100

 View Only
  • 1.  Sage 100 2017c Adv - Two weeks ago, everything was

    Posted 09-06-2017 20:00
    Sage 100 2017c Adv - Two weeks ago, everything was working, now when trying to go live, I am getting this unable to print message. Found a KB for it, but it is not resolving the problem. I uninstalled the CS ODBC service to no avail. My next thought is that the workstation client is on the fritz. Has anyone run into this issue before? Issue occurs for all Crystal reports. AS I said, two weeks ago, it was working fine.

    Attachment(s)



  • 2.  RE: Sage 100 2017c Adv - Two weeks ago, everything was

    Posted 09-06-2017 20:12
    Is the data path correct? Had an issue recently after an upgrade and the previous services had been re-enabled and turned on. With these turned off, reinstalling CS ODBC, and placing the UNC in the data paths, they are still working.


  • 3.  RE: Sage 100 2017c Adv - Two weeks ago, everything was

    Posted 09-06-2017 20:13
    The upgrade was to Sage 100 Advanced 2017


  • 4.  RE: Sage 100 2017c Adv - Two weeks ago, everything was

    Posted 09-06-2017 20:21
    I have stared at the data path several times and it appears correct in the company maintenance field.


  • 5.  RE: Sage 100 2017c Adv - Two weeks ago, everything was

    Posted 09-07-2017 04:02
    Does the user have ""Use C/S ODBC"" enabled yet the service is not running? I've had that happen and it produces ""goofy"" results which were similar (but not the same) as what you posted.


  • 6.  RE: Sage 100 2017c Adv - Two weeks ago, everything was

    Posted 09-07-2017 09:32
    I tried every possible combination. Not having the service running and running the CS ODBC enabled would cause havoc. After eliminating most of the usual suspects, I became convinced that it was a workstation install issue. Problem is that I could not test as I did not true admin rights on the server to uninstall the workstation. Earlier yesterday, the owner confirmed that all workstations were installed and that they could generate a crystal report. So I had to abort the go live (yet again). This AM, we connected so I could uninstall the client, reinstall and reboot the server. Life is back to normal and we have to schedule the go live for another day. So as it turned out, we could have pulled the trigger. Hindsight is always 20/20.