TPS file is not deleted after FrameMaker creates PDFs via Acrobat 8

Report · Jan 23, 2007

Using FrameMaker 7.2 build 158, and Adobe Acrobat 8, when creating PDF files, the temporary PostScript file (*.tps), which is created before the final PDF, is not deleted after the creation of the PDF is complete.

This is a big deal for us because we are using a tool which hooks into the PDF-creation of FrameMaker/Distiller, and is reliant on this TPS file being deleted.

Is this a known bug? Does Adobe know about this? Do any other users have workarounds for this?

Report · Jan 23, 2007

I have exactly the same setup, but there isn't a TPS left behind.

What is your process for distilling?

Art

Report · Jan 25, 2007

Hi Art,

Well, the TPS seems to be left behind only occasionnaly when using Save as PDF directly from FrameMaker.

Our bigger problem is that we are using the SDK in a propriety program our company coded to hook into FrameMaker and created PDFs through Distiller in an automated fasion.

The TPS problem shows up consistenly using this method. I guess it is more of an SDK thing, however as mentionned, I did notice left over TPS files occasionnaly using the standard Save as PDF method in Frame.

Somehow the switch from Acrobat 7 to Acrobat 8 has caused the TPS not to be deleted using our propriety program. Looks like our programmer may have to dig into the code to figure out where the problem is being caused. We figured it is a FrameMaker bug, but only those using plugins may discover it, therefore we may have to code a workaround.

Thanks for the help anyhow.

Report · Jan 25, 2007

Jonathan,

Save As PDF isn't a recommended way to go, apparently because it has a few quirks. Might try using the Adobe PDF logical printer and printing to that instead.

Also, there's something in the back of my mind that's half remembering that the TPS files don't get wiped if the distillation process aborts or fails. If you're really into tracking down the problem, you may want to look at the Distiller logs to see if you can correlate the leftover TPS files to failures...

Art

Report · Jan 25, 2007

Jonathan:

In Acrobat Distiller, see if in "File > Preferences" there is a "Delete Log files for successful jobs" checkbox...(?)

Cheers & hope this helps,
Riley

Report · Feb 09, 2007

Log files have nothing to do with the TPS files...

Report · Feb 09, 2007

John,

I think Riley was pointing out that when it (the Delete Log Files checkbox) is checked, then any log files you find would be for unsuccessful jobs, which could be linked to your left-behind .TPS files.

If the TPS file for a given job is delted, it is probably because the job completed without errors.

So if you have log files, you also have clues...

Art

Report · Feb 09, 2007

Save As PDF isn't a recommended way to go, apparently because it has a few quirks

