mrkelter1.5524898928853547E12 asked a question.
Has anybody else had this problem?
Are you sure you want to cancel the case creation?
Activity: Status change: 2 hours ago
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
On Vista, if I try to upgrade my product version 2.0.0199 to a new one with version 2.0.0205, I get the error 1316 (and Note 2203). I also see it sometimes on Windows XP. The error shows up as a popup dialog during the install and is seen in the logs
On Vista, I also see things like this in the install log, some (not all) of my Custom Actions:
InstallShield 13:46:04: Invoking script function MyOnMoving
1: SETUP: MyOnMoving
1: SETUP: MyDeleteModifiedFiles
InstallShield 13:46:04: CallScriptFunctionFromMsiCA() ends
MSI (s) (30:1C) [13:46:04:962]: NOTE: custom action MyOnMoving unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
MSI (s) (30:E8) [13:46:04:963]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,)
Action 13:46:04: ProcessComponents. Updating component registration
MSI (s) (30:E8) [13:46:04:965]: Executing op: ProgressTotal(Total=52,Type=1,ByteEquivalent=24000)
I have attached the logs.
-Walter
" Kelter wrote:
On uninstall, i get a Network error occured while attempting to read from the file C:\Windows\Installer\MyProduct.msi. This is wierd because the cached msi in that directory is named 608e1.msi. Basically, every installation creates a randomly-names msi file in that location, but on uninstall, it looks for an msi with the actual productname.
Has anybody else had this problem? "
A 1316 error should not be occurring during an uninstall as the Windows Installer does not typically look for the original MSI package. Can you attach a verbose log of the uninstall?
For upgrades, specifically for small updates and minor upgrades, the name of the MSI package needs to be the same as the base install MSI package filename. If the name changes in one of these upgrades, a 1316 error will occur. If the MSI filename needs to be changed, a major upgrade must be performed (see http://msdn2.microsoft.com/en-us/library/aa367850.aspx ).
http://community.macrovision.com/showthread.php?t=172412
for more details...
Based on some conditions out of my control, the ALLUSERS property was giving the install inconsistent locations from which to initialize itself. Grr. Should have just called support.