Hi,
we are using the PDFCreator Server on a print server. We use the properties “Filename” (fix name) and “Save Location” (\ClientComputer\c$\Temp) to save files automatically to the C:\Temp folder on the client computer.
This works for most client computers, but not for one. On this computer the printer doesn’t create the file, but not error occurs.
Do you know similar issues and the reason for that?
(The access permissions are set, the folder exists, the server service is running…)
my first guess would be PDFCreaotr is having trouble to resolve the token for that machine, please set the logging level to trace in the PDFCreator Server GUI and check where it attempts to store the document when printing from the problematic machine.
Hi Robin,
Many thanks for your quick response.
I cannot see where the printer tries to save the file, but the following error is logged:
[Error] pdfforge.PDFCreator.Server.WorkerManager.DoWork: An error occured during print job 563: System.IO.IOException: Der Netzwerkpfad wurde nicht gefunden. (Networkpath not found)
bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
bei System.IO.Directory.InternalCreateDirectory(String fullPath, String path, Object dirSecurityObj, Boolean checkHost)
bei System.IO.Directory.InternalCreateDirectoryHelper(String path, Boolean checkHost)
bei pdfforge.PDFCreator.Core.Ghostscript.GhostScript.Run(OutputDevice output, String tempOutputFolder)
bei pdfforge.PDFCreator.Core.Jobs.GhostscriptJob.RunJobWork()
bei pdfforge.PDFCreator.Core.Jobs.AbstractJob.RunJob()
bei pdfforge.PDFCreator.Server.WorkerManager.DoWork(IJobInfo jobInfo, ConversionProfile profile)
InfFile: C:\Windows\TEMP\PDFCreator Server\Spool\65127F3FB702492A9B93A5E9B10634A6.inf
DocumentTitle: Microsoft Word - Dokument1
UserName: Administrator
WinStation: Services
ClientComputer: TT00
PrinterName: PDFCreator_Bestellbestaetigung
OutputFile:
OutputFile exists: False
did you set the debug log to trace?
The error says the network path couldn’t be found so it might be an issue with resolving the machines name properly, please have a look at the DNS settings for this machine.