Sage PDF Converter failure

   I'm not sure if I'm putting this in the right section or not, so please advise me if I should be asking this elsewhere. We are running MAS 200 version 4.3 and are employing Paperless Office for the first time. All of our Sales Order users Print/PDF their invoices at the end of the day and all has been going well except for one user/PC. When this user prints her batch, the paper copies come out on the printer but she receives a Windows message stating that the document failed to print to the device "Sage PDF Converter". A check of the paperless office viewer confirms that no PDF's were created. When I re-run the batch on my PC, documents and PDF's are both created fine.

 

   There are no indications of a problem in either the MAS Activity log or the Windows Event Viewer. I ran RegCom.bat,and when that produced no discernible results I uninstalled and reinstalled the client on that PC. Still, the problem remains. I am unsure of where to go from here. Any ideas?

  • Is the printer that's selected an actual Windows Printer?

     

    Dawn

  • Jim, look to see if the Sage PDF Converter is actually installed on the work station in question. Since it is just one user/PC I would look at the printer setp of the one PC.  That is where the issues is.
  • Dawn,

     

    The printer used in the multi-part section of that form is a network printer. The default printer for that PC, however, is a printer connected to that PC that the server does not recognize. I tried making the default printer the same as the network printer, but I was still coming up with the same error.

     

    BigLouie,

     

    The Sage PDF converter is installed on this workstation as far as I know. When I receive the "failure to print" message, I go into Printers and Faxes on that PC and open up the Sage PDF converter device. There is a document sitting there (first invoice in the batch) with a status of "Error", but no explanation of what might be causing this.

  • Jim,

     

    I think you're on to something, because when I run Test Converter on that workstation I get a ProvideX - Printer Allocation Unable to Start Document message. When I OK out of that I get 'SY_System' not found. I have verified that Acrobat Reader is installed on this workstation and PDF's are associated with it. Since it was version 7, I upgraded to version 9 and re-ran the test, but I'm still getting the above error messages.

     

    I also verified that CDINTF.DLL was on the system (it's located in the ..MAS90\Home directory on our installs), but I replaced it with a copy from the server anyway. I registered it and tried again, but still no luck.

  • Jim you may have an issue similar to what I had with one of our work stations. Here is the fix I had to use.

     

    1.      Go into the Control Panel

    2.      Go into the Printer/Faxes folder.

    3.      Delete ALL printers or faxes present.

    4.      Open regedit (e.g. click Start, Run, regedit and press Enter)

    5.      Backup the Registry.

    6.      Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers

    7.      Under this key, there will be the keys Version-2 and Version-3 (one or the other of these may be absent - not a problem). The sub-keys under these contain the printer driver configuration information. Delete all the sub-keys inside Version-2 and Version-3, but not these keys themselves.

    8.      Close the Registry.

    9.      Open Windows Explorer

    10.  Navigate to %systemroot%\system32\spool\drivers\w32x86

    11.  Inside w32x86, there will be folders with the names 2 and 3 (one or more of these may be absent - not a problem). Delete all of the files and sub-folders in each of the 2 and 3 folders, but not the folders themselves.   Inside w32x86, there may be other folders with names starting with "hewlett_packard", "hphp" or something else; delete these folders also.

    12.  Start MAS

    13.  Go to File,Run and type in PL_AdvanceOptions_Ui.

    14.  Click OK

    15.  Install converter. Note that before step 9 you might want to open a command prompt window and stop the print spooler with “net stop spooler” and then start it after step 11 with “net start spooler” at the command prompt. Note that you would have to re-install all printers. We have a network script that installs printers so all the user had to do was reboot his work station.

     

  • Jim your issue is that there are conflicts with old or installed printer drivers that are just about impossible to track down. Based on research on the users forumn for the PDF converter that Sage uses and some postings on Tek-Tips I was able to develop this step-by-step. It worked fine for me.
  • BigLouie,

     

    I appreciate your extensive and explicit instructions. I'm still getting the "SY_System" not found message after all that,however, so I'm not sure what to do other than reformatting the whole machine. Thanks anyway.

  • bfocht_1,

     

    I tried this and, while it did install the converter without error, I'm still getting the "Unable to start document" message (as above) when I test the converter. Thanks for trying!

  • bfocht_1 The company that created the PDF converter that Sage uses has a known issue with the DLLs. The work around I posted was based on postings from their web page and knowledge base. In certain cases there is no other option but to delete everything concerning printers and totally re-install.
  • Just curious, but what is the workstations operating system?  We ran across this with one client and in troubleshooting found that unbeknownst to us, they had installed a Vista Ultimate 64 bit machine.  PDF converter WON"T work on 64 bit although MAS did run.