2 apps using same GUID
I repackaged DataFlux dfStudio 8 and installed the MSI on a PC. It installed and worked fine. However, when I uninstall it I get the expected DataFlux Windows Installer dialog box, then I get a generic Windows Installer dialog box. When those 2 eventually finish, I get a Symantec SEP11 Windows Installer dialog box that it is reconfiguring itself.
I looked in the Event Viewer and found the entry below and I alse searched the Registry. Sep11 appears to use the 2 GUIDs starting with {D689B41 and {9B2CAF3. DataFlux has an entry in the Registry table and also uses the GUID starting with {9B2CAF3 . Does it appear that when DataFlux removes itself that it is also removing a piece that SEP11 uses and that is causing the problem? If so, then I guess I probably need to chaneg the GUID in my DataFlux MSI.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 9/8/2010
Time: 11:32:22 AM
User:
Computer:
Description:
Detection of product '{D689B418-235A-4290-A0A5-A75E490E0351}', feature 'Core', component '{9B2CAF3C-B0AB-11EC-B01F-C8B3B9A1E18E}' failed. The resource
'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_cbb27474\downlevel_payload.8.0.50727.762\' does not exist.
I looked in the Event Viewer and found the entry below and I alse searched the Registry. Sep11 appears to use the 2 GUIDs starting with {D689B41 and {9B2CAF3. DataFlux has an entry in the Registry table and also uses the GUID starting with {9B2CAF3 . Does it appear that when DataFlux removes itself that it is also removing a piece that SEP11 uses and that is causing the problem? If so, then I guess I probably need to chaneg the GUID in my DataFlux MSI.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 9/8/2010
Time: 11:32:22 AM
User:
Computer:
Description:
Detection of product '{D689B418-235A-4290-A0A5-A75E490E0351}', feature 'Core', component '{9B2CAF3C-B0AB-11EC-B01F-C8B3B9A1E18E}' failed. The resource
'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_cbb27474\downlevel_payload.8.0.50727.762\' does not exist.
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
Dantè
14 years ago
then I guess I probably need to chaneg the GUID in my DataFlux MSI
Yes
Posted by:
pjgeutjens
14 years ago
'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations\x86_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_cbb27474\downlevel_payload.8.0.50727.762\' does not exist.
Does your package by any chance contain a merge module for Visual C++ 8.0 ATL? (If it doesn't then it should, looks like [:)])
And do all the impacted packages contain this merge module?
quote:
then I guess I probably need to chaneg the GUID in my DataFlux MSI
Yes
No, actually, sort out the shared components between the packages
Posted by:
timmsie
14 years ago
Maybe you should start conflict managing your apps as this will highlight these sort of issue's
As Pieter says though you need to sort out your shared components across your packages
As Pieter says though you need to sort out your shared components across your packages
Posted by:
zartan24
14 years ago
Yes, it does use Visual C++ 8.0. That merge module/redistributable has been a huge pain over the past 6 months when developing packages. I'm not sure how to "sort out my shared components", I'll have to look into that.
The GUID in my package does not appear to be a Key field in any table and it only appears twice. What would be wrong with changing the GUID?
The GUID in my package does not appear to be a Key field in any table and it only appears twice. What would be wrong with changing the GUID?
Posted by:
pjgeutjens
14 years ago
What would be wrong with changing the GUID?
this would seem like a solution maybe, but what happens when at some point you uninstall the DataFlux package, and it rips this component from the machine. Then, once again, all the other applications will complain about it being missing.
What is meant by sorting this out is this: we're talking about 3 applications here that want to install the same resource. For this to be done successfully some things have to be in order.
1) each package should ideally contain the same version of the merge module
2) matching files should be in components with the same GUID
3) these components should be set as shared in each of the Windows Installer package, so that when one package uninstalls, it actually notices 2 others use these files and thus leaves them in place.
I have a feeling that point 3 is where your packages go wrong.
PJ
Posted by:
zartan24
14 years ago
It turns out the problem was that my exe install Capture had an embedded MSI that I did not notice. So I captured an MSI install inside my MSI. Which is a bad thing. I normally check if an exe has an embedded MSI before I capture it, but I guess I must have missed this one.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.