10101 - System Could not open output file

PDFCreator
1

Hello,
I have inherited an application when a developer quit. There is not documentation nor a QA environment set up. We are working hard to get something working in QA. Their hasn't been any code releases but in the last two days we started having an issue with our integration in production with PDFCreator 2.4.0 console app.

The PDFCreator Dialog is poping up instead of creating without user interaction.

If i manually try to save the dialog, it processes,then throws and error

10101 - System Could not open output file.

The log for the creator is full of these.

2018-08-20 22:04:11.2100 [Error] pdfforge.PDFCreator.Core.Workflow.ConversionWorkflow.RunWorkflow: An error occured during the Viewer_CouldNotOpenOutputFile
2018-08-20 22:04:11.2412 [Error] pdfforge.PDFCreator.Core.Workflow.JobInfoQueueManager.ProcessJob: The job 'E:\PDFCreator\Certificate_20180820220408823.xfdl' terminated at step Error and did not end successfully.
2018-08-20 22:04:14.7669 [Error] pdfforge.PDFCreator.Conversion.Actions.Actions.DefaultViewerAction.OpenJobOutput: File could not be opened.
2018-08-20 22:04:14.7825 [Error] pdfforge.PDFCreator.Core.Workflow.JobRunner.RunJob: The job failed: An action failed. (Viewer_CouldNotOpenOutputFile)
2018-08-20 22:04:14.7825 [Error]

and the application that is calling the creator is getting the below error.

Error Report for PDFCreator 2.4.0.213

