Any automatic solution for fatal error ISDEV -1014 due to the target release folder specified in win explorer?

Question

My build of the installshield project gave this error:

"ISDEV: fatal error -1014: cannot rename the directory * \ Release to * \ Release.Bak. Windows Explorer or the DOS prompt may point to a subfolder of the output folder (Disk1) or Interm folder, blocking it. Change the current directory. Close all open files in Disk1 folder. Close Msidb.exe if it is open.

The reason is that before I started the build, I opened the win opener, which was listed in this release folder. And somehow ISDEV saw this as a folder lock, so he refused to rename it.

Now, is there a way, for example, to add some kind of script, to force close the entire open instance of the win explorer to release the so-called "lock" before starting the script assembly?

Thanks!

Answer 1

I know this is an old thread, but the problem still exists.

It seems that the error is not related to another process in which the folder is locked. I believe InstallShield is struggling with itself, trying to rename the folder in which IT still has files. Therefore, many traditional approaches, such as closing the conductor and even rebooting, sometimes do not work.

I found a fairly simple solution - delete the \ Express folder tree from the installation project folder before doing the build. InstallShield simply recreates it, and everything is in order, because renaming is not required.

Answer 2

This problem was as long as I remember how it worked in my first IntallShield.

Do not try to break the lock. Just make sure you do not keep the explorer open in the release folder until build. However, you can navigate to your parent folder or better: define a post-build publish event .

Answer 3

As I found, to delete this folder, you need to add something like this to the pre-build events:

RD fullPath\Express /S /Q 

Since the InstallShield project does not have the same properties as other projects, I introduced this into the Pre-build events in the properties of the main solution project.

Answer 4

There was the same problem, I just closed InstallShield and reopened it, working like a charm.