We have a project that has an additional dialog in it, which is present, has been added to the project, and which builds an installer (single exe) without any errors. However, when we then try to install the product, it complains at runtime that it encounters a file not found condition. The line number given points to the line where our extra dialog is displayed. Can anyone tell us what we're doing wrong? and why does the single exe not have the dialog embedded, like its designation implies?
Thanks for any help....
Dre'
Installer reports missing a dialog file
Re: Installer reports missing a dialog file
I'm working for the same company and also try to resolve this issue.
Some extra information:
- We remove our dialog and rebuild the installer. Now it 'complains' about the next dialog in line (that is licensecheck)
- In debugging mode the problem also occurs, but I can destill any more info. Are there certain system variables I show watch?
We've got a previous version from source control which does work. Obviously any bugfixes between that version and our current version are suspect, but nothing is changed on the part of the dialogs.
The (extra) changes prior to the dialogs are basically stopping IIS, stopping the license server and stopping our logging service. I can't imagine which of those could be blocking our current installer. I assume that any changes after the dialogs don't affect the installer.
We're in quite a pickle here, so any thoughts are welcome.
Some extra information:
- We remove our dialog and rebuild the installer. Now it 'complains' about the next dialog in line (that is licensecheck)
- In debugging mode the problem also occurs, but I can destill any more info. Are there certain system variables I show watch?
We've got a previous version from source control which does work. Obviously any bugfixes between that version and our current version are suspect, but nothing is changed on the part of the dialogs.
The (extra) changes prior to the dialogs are basically stopping IIS, stopping the license server and stopping our logging service. I can't imagine which of those could be blocking our current installer. I assume that any changes after the dialogs don't affect the installer.
We're in quite a pickle here, so any thoughts are welcome.
Re: Installer reports missing a dialog file
Well, we figured it out. I'd still like some input from the IA team though.
What we found is that when we called:
in the section:
that the problem as described in the first post occured.
When this call was removed, our script continued to work. Next we placed it in:
The script continued to work fine.
Can anyone of the IA team elaborate on this? Is this a oversight on my part? Should I have known not to do this call in the Check/Install Application Pre-requisites section, or is this a bug?
What we found is that when we called:
Code: Select all
Run Program $SERVICETARGETDIR$RoganSysLog.exe -k (WAIT, get result into variable LASTERROR)Code: Select all
Check/Install Application Pre-requisitesWhen this call was removed, our script continued to work. Next we placed it in:
Code: Select all
Perform First or Maintenance InstallationThe script continued to work fine.
Can anyone of the IA team elaborate on this? Is this a oversight on my part? Should I have known not to do this call in the Check/Install Application Pre-requisites section, or is this a bug?