Sage 100

 View Only
  • 1.  A customer is working in a totally remote server e

    Posted 01-25-2018 13:02
    A customer is working in a totally remote server environment on Amazon servers. They are on Sage 100 2016 Advanced. They have had intermittent difficulties with generating PDF files in Paperless Office. The problem appears totally random and I have fought the issue for a while. I have combed through a half dozen or so Knowledgebase articles and while we think the problem is gone, it eventually pops back up. here are the typical errors. They received these on Tuesday morning: Unable to process the Lockfile. ""Crystal Reports - Invoice Printing"" The PDF document was not created successfully: ABC_SO_DailySalesReports_bMultiple_SO-019630_000.PDF Printer not activated, error code -30 I have done things like make sure that all users have full rights for the Sage directories and changed the Registry entries so that all users have full rights. The last thing that I tried on Tuesday was to alter the properties for the program so that it always runs as Administrator. As of this afternoon, no one has had the problem pop back up. I hope that this solves the issue. If anyone else has any bright ideas I would be more than happy to entertain a conversation.


  • 2.  RE: A customer is working in a totally remote server e

    Posted 01-25-2018 13:24
    Windows 10? If yes, try KB ID:68571


  • 3.  RE: A customer is working in a totally remote server e

    Posted 01-25-2018 13:44
    Windows Server 2008 R2 Datacenter. KB ID: 68571 is where I found the ""Run As Administrator"" trick. I applied that on Tuesday and no problems so far. We're keeping our fingers crossed!


  • 4.  RE: A customer is working in a totally remote server e

    Posted 01-25-2018 14:11
    I'm sure you've tried this. Last week I resolved a similar issue by uninstalling, then reinstalling the drivers. I also changed the port from null to the local Sage port which I created.


  • 5.  RE: A customer is working in a totally remote server e

    Posted 01-25-2018 15:20
    Registry key permissions to full, then running the workstation install to repair (as admin), then run the workstation as admin the first time. This usually works for me...