A Network Error Occurred When Installing Your Product
Posted: Mon Oct 18, 2010 11:37 pm
Hi folks,
I have inherited a product which has a 32 and 64 bit version of its installer. Both installers are built from the same installaware project, and to accommodate this setup I'm using a script to drive miabuild.exe from the command line, and setting different compiler variables depending on whether we're making a 32 or 64 bit installer. This approach has worked well for the last couple of years, but on one of my products it stopped working a few months ago. When there was a change in the script driving miabuild, so clearly the fault is on my end, but I can't for the life of me work out where.
The log output that I have for the script doesn't "look" like there's any change in what's being handed in to installaware, and doing a diff against an old, working log seems to indicate that I am handing the same arguments in to installaware as we ever have, so I'm assuming that the problem is in one of the hard coded variables inside the scripts.
The variables that have changed include the product code, the upgrade code and the revision code, so that the 32 and 64 bit versions of the product can be installed on the same computer. The product codes are generated using GUIDGen.exe, and the upgrade and revision codes are generated using a call against MS's built in APIs.
There are two symptoms of the problem. The first is that if i install the 64 bit version of the product, and then try to install the 32 bit version, I receive a warning dialog telling me "A Network Error Occurred When Installing Your Product", and a path to a temporary folder.
If I install the 32 bit version, then the 64 bit version, funnily enough the installer simply fails silently.
The second symptom, though, is that DATADIR is being set to the same value in both of the logs for the installations. I suspect this is the "underlying" cause of the other errors, but I'm uncertain how to go about fixing this as I've never encountered the error before. The InstallAware Help file didn't seem to have any obvious clues as to how to go about resolving this problem, either, though I could easily have simply overlooked something.
Can you help me work out how to fix this problem?
I have inherited a product which has a 32 and 64 bit version of its installer. Both installers are built from the same installaware project, and to accommodate this setup I'm using a script to drive miabuild.exe from the command line, and setting different compiler variables depending on whether we're making a 32 or 64 bit installer. This approach has worked well for the last couple of years, but on one of my products it stopped working a few months ago. When there was a change in the script driving miabuild, so clearly the fault is on my end, but I can't for the life of me work out where.
The log output that I have for the script doesn't "look" like there's any change in what's being handed in to installaware, and doing a diff against an old, working log seems to indicate that I am handing the same arguments in to installaware as we ever have, so I'm assuming that the problem is in one of the hard coded variables inside the scripts.
The variables that have changed include the product code, the upgrade code and the revision code, so that the 32 and 64 bit versions of the product can be installed on the same computer. The product codes are generated using GUIDGen.exe, and the upgrade and revision codes are generated using a call against MS's built in APIs.
There are two symptoms of the problem. The first is that if i install the 64 bit version of the product, and then try to install the 32 bit version, I receive a warning dialog telling me "A Network Error Occurred When Installing Your Product", and a path to a temporary folder.
If I install the 32 bit version, then the 64 bit version, funnily enough the installer simply fails silently.
The second symptom, though, is that DATADIR is being set to the same value in both of the logs for the installations. I suspect this is the "underlying" cause of the other errors, but I'm uncertain how to go about fixing this as I've never encountered the error before. The InstallAware Help file didn't seem to have any obvious clues as to how to go about resolving this problem, either, though I could easily have simply overlooked something.
Can you help me work out how to fix this problem?