29100 - Internal GhostScript Error

Hi,

if the app sends PCL commands directly, I am afraid PDFCreator will not be able to handle it. I think you can find out by disabling automatic saving in PDFCreator, printing something from the app and then (before pressing save inside the PDFCreator GUI) checking the file in %temp%\PDFCreator\spool. It will be a .ps file, but if you open it with a text editor and it doesn’t have a .ps header, it isn’t actually a proper Postscript file.

Best regards

Robin

Thanks for the suggestion! I will try that.

-Ray

Hi Robin,
I'm a Chinese user,I met the same error code, “29100 - Internal GhostScript Error.”
My PDFCreator version is 3.2.1,OS: windows 7 sp1 x64
can you help me with some solution?
Thanks & Best regards

Hi Qian,

there can be multiple reasons for getting this error; it basically just means something unexpected or beyond our control went wrong during the conversion from Postscript, which is done by Ghostscript.
Please go to the PDFCreator application settings, set the logging level to "trace" and reproduce the error.
Afterwards, either send your log to support(at)pdfforge.org or post it here and we will try to help.

Best regards

Robin

Hey Robin,
Thanks a lot, and I will try it.

Best regards

Hi

It works succesfulate in last year.
But it doesn't work after reinstall WIN10 with format.
I tried many versions PDFCreator.
Now I install latest 3.2.2 and occured ghostscript error 29100

So I needs your helps.

Here is my log file.

'
2018-06-29 10:51:27.9439 [Error] pdfforge.PDFCreator.Conversion.Ghostscript.Conversion.GhostscriptConverter.DoConversion: Ghostscript execution failed: Error: /undefinedfilename in (C:\Users\\354\302\254\354\332\251\354\336\220\AppData\Local\Temp\PDFCRE~1\Spool\33AF3C~1\testpage.ps)
Operand stack:

Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push
Dictionary stack:
--dict:999/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)--
Current allocation mode is local
Last OS error: No such file or directory

2018-06-29 10:51:27.9439 [Error] pdfforge.PDFCreator.Conversion.Ghostscript.Conversion.GhostscriptConverter.DoConversion: There was a Ghostscript error while converting the Job C:\Users\사용자\AppData\Local\Temp\PDFCreator\Spool\33af3c1b-b47f-4297-bf34-366195b5073d\testpage.inf: pdfforge.PDFCreator.Conversion.Jobs.ProcessingException: Ghostscript execution failed: Error: /undefinedfilename in (C:\Users\\354\302\254\354\332\251\354\336\220\AppData\Local\Temp\PDFCRE~1\Spool\33AF3C~1\testpage.ps)
Operand stack:

Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push
Dictionary stack:
--dict:999/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)--
Current allocation mode is local
Last OS error: No such file or directory

위치: pdfforge.PDFCreator.Conversion.Ghostscript.Conversion.GhostscriptConverter.DoConversion(Job job)
2018-06-29 10:51:27.9439 [Error] pdfforge.PDFCreator.Core.Workflow.JobRunner.RunJob: The job failed: Ghostscript execution failed: Error: /undefinedfilename in (C:\Users\\354\302\254\354\332\251\354\336\220\AppData\Local\Temp\PDFCRE~1\Spool\33AF3C~1\testpage.ps)
Operand stack:

Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push
Dictionary stack:
--dict:999/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)--
Current allocation mode is local
Last OS error: No such file or directory

(Conversion_GhostscriptError)
2018-06-29 10:51:27.9719 [Error] pdfforge.PDFCreator.Core.Workflow.ConversionWorkflow.RunWorkflow: Error Conversion_GhostscriptError: Ghostscript execution failed: Error: /undefinedfilename in (C:\Users\\354\302\254\354\332\251\354\336\220\AppData\Local\Temp\PDFCRE~1\Spool\33AF3C~1\testpage.ps)
Operand stack:

Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push
Dictionary stack:
--dict:999/1684(ro)(G)-- --dict:0/20(G)-- --dict:78/200(L)--
Current allocation mode is local
Last OS error: No such file or directory

2018-06-29 10:51:29.6189 [Error] pdfforge.PDFCreator.Core.Workflow.JobInfoQueueManager.ProcessJob: The job 'PDFCreator Testpage' terminated at step Error and did not end successfully.

'

Please help.
Thx.

Hi,

it seems it isn't able to correctly rebuild the string for your username, but I am not sure why. I created a user account with your username for testing but it was able to convert everything properly, so the Unicode characters don't seem to be the issue.
Did you by any chance disable the creation of 8.3 DOS File Names on your partition(s)?
PDFCreator won't work properly if this is disabled, but it is enabled by default in all supported Windows editions.

Best regards

Robin

I pinned down the 29100 Error for my system: The error occurs if

  1. the user has blanks in the username (as it may become standard with Windows 10!)
  2. PDFCreator profile prints to PDF/A

I first thought the reason was because the print profile has the "change" > "use PDF as background" option enabled, but this is not the case - the only reason is PDF/A in combination with "username has blanks" (for my system).

I will attach two trace logs (one with PDF/A => error occurs, second with PDF (not A) => no error). Please consider that neither the "background file" part nor the "post process script call" that I use has any influence on the occurence of the error (I tried both). I tried with another user account that has a user name without blanks on the same machine, same profiles (importet via INI) => no error.

Maybe that help's to get rid of this odd old error - at least on some machines.

PDFCreator_UserWithBlanksInName_ProfileUsesPdfA_Error29100.log.txt (17.1 KB)
PDFCreator_UserWithBlanksInName_ProfileUsesPdfWithouttA_NoError29100.log.txt (20.0 KB)

Hi. I just solve 29100 Internal GS Error. In my case PDF creator was not printed at all, when i click print in any program, nothing happens, only after approx. 2 minutes pdfcreator shows window with 29100 error. some text with "29100" and "ActivationException format is not supported".
Ok, in my case the last one is the key to solve problem. This mean that in my system in system variables (Control panel->system->advanced system settings->environment variables) variables with names like "TEMP" and "TMP" was allocated with many ways. All that you need is to click "Change" in Environment variables menu for TEMP or TMP variable and then delete all ways expect system (which seems like %USERPROFILE%\AppData\Local\Temp). Then save and without reboot PDF Creator will work.
Check this variables in your case - this may help.
sorry for bad english

1 Like