Exception:
InvalidOperationException
A pipe server with the name PDFCreator-2 already exists!
at pdfforge.PDFCreator.Core.Communication.PipeServer.Start()
at pdfforge.PDFCreator.Core.Communication.PipeServerManager.StartServer()
at pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TryStartApplication(Func1 startApplication, Boolean startManagePrintJobs) at pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication(Func1 composePipeMessage, Func`1 startApplication, Boolean startManagePrintJobs)
at pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedStart.Run()
at pdfforge.PDFCreator.UI.Views.App.App_OnStartup(Object sender, StartupEventArgs e)
at System.Windows.Application.<.ctor>b__1(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

Log:
2018-08-22 09:30:10.1409 [Debug] 12528-1 (ProgramThread) pdfforge.PDFCreator.Editions.EditionBase.ProgramBase.StartApplication: Starting PDFCreator
2018-08-22 09:30:10.5933 [Debug] 12528-1 (ProgramThread) pdfforge.PDFCreator.Core.Printing.FolderProvider..ctor: Temp folder is 'C:\Users\PrintUser\AppData\Local\Temp\2\PDFCreator\Temp'
2018-08-22 09:30:10.5933 [Debug] 12528-1 (ProgramThread) .lambda_method: Spool folder is 'C:\Users\PrintUser\AppData\Local\Temp\2\PDFCreator\Spool'
2018-08-22 09:30:10.7961 [Info] 12528-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStartFactory.CreateApplicationStart: Command Line parameters:
/INFODATAFILE=C:\Users\PrintUser\AppData\Local\Temp\2\PDFCreator\Spool\5-3D54A664024647AAAE8D4EC9F0A0832D.inf
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile 'fc85ad83-5d44-4f1d-8f68-d706b029c66c' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile '0e89f533-5d35-4cb6-bcfd-4f4b90bceb2e' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile '787782e8-2b91-4aa9-8d9a-450ab649193f' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile 'fad452fd-87cc-435c-af60-306d3f9ed203' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile 'ee386a40-2522-4473-b83f-4159ca505f60' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile 'd3af0289-3366-4e1d-bf3b-e513fcc51c44' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile 'f5bb98ba-c26e-4fcd-94f8-feedd3f1ea58' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile 'b06fd26b-00c9-473c-8fbc-be6468a42999' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.TranslateProfilenames: Profile '41eb8372-c3ac-4eb7-b7b4-a0916d418072' has no translation
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles: Profiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.1706 [Trace] 12528-1 (ProgramThread) pdfforge.PDFCreator.UI.ViewModels.SettingsLoader.LogProfiles:
2018-08-22 09:30:11.2330 [Debug] 12528-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: Starting attempt 1:
2018-08-22 09:30:11.2642 [Debug] 12528-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TryStartApplication: Starting pipe server
2018-08-22 09:30:11.2642 [Debug] 12528-1 (ProgramThread) pdfforge.PDFCreator.Core.Communication.PipeServerManager.StartServer: Starting pipe server thread
2018-08-22 09:30:11.2642 [Error] 12528-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TryStartApplication: There was an error while starting the application
2018-08-22 09:30:11.2798 [Debug] 12528-1 (ProgramThread) pdfforge.PDFCreator.Core.Communication.PipeServerManager.Shutdown: Stopping pipe server
2018-08-22 09:30:11.3110 [Error] 12528-1 (ProgramThread) pdfforge.PDFCreator.Editions.EditionBase.ProgramBase.Application_DispatcherUnhandledException: Uncaught exception in WPF thread

2

Hi,

I am not quite sure what is happening there, but PDFCreator can't create xfdl files, is this the intended output format, or the input? The version you are using is rather old, if you can update to PDFCreator 3.2.2 we will be able to provide better support.
Please set the logging level to "trace" in the PDFCreator application settings, reproduce the error and send us the log to support(at)pdfforge.org

Best regards

Robin

3

Hello,
Thanks for your reply. We are working on getting the code set up in a QA environment so we can update the PDFCreator and make sure the app still works. It seems that some inner profile has become corrupt. The xfdl file is the source of the PDF. Currently the console app we inherited is expecting the file to name in a format that PDFCreator is no longer using. PDFCreator is appending the drive letter and underscore and the folder name on the PDF.

I turned on trace. It seems that our app might be running too many prints at the same time?

2018-08-23 11:50:57.3249 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: Starting attempt 1:
2018-08-23 11:50:57.3405 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TrySendPipeMessage: Found another running instance of PDFCreator, so we send our data there
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.TrySendPipeMessage: Pipe message successfully sent
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: TrySendPipeMessage: True
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: Starting update check thread
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Adding thread UpdateThread
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.SendMessageOrStartApplication: Starting Cleanup thread
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Starting CleanUpThread thread
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Utilities.Threading.ThreadManager.StartSynchronizedThread: Adding thread CleanUpThread
2018-08-23 11:50:57.3561 [Debug] 39944-11 (UpdateThread) pdfforge.PDFCreator.UI.ViewModels.Assistants.Update.UpdateAssistant.UpdateThread: Launched UpdateThread
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Core.Startup.AppStarts.MaybePipedApplicationStarter.Shutdown: Waiting for all threads to finish
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Utilities.Threading.ThreadManager.WaitForThreads: Waiting for all synchronized threads to end
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Utilities.Threading.ThreadManager.WaitForThreads: 2 Threads remaining
2018-08-23 11:50:57.3561 [Debug] 39944-11 (UpdateThread) pdfforge.PDFCreator.UI.ViewModels.Assistants.Update.UpdateAssistant.Update: Update period did not pass. Next Update is set to: 8/30/2018 11:44:31 AM
2018-08-23 11:50:57.3561 [Debug] 39944-1 (ProgramThread) pdfforge.PDFCreator.Utilities.Threading.ThreadManager.WaitForThreads: 1 Threads remaining
2018-08-23 11:50:57.3561 [Debug] 38876-13 () pdfforge.PDFCreator.Core.Controller.NewPipeJobHandler.HandlePipeMessage: New Message received: NewJob|C:\Users\ADMINI~1.GEO\AppData\Local\Temp\2\PDFCreator\Spool\79-03F278772B0D41FDB75F244FB13EA033.inf
2018-08-23 11:50:57.3717 [Debug] 38876-13 () pdfforge.PDFCreator.Core.Controller.NewPipeJobHandler.HandleNewJobMessage: NewJob found: C:\Users\ADMINI~1.GEO\AppData\Local\Temp\2\PDFCreator\Spool\79-03F278772B0D41FDB75F244FB13EA033.inf
2018-08-23 11:50:57.3717 [Trace] 38876-13 () pdfforge.PDFCreator.Core.Controller.NewPipeJobHandler.HandleNewJobMessage: The given file exists.

4

Hi,

thanks for the log, but I am afraid it doesn't really contain any clues about what could be going wrong.
If the console app expects a format which PDFCreator is no longer using, it was most likely written for 1.x version and can't work with 2.x, since the entire application + COM interface were completely redesigned for PDFCreator 2.x. Do you have the source code of the console application? If it doesn't perform very complex tasks,you might be better off rewriting it, the current COM interface is well documented:
http://docs.pdfforge.org/pdfcreator/3.2/en/pdfcreator/com-interface/

Best regards

Robin

5

The application isnt doing anything so fancy. It is calling the systems print function from console and passing the xfdl file as parameter to convert to a pdf.

I see in the admin app config options to append tokens to the name. Is there an INI file that might have been corrupted? or a place I could look to see why its appending these new values?

6

Hi,

PDFCreator can use INI files to load/save settings manually, but during normal operation, it will load/save settings from/to HKCU\Software\pdfforge\PDFCreator\Settings
If the application is only printing to PDFCreator and not accessing it through the COM interface, you could potentially restore the PDFCreator settings to default through the GUI and then configure everything as required.

Best regards

Robin