Fail to open .ps file

[Paul5FD5]

I have just installed Adobe Acrobat Pro DC Continuous Release | Version 2020.012.20043 and Adobe Acrobat Distiller DC Professional Version 20.12.20041394260. I have a .ps file that I'd like to convert from .ps to PDF. When I try and open the file from Acrobat, I get the following error message:

%%[ ProductName: Distiller ]%%
%%[ Error: invalidfileaccess; OffendingCommand: file ]%%

Stack:
(w)
(XSFT01.img)
/Fout

%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%

Any ideas?

[ls_rbls]

+++ EDITED REPLY

Seems like the source .ps file may be enforcing some editing  restrictions.

Is it possible for you to share this file ?

If this was an image file, how did the file ended up becoming a postscripted file? 

Did you print  the original file as image and then saved it as .ps?

[Paul5FD5]

Sorry, can't share the file. The tech process that generates the file is via Dialogue (Dialog?). What it does is generates 2 files, a PDF and a PS. The PDF is used to upload to our customer site so that they can download a statement or comms electronically. For some items, we also have to snail mail via the PS file. The PS file gets shipped to a PostScript printer, printed, put in an enevelop and mailed to the customer. The files are NOT identical. When we make changes (not too often) we get the .ps file from the outsourcer but we're not having much luck printing it. Adobe Distiller was my attempt to look at the file to ensure it's correct after changes but we ran into the error above.

[ls_rbls]

If I understood correctly, is Dialogue the PDF producing software? Is this related to architechtural design or a newsreader service?

[ls_rbls]

I also forgot to ask, from which operating system and version is the postscripted file being processed before printing? Is this a macOS environment? And which type of printer is it defaulted to to handle the printing of the postscripted file(s)? 

[Paul5FD5]

We don't have access to a PS printer, it's a secuity hazard...think SoX. We don't want people intercepting .ps files and printing "real" statements. The file we are intercepting is a test file with fake customer data.

[Paul5FD5]

Dialogue it a product produces both the PDF and the PS file. It probably runs on Windows or it could be unix. For us it's a service, we send them a file electronically, they produce the PDF and PS files which get automatically loaded into the customer portal or get sent to the mailing house (the PS does). It's all outsourced to a multinational...we have 1M+ customers..everything is a service. The file we are intercepting is in the test system. We run a process and it spits out a .pdf and a .ps in a directory and my testers open and inspect to ensure correctness. PDF is easy, PS is proving a pain in the a$$.

[ls_rbls]

From what I'm reading in regards of  the "XSFT01.img" error, this could be one of four things:

• If the postscript file wirtten to a TEMP folder (Unix-like systems) where the OS assumes the directory is writeable
• If the image files are currently processed in a directory other than a TEMP folder, maybe thethe folder has write permissions that need to be disabled
• the current value of the LockDistillerParams  parameter  is interfering with the Save operation
• the postscript printer where the file is sent to for printing does not implement the currentdistillerparams or setdistillerparams  operators.

See this old guide : Chapter 1, How to Set Distiller Parameters - "Inserting PostScript Code Into the Job", Page 14 

[Paul5FD5]

The XSFT01.img error is generated when I run Acrobat Distiller on my laptop running Windows 10 trying to open the file. I have been sent a copy of the .ps file and I was assuming that Distiller could read it...obviously not. I'm now wondering whether instead we could use GhostScript to read and print the file so we can have a look at it for errors.

[ls_rbls]

Apparently this happens with Ghostscript, and also with ps2pdf.

This looks more to me like an issue related to the font and/or image embedding.

See if the answer provided by Adobe Employee, Anandsri, in this discussion is relevant: 

• windows 10 distiller error %%[ Error: invalidfileaccess; OffendingCommand: file ]%%  

[Bernd Alheit]

Why want you create a image file?

[Paul5FD5]

In fact I did create an image file. I was not sure exactly which filetype it is. First I took a .jpg file and renamed it to XSFT01.img, put it in the same folder as the .ps file but no luck, same error. Then I thought perhaps it's a real .img file (google it), which is an image of a disk or folder structure. So I created a real .img file with 1 picture in it with the name XSFT01.img. Tried that, again no go, same error.

[Bernd Alheit]

The command in the PS file want create a image file.

[ls_rbls]

Could it be that the .img is also referring to the image dictionaries used by the Acrobat Distiller?

Normally .img is used by a software to create a group or sets of files in raw format while is writing to a temporary folder location  from the source document; then it regroups them. If that is the case I am thinking of the watchfolder.

It may need to be cleared of old files or test and create a new watch folder using Acrodist.exe and re-verify that such new watchfolder has no restrictions.

See slides:

Also, check the Distiller Reference guide I posted earlier, Page 22, and take a moment to read about image dictionaries for supporting JPEG2000 image compression. If this is actually the setting that is conflicting with the file creation, you may adjust this manually by selecting  custom Adobe PDF default settings:

See next slide: