Skip to main content
Participant
January 8, 2014
Answered

Framemaker 9 generating empty .PS file.

  • January 8, 2014
  • 6 replies
  • 1914 views

I have an enduser that is having an odd issue with Framemaker. They are trying to print a book to a .PS file, when the opperation is run, it is generating an empty .PS file. This ONLY happens to one file, and that file will work on other systems running the same versions of FrameMaker. Other Books on this system print fine. Also if you print to PDF you get the same results. We have tried to have another user on the same machine log in a the results are the same.

Any thought?

--Mike

This topic has been closed for replies.
Correct answer Mike Wickham

Could the comma in that filepath be a problem?

6 replies

Inspiring
August 22, 2018

Hi,

Just wanted to let you know that I also experienced this issue, but it was because my files were located in OneDrive (cloud). It created a postscript file no problem once the files were moved off the cloud.

Participant
January 8, 2014

Thanks everyone, there was a bloody comma in the file path.

Thanks so much

Bob_Niland
Community Expert
Community Expert
January 8, 2014

> ... there was a bloody comma in the file path.

This bug may exist in every version of Windows FM. I know it goes back to 7.0. It does not exist for Unix FM. Dunno about Mac.

Because it fails silently, I'm inclined to think it was not a deliberate check to avoid what was an illegal filepath character on Netware from DOS.

In any event, anyone still running FM3 or 4 on Windows 3.1/DOS, has learned to live with it by now.

Participant
January 8, 2014

Thanks for the replies,

I will be getting with the user here in a little bit to try the sugestions. in the meantime here is the log file

Acrobat Distiller 8.0

Started: January 7, 2014 at 15:32:49

Adobe PostScript software version: 3016.102

CID support library initialization completed.

Start Time: January 7, 2014 at 15:32:49

Source: RME_ReferenceGuide.tps

Destination: D:\BDB\Reference Model Editor 4.0,x\reference\RME_ReferenceGuide.pdf

Adobe PDF Settings: C:\Documents and Settings\All Users\Application Data\Adobe\Adobe PDF\Settings\Standard.joboptions

%%[ Warning: Empty job. No PDF file produced. ] %%

Distill Time: 00 Hour(s) : 00 Minute(s) : 00.47 Second(s)

I assume that this is the correct one it iwas located here c:\Documents and Settings\localuser\Application Data\Adobe\Acrobat\Distiller 8

If it is an issue with the graphics or fonts, would that not also carry forward to other computers?

thanks

--Mike

Bob_Niland
Community Expert
Community Expert
January 8, 2014

> Acrobat Distiller 8.0

Our installation of FM9 has Acrobat 9, not 8.

Not obvious if this is a problem.

> Source: RME_ReferenceGuide.tps

What log do you get just trying to print-to-Ps?

I'd expect at least a Ps header to be written.

> If it is an issue with the graphics or fonts, would that not also carry forward to other computers?

Not if it's imports inaccessible on, or fonts not installed on, that specific machine.

Inspiring
January 8, 2014

If you pull the one problem component file out of the book, will the book

print?

Art Campbell

art.campbell@gmail.com

"... In my opinion, there's nothing in this world beats a '52 Vincent and

a redheaded girl." -- Richard Thompson

No disclaimers apply.

DoD 358

I support www.TheGrotonLine.com, hyperlocal news for Groton MA.

On Wed, Jan 8, 2014 at 11:09 AM, Michael McBrine

Bob_Niland
Community Expert
Community Expert
January 8, 2014

Anything in the log file?

The list of things that could cause this is pretty much open-ended.

A few possibilities, in random order:

  • "use system fonts" is on in driver setup
  • default printer is not using a Ps or PDF driver
  • insufficient space for .ps or .tps file
  • various font and content errors that should be reported in log file
  • document or output file name or path has a comma in it
Arnis Gubins
Inspiring
January 8, 2014

What is the printer instance that is being used when printing to the .ps file?

Any graphics in that file? If so, turn them off using <esc> v v toggle and try printing again. If it does print then, then one of the graphics is the culprit.