cwadams1955
Programmer
Hi,
The office staff here has a couple of custom templates that they've been using for several years now to generate company letters. The company was bought by another firm, and about two weeks ago this office's network was attached to the new company's domain; login scripts were changed, security permissions, desktop settings, and so forth. Since that time, staff has been unable to convert their documents. Monday I started digging into the problem and found an Adobe Knowledgebase article referencing corrupted .icc files at this link:
The error referenced was not exactly the same, but it was the closest thing I've been able to find, so I decided to give it a shot.
Late Monday I went through the steps in the article on one of the problem workstations, and the error went away - was able to do seven or eight conversions successfully, so I saved the files and instructions for use the next day. Yesterday I started to do the same process on the other three workstations, but it had no effect on them, and in the middle of this, I was notified that now the first workstations has stopped working again, also - it was neither turned off nor rebooted overnight, but the same error is appearing again. Repeating the process from the day before does nothing now to correct the error, nor can I convert the *same test document* that I converted successfully multiple times the day before. Hopefully someone can point me in a direction to start looking.
Machines: Dell and HP, various hardware.
Example: Dell Pentium 4, 3.20 GHz, 3.00 GB RAM
OS: Windows XP Pro, v2002, SP2
MS-Word 2003 SP2
Adobe Acrobat 6.0 Standard, v6.0.6
Adobe Distiller v6.0.1
Inside Word, Adobe Conversion Settings:
Use prologue.ps and epilogue.ps
Conversion Settings file: Custom template settings (standard doesn't work, either)
Enable accessibility & reflow with tagged PDF is checked
Compatibility - Acrobat 5.0
Color settings file - "None" (some machines have Web Standard selected, which also doesn't work.)
Color management policies - Leave color unchanged
Imbed fonts - checked on two W/S, one has several fonts excepted
- unchecked on two W/S
Process:
Letter template has macros which insert a logo in the document at print time, check tables, do calculations, check for "forbidden words". Template also contains a TOC. To test this, I simply open Word, make sure the macros are loaded (since the login scripts changed, this has to be done manually,) and create a new document from the proper template. There is a startup macro that can be simply bypassed (all it does is allow operator to change the office location, otherwise just leave the default,) and then from the "Adobe PDF" option on the Word menu bar, select "Convert to PDF". If the complete conversion runs, this may take up to a couple of minutes to finish, then the converted document is opened in Acrobat. What happens now is that the conversion process starts, then the process bar hangs for a few seconds and we get a messagebox stating: "Adobe pdf printer failed to create the pdf file"
Most of the time, it doesn't seem to produce an errorlog, but if it does, this is what I see in the log:
%%[ ProductName: Distiller ]%%
%%[ Error: undefined; OffendingCommand: pdfmark ]%%
Stack:
[{FMSMColorLogo}]
[{FMSMColorLogo}]
-mark-
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
The office staff here has a couple of custom templates that they've been using for several years now to generate company letters. The company was bought by another firm, and about two weeks ago this office's network was attached to the new company's domain; login scripts were changed, security permissions, desktop settings, and so forth. Since that time, staff has been unable to convert their documents. Monday I started digging into the problem and found an Adobe Knowledgebase article referencing corrupted .icc files at this link:
The error referenced was not exactly the same, but it was the closest thing I've been able to find, so I decided to give it a shot.
Late Monday I went through the steps in the article on one of the problem workstations, and the error went away - was able to do seven or eight conversions successfully, so I saved the files and instructions for use the next day. Yesterday I started to do the same process on the other three workstations, but it had no effect on them, and in the middle of this, I was notified that now the first workstations has stopped working again, also - it was neither turned off nor rebooted overnight, but the same error is appearing again. Repeating the process from the day before does nothing now to correct the error, nor can I convert the *same test document* that I converted successfully multiple times the day before. Hopefully someone can point me in a direction to start looking.
Machines: Dell and HP, various hardware.
Example: Dell Pentium 4, 3.20 GHz, 3.00 GB RAM
OS: Windows XP Pro, v2002, SP2
MS-Word 2003 SP2
Adobe Acrobat 6.0 Standard, v6.0.6
Adobe Distiller v6.0.1
Inside Word, Adobe Conversion Settings:
Use prologue.ps and epilogue.ps
Conversion Settings file: Custom template settings (standard doesn't work, either)
Enable accessibility & reflow with tagged PDF is checked
Compatibility - Acrobat 5.0
Color settings file - "None" (some machines have Web Standard selected, which also doesn't work.)
Color management policies - Leave color unchanged
Imbed fonts - checked on two W/S, one has several fonts excepted
- unchecked on two W/S
Process:
Letter template has macros which insert a logo in the document at print time, check tables, do calculations, check for "forbidden words". Template also contains a TOC. To test this, I simply open Word, make sure the macros are loaded (since the login scripts changed, this has to be done manually,) and create a new document from the proper template. There is a startup macro that can be simply bypassed (all it does is allow operator to change the office location, otherwise just leave the default,) and then from the "Adobe PDF" option on the Word menu bar, select "Convert to PDF". If the complete conversion runs, this may take up to a couple of minutes to finish, then the converted document is opened in Acrobat. What happens now is that the conversion process starts, then the process bar hangs for a few seconds and we get a messagebox stating: "Adobe pdf printer failed to create the pdf file"
Most of the time, it doesn't seem to produce an errorlog, but if it does, this is what I see in the log:
%%[ ProductName: Distiller ]%%
%%[ Error: undefined; OffendingCommand: pdfmark ]%%
Stack:
[{FMSMColorLogo}]
[{FMSMColorLogo}]
-mark-
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%