Customers have commented that whenever they try to install other products or patches they continually see the following message,<\/p>\n
\nAnother installation is in progress. You must complete that installation before continuing this one.<\/p>\n<\/blockquote>\n
Customers may also see instances of msiexec.exe or msiexec.exe*32 appear continuously in Task Manager or other process monitoring software.<\/p>\n
This may occur after installing either Visual Studio 2008 or Visual Studio 2010 Beta 1. If you look in your Application event log as described below, for the MsiInstaller source you may see a message like either of the following,<\/p>\n
\nDetection of product ‘{AA4A4B2C-0465-3CF8-BA76-27A027D8ACAB}’, feature ‘VSTA_IDE_12590_x86_enu’, component ‘{FF4A39EF-8F8B-4557-9F81-50DC44C6D30A}’ failed. The resource ‘c:\\Program Files (x86)\\Microsoft Visual Studio 9.0\\Common7\\IDE\\PublicAssemblies\\en\\’ does not exist.<\/p>\n<\/blockquote>\n
Or,<\/p>\n
\nDetection of product ‘{874D5E2B-AACE-303A-B3EC-2563E071473E}’, feature ‘VS_IDE_657_x86_enu’, component ‘{A5854250-7B92-4A50-935F-6A486589F87D}’ failed. The resource ‘d:\\Program Files\\Microsoft Visual Studio 10.0\\Common7\\IDE\\PublicAssemblies\\en\\’ does not exist.<\/p>\n<\/blockquote>\n
In either case, some of the quoted values may be different but the path may still reference \u201cMicrosoft Visual Studio 10.0\\Common7\\IDE\\PublicAssemblies\\en\u201d.<\/p>\n
How to work around this issue<\/h3>\n
To determine if the issue affecting you is the one described here, you must start the event viewer. This is also necessary to identify the missing resource, if any, that needs to be created.<\/p>\n
\n
- Click on Start<\/b> <\/li>\n
- Click on Run<\/b> <\/li>\n
- Type \u201ceventvwr\u201d (without quotes) and click OK<\/b>. If you are prompted to elevated on Vista or newer, click Continue<\/b>. <\/li>\n
- Expand Windows Logs<\/b> and click Application<\/b> <\/li>\n
- Find the recent warning where the Source is MsiInstaller. In Vista and newer,\n
\n
- Click Filter Current Log\u2026<\/b> in the right action pane <\/li>\n
- Check Warning<\/b> <\/li>\n
- Type \u201cMsiInstaller\u201d (without quotes) in the Event sources<\/b> edit control <\/li>\n
- Type \u201c1004\u201d (without quotes) in the event IDs edit control <\/li>\n
- Click OK<\/b> <\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
I’ve also attached an event viewer filter you can unzip and import as a custom view.<\/p>\n
You should see a message similar to those above, stating stating that a directory like \u201cC:\\Program Files\\Microsoft Visual Studio 10.0\\Common7\\IDE\\PublicAssemblies\\en\\\u201d does not exist. If you do not find such a message, you might search for event ID 1001 as logged during a similar event<\/a>.<\/p>\n
To work around this particular issue, simply create the directory that is missing.<\/p>\n
<\/h3>\n
Description of the issue<\/h3>\n
This is another example of the potential problems when advertising Windows Installer features<\/a>. When COM registration is advertised, serialized data identifying the product feature that provides the COM server is written to the registry. When the class loader reads this value in this format that identifies a Windows Installer product feature, Windows Installer is queried for the component path which starts a resiliency check<\/a> against the feature.<\/p>\n
Because in this case a directory is missing for a component, Windows Installer logs an event and begins a maintenance installation to repair affected features. If you cancel this repair operation the issue will continue to surface. If allowed to continue, you might be prompted for source. However, unlike another example of a similar event<\/a>, repairing the product will not resolve the issue.<\/p>\n
As described for ICE18<\/a>, a component that does not have a key path set must declare a related entry in the CreateFolder<\/a> table. Of course, a versioned file is always preferred as a key path for a component if available, but an unversioned file or registry value will suffice.<\/p>\n
So because the component referenced in the event log does not declare a key path nor create the \u201cen\u201d sub-directory, a repair triggered by a resiliency check will always be performed. And because only one Windows Installer transaction can run at a time, other Windows Installer installations are blocked.<\/p>\n