This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: More InstallShield project issues
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 27, 2008
10:13 AM
More InstallShield project issues
I am currently evaluating Express 2008 to release a web service.
When I build my InstallShield project I get the following error -1014:
-1014: Cannot rename directory F:\DevPsiPro\NewPsion\PocketGM WS\Setup\Express\SingleImage to F:\DevPsiPro\NewPsion\PocketGM WS\Setup\Express\SingleImage.Bak.
Windows Explorer or a DOS prompt may be pointing to a subfolder of the release output folder (Disk1) or to the Interm folder, locking it. Change the current directory. Close any open files in the Disk1 folder. Close Msidb.exe if it is open.
I do not have file explorer or Msidb running.
Also, if I select File and Features from the project window, I get the "Microsoft Visual Studio has encountered a problem and needs to close"
If anyone can throw any light onto these issues I would very much appreciate it, many thanks
When I build my InstallShield project I get the following error -1014:
-1014: Cannot rename directory F:\DevPsiPro\NewPsion\PocketGM WS\Setup\Express\SingleImage to F:\DevPsiPro\NewPsion\PocketGM WS\Setup\Express\SingleImage.Bak.
Windows Explorer or a DOS prompt may be pointing to a subfolder of the release output folder (Disk1) or to the Interm folder, locking it. Change the current directory. Close any open files in the Disk1 folder. Close Msidb.exe if it is open.
I do not have file explorer or Msidb running.
Also, if I select File and Features from the project window, I get the "Microsoft Visual Studio has encountered a problem and needs to close"
If anyone can throw any light onto these issues I would very much appreciate it, many thanks
(1) Reply
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Feb 28, 2008
02:58 PM
It's very likely that Visual Studio itself has the directory open. You can use Process Explorer to locate the application that has the directory open and close the handle:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx