Hi
I have a installer buid using AI 9.8. We are able to sucusfully install the product in XP, Win 7 (both 64 and 32 bit)
But we are unable to install the product in windows server 2003. Please find the installtion log from the attachment.
Suggested Articles
Installtion on windows server 2003
- Attachments
-
- WindowsServer2003.LOG
- (381.11 KiB) Downloaded 353 times
Re: Installtion on windows server 2003
Hi,
I'm not sure why you encounter this behavior. In the log you sent it seems that the installer complains about permissions to access the "HKEY_LOCAL_MACHINE32\Software\Wow6432Node\Microsoft\Windows\Office\Excel\AddIns\SteelwedgeTangoPlugin.Connect" registry entry.
Can you please send us the .AIP (project file) and a verbose log of the installation (created with /L*V option) to support at advancedinstaller dot com so we can investigate them? Also, can you tell us if the Windows Server 2003 machine where you test it a 32-bit or 64-bit machine?
Best regards,
Eusebiu
I'm not sure why you encounter this behavior. In the log you sent it seems that the installer complains about permissions to access the "HKEY_LOCAL_MACHINE32\Software\Wow6432Node\Microsoft\Windows\Office\Excel\AddIns\SteelwedgeTangoPlugin.Connect" registry entry.
Can you please send us the .AIP (project file) and a verbose log of the installation (created with /L*V option) to support at advancedinstaller dot com so we can investigate them? Also, can you tell us if the Windows Server 2003 machine where you test it a 32-bit or 64-bit machine?
Best regards,
Eusebiu
Re: Installtion on windows server 2003
Its windows Server 2003 X64 – SP2
I have send the details to support at advancedinstaller dot com
I have send the details to support at advancedinstaller dot com
Re: Installtion on windows server 2003
Hi,
Just posting the solution discussed on the forums, so other users can see it.
The first problem is that you configured incorrectly the registry entries from the package, under HKLM.
You must NEVER create manually the registry hive "Wow6432Node", this is done automatically by the OS. Please
delete the entire key "Wow6432Node" from your project and try it again.
Let me explain how registry redirection works and why do not need to create that key manually.
The hive "Wow6432Node" is a virtual one, generate and maintained by the OS, for 32 bit application that run on 64 bit OSes.
So if you have an installer or an application that tries to write or read from "HKLM\Software\Microsoft\...", the OS will automatically redirect it to
"HKLM\Software\Wow6432Node\Microsoft\...", even if in debug mode of your application you see the path without "Wow6432Node" in it.
So the installer should not try to write this key, the other key you have will be automatically written in that location.
Also, I see you have set the package to be mixed, but the installation path is incorrect, it should be:
This will make it always go to "Program Files" folder on 32 and 64 bit machines.
As for the registry keys, that remain, if you do not want them to be redirected to "Wow6432Node" key on 64 bit machines, you need to set the flag "64-bit component" on them. To do that select the registry values, press F8 and then set the flag on the component.
This flag is ignored on 32-bit machines, so the registry will still be normally created there too.
Best regards,
Bogdan
Just posting the solution discussed on the forums, so other users can see it.
The first problem is that you configured incorrectly the registry entries from the package, under HKLM.
You must NEVER create manually the registry hive "Wow6432Node", this is done automatically by the OS. Please
delete the entire key "Wow6432Node" from your project and try it again.
Let me explain how registry redirection works and why do not need to create that key manually.
The hive "Wow6432Node" is a virtual one, generate and maintained by the OS, for 32 bit application that run on 64 bit OSes.
So if you have an installer or an application that tries to write or read from "HKLM\Software\Microsoft\...", the OS will automatically redirect it to
"HKLM\Software\Wow6432Node\Microsoft\...", even if in debug mode of your application you see the path without "Wow6432Node" in it.
So the installer should not try to write this key, the other key you have will be automatically written in that location.
Also, I see you have set the package to be mixed, but the installation path is incorrect, it should be:
Code: Select all
[AI_ProgramFiles][Manufacturer]\[ProductName]As for the registry keys, that remain, if you do not want them to be redirected to "Wow6432Node" key on 64 bit machines, you need to set the flag "64-bit component" on them. To do that select the registry values, press F8 and then set the flag on the component.
This flag is ignored on 32-bit machines, so the registry will still be normally created there too.
Best regards,
Bogdan