Personal ISOGEN error 53

[boon752003]

I have been working away for a while but before i went my PC ran isos fine. Now that im back all i get every time is this Personal ISOGEN error53.

Can somebody tell me how to fix this?

[TurnerSM]

Error 53 is "Unable to copy a file from the style directory to the current working directory."

Whcih file is a good question. You might want to check the pathing in your isogen.fls file for the particular style you are running.

You can access the IsoGen error codes online (if you do not still have the PDF from the 2004 version) here:

http://docs.bentley.com/en/PlantSpaceAutoISOGEN/

Even though this is a PlantSpace area, the IsoGen information is still relevant.
I've also attached the PDF for those that may prefer that format.

[boon752003]

Ive check the .fls file and everything seems fine, ive also check to make sure no folers/files have been changed to "Read Only", again everything seems ok.

Any ideas anybody?

[LenS]

sometimes a space in the directory file name can cause a problem for isogen to locate the required directory, also sometimes the trailing backslash can be missing from the end of one of the paths in the *.fls file causing errors

[WiZardOz]

Everytime you run a Iso some of the style files are copied from the
project isogen\**SYTLENAME*** Directory
to
C:\Documents and Settings\***USERNAME***\Local Settings\Temp Directory

If any of your projects style files are set as read-only (particularly the isogen.fls file) the copy that is placed into the C: Drive Directory is also read-only, then when you try to run another iso it can't copy the file over the top of the existing file in the C: Drive Directory and you get a PI Error 53 :(

Look in C:\Documents and Settings\***USERNAME***\Local Settings\Temp Directory and check for any Isogen Style related files (ie .fls, .opl) and make sure they are not read-only (these can be deleted), if they are read-only you will also need to find the project files that are read-only also or the problem will happen again next time that Project/Style is used


Regards,
Garry

[kfauver]

This usually happens when ISOGEN crashes or somebody stops ISOGEN through the Windows task manager. Meaning that one of the files is set to read-only because technically somebody still has it open. Find out who had it open last then have them re-boot. This will usually release it from read-only mode.