Microsoft_VC80_ATL_x86.msm (8.0.50727.762) merge module upgrade issue - by Manas.t

Status : 


Sign in
to vote
ID 566871 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 6/11/2010 3:28:04 PM
Access Restriction Public


I have a product that includes the Microsoft_VC80_ATL_x86.msm (8.0.50727.762) merge module. I have observed that there is an issue with this merge module when my product goes through an upgrade installation. Both versions of the product include the same version of the merge module. Clicking on an advertised shortcut in the start menu results in a resiliency repair.

The application event log reveals:
Detection of product '{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}', feature '<feature_name>', component '{97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}' failed.  The resource '' does not exist. 

The component {97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E} is associated with the ATL80.dll file which goes into "C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c". Normally the last line of the message would point towards the exact deliverable that does not exist. In this case it should have said "The resource ' C:\Windows\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c \ATL80.dll' does not exist.". The missing resource between the single colons leads me to believe that this particular component did install the deliverable but somehow did not register that information properly in the registry, from where the cached MSI most likely obtains information to co-relate the component with the deliverable.

Interestingly this issue happens on on Vista (both x86 and x64) and Server 2008 x64 systems only.

An internet search revealed a couple of posts in some setup community forums where this exact issue has been reported with the exact same merge module (; There are some other related posts as well where this issue has been reported with other MS merge modules (; This leads me to believe that the issue is with the merge module during upgrades with certain versions of windows installer (4.5.x) on certain OS (Vista and Server 2008 x64 only). Installing OS service packs and/or upgrading windows installer may or may not mitigate this issue. 

It will be appreciated if someone from Microsoft can possibly reproduce this in-house and provide a potential solution. This is really a VS2005 runtime issue. However, there doesn't seem to be a forum for VS2005 in Connect. Kindly move this to the right forum if necessary.
Sign in to post a comment.
Posted by Microsoft on 6/11/2010 at 5:05 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(