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: Corruption of TCP/IP after IS2008 Basic MSI setup
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
‎Sep 13, 2007
12:06 PM
Corruption of TCP/IP after IS2008 Basic MSI setup
Hi,
we have a serious problem with a basic msi setup created with IS2008 Premier.
Problem: IS2008 Basic MSI Setup corrupts customer machines during INSTALLATION if a COM component is deployed (in contrast to knowledge base article Q113345 where uninstalls are affected)
Severity: Showstopper [end-customer systems will be corrupted]
Reproducability: always
Customer systems affected: W2k, WXP, Vista
Symptoms:
1. c:\>ping localhost (works fine)
2. Execute IS2008 created Basic MSI Setup with COM extraction at build time or with Extracted COM information (in our test case 1 COM component is installed).
3. c:\>ping localhost (does not work anymore)
TCP/IP stack is corrupt. There are no special operations in the setup except the registration of the 3 COM components (no custom actions, no registry entries etc.)
We have reproduced this behavior with a fresh basic msi installation. We only added one exe-file, and extracted the COM info (1 interface only). We did nothing else, except to choose MSI 3.1 and a single setup file distribution. The correct resolution of the localhost (127.0.0.1) stops after the installation. Even after a reboot it does not work anymore.
Any suggestions are welcome!
Ralf
we have a serious problem with a basic msi setup created with IS2008 Premier.
Problem: IS2008 Basic MSI Setup corrupts customer machines during INSTALLATION if a COM component is deployed (in contrast to knowledge base article Q113345 where uninstalls are affected)
Severity: Showstopper [end-customer systems will be corrupted]
Reproducability: always
Customer systems affected: W2k, WXP, Vista
Symptoms:
1. c:\>ping localhost (works fine)
2. Execute IS2008 created Basic MSI Setup with COM extraction at build time or with Extracted COM information (in our test case 1 COM component is installed).
3. c:\>ping localhost (does not work anymore)
TCP/IP stack is corrupt. There are no special operations in the setup except the registration of the 3 COM components (no custom actions, no registry entries etc.)
We have reproduced this behavior with a fresh basic msi installation. We only added one exe-file, and extracted the COM info (1 interface only). We did nothing else, except to choose MSI 3.1 and a single setup file distribution. The correct resolution of the localhost (127.0.0.1) stops after the installation. Even after a reboot it does not work anymore.
Any suggestions are welcome!
Ralf
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 20, 2007
07:53 AM
Check the Registry table of your built .msi file (in Orca or in Direct Edit mode) and/or create a install log. Maybe your setup is overwriting som TCP/IP settings?
Stefan Krueger
InstallSite.org
InstallSite.org
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 20, 2007
08:36 AM
Stefan, thanks for your reply. We have found the problem. You are right the problem was the registry table, but the reason was as follows:
The "Extract COM Data" function of IS2008, regardless whether it is done at built time or not, does not only extract COM data (CLIS, ProgID, TypeLib).
In our case our program registers a temporary TCP protocol handler at runtime, valid only during runtime and only for the process. The Extract COM procedure catches this data and writes it to the registry table. (Removing this data solves the problem.)
We can reproduce the behaviour, if we only add this single exe to a fresh setup. Extract COM and build the setup.
From my point of view it's a clear error of "Extract COM data" procedure. Looks like, our program is initialized during this process and all modifications to the registry are registered.
The "Extract COM Data" function of IS2008, regardless whether it is done at built time or not, does not only extract COM data (CLIS, ProgID, TypeLib).
In our case our program registers a temporary TCP protocol handler at runtime, valid only during runtime and only for the process. The Extract COM procedure catches this data and writes it to the registry table. (Removing this data solves the problem.)
We can reproduce the behaviour, if we only add this single exe to a fresh setup. Extract COM and build the setup.
From my point of view it's a clear error of "Extract COM data" procedure. Looks like, our program is initialized during this process and all modifications to the registry are registered.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 20, 2007
09:34 AM
http://support.installshield.com/kb/view.asp?articleid=Q113345
Is it this bug? If possible I do not use extract at build, one of the reasons being the loss of control and therefore the potential for unexpected things appearing in the registry.
Is it this bug? If possible I do not use extract at build, one of the reasons being the loss of control and therefore the potential for unexpected things appearing in the registry.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)