Art, can you point out which quirks. It would be interesting to know. To my knowledge the Save As command invokes the AdobePDF printer anyway (same as print), create a PostScript file (that happens to be called TPS instead of PS, and should be deleted. And finally starts Distiller.

keep smiling
thomas

Report · Feb 09, 2007

Thomas,

FWIW, speaking from experience with the Save As route, I've seen
random "phunnies" in the final PDFs (such as the missing fonts
issues), a bigger .tps file than the .ps file generated from directly
printing to file, slower throughput in both the intermediate
postscript file creation and actual distilling (probably tied in to
the larger .tps file) and other differences from what the joboptions
should have been.

There should not have been any differences in the file sizes being
created if the same printer instance/configuration was actually being
used. I also see this on some automated runs with Miramo. It's not
consistent either - sometimes it works fine and then the next run, the
process is considerably slower and there are dropouts in the PDFs.

So far, manually printing to a ps file and distilling always seems to
work without any issues.

Your mileage may vary.

Arnis

Report · Feb 09, 2007

Arnis,

Thanks, and:
" ..So far, manually printing to a ps file and distilling always seems to work without any issues..."

which is always the since Adobe invented Acrobat as a 'substitute' for PRINTING.

I do know what you mean, I I too have impressions and experiencenses of exactly the opposite when I look into your comments. The PS might be smaller then the TPS, fonts drop out when distilling the PS file, PS can be slower (partiucularly if there are a lot of tables in the FM files)

keep smiling
thomas

Report · Feb 12, 2007

Jonathan,

It's obvious what is happening. TPS reports are now mandatory.

"So, Peter, what's happening? Aahh, now, are you going to go ahead and have those TPS reports for us this afternoon?"

--Bill Lumbergh, from the movie Office Space

Ken

(Sorry. Couldn't resist)

Report · Feb 15, 2007

I had the same problem after upgrading to Acrobat 8.0.
Check your Distiller preferences (open Distiller and select File->Preferences). There are options here to select whether or not the log files are deleted for successful jobs.

Report · Feb 15, 2007

Sorry, this appears to make no difference :-(

Report · Apr 20, 2007

I have the same problem when using FM 7.2 build 158 and Acrobat 8 after using the Save As option in FM to save as PDF. The temporary files .tps and .tpdf are left in the folder. This is a huge issue when dealing with multiple manuals/books. I gained back over 40GB of memory after going through and deleting these two temporary files. Any know fix for automatically deleting the .tps and .tpdf files???

Report · Apr 25, 2007

I've noticed the exact same messiness with .TPS files when making PDF's from Frame7.2 with Acrobat 8 - the resulting PDF also never opens in Acrobat automatically either.

Report · Apr 30, 2007

I have had these exact same problems. It seemed to start when we upgraded to Acrobat 8 (from Acrobat 7). Using the info in this thread, I am now printing to Adobe PDF and then using Distiller to create the .pdf from the .ps file. It's an extra step but it works.

Thanks!

Report · May 01, 2007

Argh, these endless old-wives' tales about "Save as PDF" vs "Printing to Adobe PDF and then distilling" -
the former route isn't deprecated in the FrameMaker user docs (infact, it's the suggested route).
If it doesn't work properly, why is it in the application at all?
What does it do differently to printing anyways? (since both routes proceed via an intermediate PostScript file, then invoke Distiller - Frame doesn't create PDF natively the way InDesign or Illustrator do).

Report · May 16, 2007

For what it's worth:
I've been using "Save As PDF" in FrameMaker 7.0p578 with Distiller 6 & 7 and Acrobat 6 & 7 to create PDFs every day for years, and all has worked beautifully.
But a few days ago I upgraded to Distiller 8 and Acrobat 8 and am now getting the TPS problem and "File cannot be found. Unable to open..." message in Acrobat EVERY TIME.

Report · Jun 05, 2007

No improvement after installing today's 8.1.0 patch. (Still have the TPS problem and "File cannot be found. Unable to open..." message.)
Anyone else tried the patch yet?

Report · Jun 06, 2007

I just saw this from Shlomo Perets at www.Microtype.com:
"...once Acrobat/Distiller is upgraded to 8.1, "Save as PDF" won't work with TimeSavers settings, until a future version of FrameMaker will modify the "Save as PDF" function so that it triggers Distiller with the -F flag (so that it is capable of processing external files).
Obviously, you'll have to contact Adobe representatives with questions as to future FrameMaker versions and their "Save as PDF" capabilities."

Jeanie

Report · Jun 06, 2007

Does this mean we can again print to a PS file and distill will work?

Report · Jun 06, 2007

Sherman,

That's always worked. What's happened with the 8.1 Distiller is that
the default mode will no longer allow the postscript file being
distilled to access other external files (TimeSavers pulls in other
.ps files to do its magic stuff). One needs to configure Distiller to
start with the -F switch, which can't be done using Save As PDF (it
always calls Distiller without the switch).

Report · Jun 07, 2007

Hi Guys:
maybe my experience can eliminate the Acrobat 7, 8 diagnostic issue. I do not own either 7 or 8, but am having *occasional* failures in "save as" in FM 7.2 build 158. By failures I mean pretty substantial crashes with the .tps file being left behind as debris.

I have had a flawless performance from FM 7.2 in "save as" pdf until I installed the 158 patch. This could be coincidence but much more likely to be ignorance. I do not have a clue what goes wrong and am busy .MF'ing all the relevant files and trying again and again and again.
Down with all old wive's tales [spouses' tales?]let's sort this out
someone must know.

Rob Shell

Report · Aug 31, 2007

Save as PDF is needed when dealing with cross-referenced books.

All the books need to be open in FM and saved as PDF or you can end up with bad links.

Report · Sep 12, 2007

Well, I use Frame 7.2b144, Acrobat 7.0 (standard) and Distiller 7.0.

I have the same problem of tps files left behind after having "save as PDF" from Frame.
But this does not happen all the times and I have no explanation.

I remember that in former version of Acrobat/Distiller, preferences menu allows the user to chose to delete or not tps files. With recent Acrobat/Distiller, this choice has disappeared (only remains the choice to delete or not log files).

The point is not to chose between two way of creating PDF file ("print" or "save as") : there is a bug with Frame and/or Acrobat and Adobe shall solve it !

Regards