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: directory resolution problem
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 28, 2008
01:28 PM
directory resolution problem
I am having some issues running command lines in the installer as CAs (don't even get me started on how bad a design this is, but I have to work with the junk the developers give me to work with).
So, I am trying to run some command lines as CAs. For working dirctory, I use [WindowsVolume]. The installer doesn't seem to complain about this property being used as the installation location for a component, but when used in the CA this way, I get this error:
"Error 2727. The directory entry [WindowsVolume] does not exist in the Directory table."
Does the property get reset at some point before the CA runs? Is there a better way to accomplish this?
So, I am trying to run some command lines as CAs. For working dirctory, I use [WindowsVolume]. The installer doesn't seem to complain about this property being used as the installation location for a component, but when used in the CA this way, I get this error:
"Error 2727. The directory entry [WindowsVolume] does not exist in the Directory table."
Does the property get reset at some point before the CA runs? Is there a better way to accomplish this?
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 29, 2008
11:31 AM
Please ensure the Working Directory does not include square brackets; it should just be the Directory name you would like to use:
WindowsVolume
If this is not the issue, can you confirm that WindowsVolume is present in the built MSI's Directory table?
WindowsVolume
If this is not the issue, can you confirm that WindowsVolume is present in the built MSI's Directory table?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 29, 2008
09:48 PM
Well, I tried it with and without brackets.
I must assume the value appears in the MSI, since I have components that are being installed to it (and I've verified that they do get installed), however I am using this as my measure since I am building this as a setup.exe (have prerequisites in the project). The problem only seems to occur when I use WindowsVolume as the working directory for a custom action.
I must assume the value appears in the MSI, since I have components that are being installed to it (and I've verified that they do get installed), however I am using this as my measure since I am building this as a setup.exe (have prerequisites in the project). The problem only seems to occur when I use WindowsVolume as the working directory for a custom action.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 30, 2008
10:33 AM
I would recommend running full MSI validation against your built MSI package. If the package checks out, there should be no ICE03 errors or any other errors reported on the CustomAction table, Directory table, or sequence tables.