x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 16 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 6648 views
  • Users 0 members are here
Browse Forums
Announcements
292
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
43
topics
90
replies
Payroll, Time Tracking, and Job Cost
775
topics
1k
replies
Reporting and Analytics
960
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
Freddie.

SAGE100: the PDF document was not created successfully

SUGGESTED
Posted By

Hello,

We have SAGE100 installed on a server. Last week we lost power for 3 hours and after that whenever someone is trying to save a pdf from remittance I keep getting this message and the process fails: "the PDF document was not created successfully"

I googled the issue and I applied the following patches but none of them worked:

1. Re-install PDF Converter

2. Make sure the user accessing sage100 has permissions in register and folder wise (full control access)

3. Making sure PDF Converter driver is using the right driver.

I really do not know how to fix it. Any help is much appreciated

  • 0
    SUGGESTED

    From the Knowledge Base:

    Description

    Error: "The PDF document was not created successfully" when trying to save a PDF document using Paperless Office for Sage 100



    Resolution
    • Verify that the "Use Lockfile" checkbox is selected in Paperless Office Advanced Options for each company code
      1. From the Sage 100 Desktop, open File,
      2. Select Run
      3. For Program, enter PL_AdvancedOptions_UI
      4. Click OK to open the Paperless Office Advanced Options task window
      5. Make sure the "Use LockFile" checkbox is selected (checked)
      6. Click Accept
    • Check the PDF Directory path and permissions
      1. Open Paperless Office, Setup menu,
      2. Select Journal and Register Maintenance, Report Maintenance, or Form Maintenance, etc. (depending on whether it is a journal/register, report, or form)
      3. Click the Entries (flashlight icon) button to see the list of existing entries already made (e.g. Journal and Register Entries, Report Entries, or Form Entries button)
      4. Select the most appropriate existing entry that covers the journal, register, report, or form where the error occurs, by company, module, and/or document
      5. Copy the PDF Directory path
      6. Open the path in File Explorer or Windows Explorer
      7. Verify that any existing PDF documents can be opened and displayed
        • Note: The path should be a UNC path. One of the most common reasons fo the error message is due to time-out when the storage location is on a separate server from the Sage 100 server. So try to make sure the UNC path is to a storage location on the same server as the Sage 100 host.
      8. If there are any 0 KB sized PDF documents, delete them from the list.
      9. Test to see if the user is able to create a new file (such as a new text document) in the directory and delete that new file.
        • Note: If the user is not able to do so ("Access is denied", etc.) there is a Windows security/permissions issue that needs to be resolved by the network administrator.
    • Restart the Print Spooler
      1. Access the Windows Control Panel, Administrative Tools, Services
      2. Find the Print Spooler service
      3. Stop the Print Spooler service
      4. Start the Print Spooler service
  • 0

    How do you try to troubleshoot this message when it works one day, then does not work the next day on the same computer, with the same user, within the same company, with the same document?

  • 0 in reply to Roslyn

    Look for anything that changes (new software installed, Windows Updates, updated network permissions...). 

    We've seen that with a mapped drive (using alternate credentials) going to "sleep", where the user intermittently loses permission to a network path.

  • 0 in reply to Kevin M

    I forgot to mention that this is only one company out of 200+.  All others work fine and have not had any intermittent issues.  

  • 0 in reply to Roslyn

    The Paperless path could be different for that company (eg. mapped drive vs UNC... or to a different share / folder with different permissions).

  • 0 in reply to Kevin M

    They are all the same, with security granted at the top level. 

  • 0 in reply to Kevin M

    Thanks.  We have tried everything that is documented on any of the Sage sites or elsewhere.  Definitely falls in the category of "Things that make you go hmmmm......."

  • 0 in reply to Roslyn

    if it only happens in 1 company, the most common reasons would be this company has "Use  Lockfile" selected or un-selected different than others (this setting is per company) or as mentioned elsewhere here the path is different for those type of documents and that company than for others and that individual PDF Location is having an issue being accessible at the moment the error occurs.  For the Lockfile setting you can use Datafile Display and Maintenance to check the SY_Company file in MAS_SYSTEM folder and compare the value for UsePDFLockFile$ (typically field 51) for the different companies.  You can run File, PL_AdvancedOptions_ui and select the Lockfile to match other companies.

    One other option is a Amyuni Document Converter 600 driver conflict (due to Windows updates or other software installed that uses that driver) which makes the version conflict with Sage 100 and these can be intermittent errors - but not typically linked to one company unless that company just happens to have more printing/Paperless activity than others.  See Knowledgebase articles 103205 Paperless Office Printing prompts manually for PDF Location after Windows Updates installed (and a variety of other errors and situations) and the related article # 111219  Download Amyuni Driver Update for Sage 100 2019, 2020, and 2021.

  • 0 in reply to DGR

    Thanks DGR.  All of those options have been tried as well.  I also spent 1-1/2 hours on the phone with Sage Support yesterday and still no resolution other than running it in MAS90 mode which is definitely not a long term solution.

*Community Hub is the new name for Sage City