Hey Justin - There are a bunch of reasons for that "Unable to initialize PDF Converter" but if you get it to the point where it only continues to happen thru BOI / DCOM, then it could be you need to copy the [Paperless] section of \Launcher\Sota.ini to Home\Pvx.ini. At least that's been true for me.

Thanks for the input Alnoor.  Let me give it a shot.  EDIT - worked great, thanks!

Kent,

You nailed it.   The Sy_ReportSetting.m4t table did not have a machine entry for the Server the script was running.  It was using the redirect printer from my rdp session. 

I logged in directly on the console ran the Sage process thru GUI to get an entry inserted into the Sy_ReportSetting table for the machine settings. The script now runs thru the scheduler while not logged in. 

Perfect, thanks!!

Kent,
It there a switch to pass to Sage’s smtp (mail) server when it encounters an error while nProcessReport("PRINT") is sending out AR Statements (electronically in background), such as the checkbox to ignore all errors?    Occasionally an error will occur, usually a smtp timeout. The process of sending out statements (waits on the response) to smtp dialog that is background.    Any thoughts or other parameters to pass to the email engine?          Thanks, Mike

Greetings,

There is no parameter or setting that can be passed to the Sage 100 email engine to ignore errors.  Is it possible for you to increase the timeout on the mail server to see if that helps?

Thanks,

Kent

I wished we could as it is Sage's smtp (mail) server that only waits for 30 seconds.  My understanding is the timeout is hard coded to 30 seconds in Sage.  Please tell me different.      Thanks, Mike  

Continuing on with this - Is anyone aware of the correct BOI procedure to update a subledger register, then immediately update the resulting daily transaction register?  Ideally I would like to post the DTR for just the subledger batch I'm posting, but if I need to post everything that's sitting in the DTR, that would be fine.

Right now, with the same session object, I'm running the SO Sales Journal's nUpdate() method, which is updating nicely, but if I attempt to create a GL_DailyTransaction_upd object and run nProcessReport/nUpdate, I'm getting 'File is empty'.  

Any help would be appreciated!

Are you allowing for adequate processing time before trying to print the DTR?  It can take a while for the GL_DailyPosting data to be finalized.

I tried waiting up to 30 seconds after posting a 1 invoice SO batch, but get the same thing.  I even tried destroying/recreating my session object before attempting to run the DTR ,but same result.  :(

Before attempting to print the DTR, execute this method of the DTR object:  SetUpdateRegister() with an argument of Source Journal + Journal Number.  Source Journal is a two character value and the Journal Number is a six character zero filled value, example:  SO000100.  This method is used in the update programs when chaining to the DTR.