Microsoft Visual Studio/.Net Framework Setup & Deployment Tips & Tricks

The mounted file system does not support extended attributes

2013-05-06T14:00:00Z

The Microsoft .Net Framework 3.5 SP1 /2.0 SP2 Setup may fail without any error message or the setup may crash almost at the end. You can find the below error messages in the log file:

MSI (s) (00:C8) [10:09:41:999]: Executing op: CustomActionSchedule(Action=CA_InstallAssemblyDef.3643236F_FC70_11D3_A536_0090278A1BB8,ActionType=1025,Source=BinaryData,Target=InstallAssembly,CustomActionData=c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\IEExecRemote.dll;8192)

MSI (s) (00:DC) [10:09:42:092]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI20D.tmp, Entrypoint: InstallAssembly

04/18/13 10:09:42 DDSet_Status: LANGID: 1033

04/18/13 10:09:42 DDSet_Entry: InstallAssembly started

04/18/13 10:09:42 DDSet_Status: CustomActionData: c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\IEExecRemote.dll;8192

04/18/13 10:09:42 DDSet_Status: Loading mscoree.dll

04/18/13 10:09:42 DDSet_Status: Loading fusion.dll using LoadLibraryShim()

04/18/13 10:09:42 DDSet_Error: Failed to install assembly c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\IEExecRemote.dll. IAssemblyCache->InstallAssembly() returned -2147024614.

04/18/13 10:09:42 DDSet_Error: Failed to install assembly 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\IEExecRemote.dll' because of system error: The mounted file system does not support extended attributes.

The error code -2147024614 means ERROR_EAS_NOT_SUPPORTED # the mounted file system does not support extended attributes

I captured a procmon trace http://technet.microsoft.com/en-in/sysinternals/bb896645.aspx and after reviewing the procmon, I found that the failure occurs when performing FSCTL_SET_REPARSE_POINT on the GAC directory for IEExecRemote.dll:

11:03:52.4649173AM MsiExec.exe 3888 FileSystemControl 328 C:\WINDOWS\assembly\GAC_MSIL\IEExecRemote\2.0.0.0__b03f5f7f11d50a3a EAS NOT SUPPORTED Control: FSCTL_SET_REPARSE_POINT

The reparse points are used in hard links (and possibly directory junctions). A hard link is a directory entry that associates a name with a file on a file system. The Hard link is used between win32 assemblies in WinSxS and this particular assembly has a win32 manifest, so that could be why this is happening. None of the previously successfully installed assemblies have win32 manifests, and I found none of them setting reparse points. So we tried to create a hard link on this drive and see if that is supported. In order to do the same I used the tool called junction.exe http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx

C:\>junction.exe c:\test1 c:\test

Error setting junction for c:\test1:

The mounted file system does not support extended attributes.

I also took a procmon trace while running the junction.exe and found the similar behavior like .Net Framework install

06:28:28.2800295 PM junction.exe 3512 FileSystemControl C:\test1 EAS NOT SUPPORTED Control: FSCTL_SET_REPARSE_POINT domain\user1 00000000:0001e183 0

It had the below stack:

0 fltmgr.sys fltmgr.sys + 0x24ca 0xf734c4ca C:\WINDOWS\System32\Drivers\fltmgr.sys

1 fltmgr.sys fltmgr.sys + 0x3f2a 0xf734df2a C:\WINDOWS\System32\Drivers\fltmgr.sys

2 fltmgr.sys fltmgr.sys + 0x48d2 0xf734e8d2 C:\WINDOWS\System32\Drivers\fltmgr.sys

3 fltmgr.sys fltmgr.sys + 0x12693 0xf735c693 C:\WINDOWS\System32\Drivers\fltmgr.sys

4 ntoskrnl.exe ntoskrnl.exe + 0x401d3 0x808401d3 C:\WINDOWS\system32\ntoskrnl.exe

5 ntoskrnl.exe ntoskrnl.exe + 0x12c3f9 0x8092c3f9 C:\WINDOWS\system32\ntoskrnl.exe

6 ntoskrnl.exe ntoskrnl.exe + 0x12c32e 0x8092c32e C:\WINDOWS\system32\ntoskrnl.exe

7 ntoskrnl.exe ntoskrnl.exe + 0x1397ef 0x809397ef C:\WINDOWS\system32\ntoskrnl.exe

8 ntoskrnl.exe ntoskrnl.exe + 0x33c3f 0x80833c3f C:\WINDOWS\system32\ntoskrnl.exe

9 junction.exe junction.exe + 0x294a 0x40294a C:\1A1\Net Updates\19APR\Junction\junction.exe

The error message comes from STATUS_EAS_NOT_SUPPORTED => ERROR_EAS_NOT_SUPPORTED. This is the error code returned by NTFS when you try to set a reparse point on a file that already has EAs on it. (Reparse points and EAs cannot coexist on the same file.) Hence, I generated the list of file system filters present on the system. So we ran the below command:

C:\>fltmc filters

Filter Name Num Instances Frame

------------------------------ --------------------- ----------

EzWatch 1 1

BHDrvx86 1 1

eeCtrl 1 1

SRTSP 3 1

DfsDriver <Legacy>

SymEFA 3 0

C:\>fltmc instances

Filter Volume Name Altitude Instance Name

-------------- --------------------- ------------- -----------------------

EzWatch C: 370030 EzWatch Instance

BHDrvx86 C: 365100 BHDrvx86

eeCtrl C: 329010 eeCtrl

SRTSP C: 329000 SRTSP

SRTSP \Device\LanmanRedirector 329000 SRTSP

SRTSP \Device\RdpDr 329000 SRTSP

SymEFA C: 260600 SymEFA

SymEFA \Device\LanmanRedirector 260600 SymEFA

SymEFA \Device\RdpDr 260600 SymEFA

In the above list DfsDriver is the only filter driver which is owned by Microsoft and the remaining all are Third party filter drivers. We tried removing the filters one at a time and after each removal and tried the junction scenario until we find when it stops working. In order to remove the filter driver, I opened an Admin command prompt and ran the below commands:

For EzWatch

sc config EzWatch start= disabled

For BHDrvx86

sc config bhdrvx86 start= disabled

For eeCtrl

sc config eectrl start= disabled

For SRTSP:

sc config srtsp start= disabled

For SymEFA

sc config symefa start= disabled

In this way I found that EzWatch was the file system filter driver which caused setting the junction though the file system was NTFS. In the same way it caused the .Net Framework Setup failure. Disabling EzWatch filter driver resolved the issue.

To re-enable them the process is similar, just use start= system

For example: sc config bhdrvx86 start= system

Also we can make the above changes in the registry in this path for each driver by changing their start value from 0 (boot) or 1 (system) to 4 (disabled): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services

MBSA 2.2 scanning tool reoffering KB 2538243, even after a successful installation on the machine

2013-04-29T20:52:03Z

This week we worked on a customer case, where we found that the computer was being scanned vulnerable by Microsoft Base Line Security Analyzer tool (MBSA 2.2).

Issue Description:

MBSA 2.2 scanning tool is reoffering KB2538243, even though it has been already installed on the machine.

Cause:

We worked on computer and found that the VC ++ Security update KB2538243 provided as a part of Security bulletin MS11-025 was getting reoffered.

Security Bulletin page: http://technet.microsoft.com/en-us/security/bulletin/ms11-025

KB describing the file versions: http://support.microsoft.com/kb/2538243

Link to download files: http://www.microsoft.com/en-us/download/details.aspx?id=26368

Resolution:

Since the computer was x64 bit OS, the customer had only installed the x64 file from the download page. Though the installation looked OK(as per the verbose logs located under the %temp% folder), the MBSA would still say that the update is missing.

Going back to the download page, we found three types of installer files: x86, x64 and IA64.

With the OS in this case having an X64 architecture, we could have both x86 and x64 editions of Visual C++ redistributables installed on the machine. Visual C++ is a commonly used component for various applications and it is normal to have 32 bit and 64 bit runtime installed on a 64 bit system.

Since the customer had only one version of the VC++ installed, they were being offered KB2538243 to be installed on the computer.

We decided to download both the x86 and x64 versions of the VC++ runtime and installed it. Once both were installed, the MBSA did not show the vulnerability anymore.

Content by: Ajith Thomas

A custom deployment of ClickOnce application starts the reinstallation process every time the user logs off and logs back again

2013-04-29T20:35:47Z

While working on customer case, I came across an interesting issue with an application deployed using ClickOnce.

Issue Description:

A custom deployment of ClickOnce application starts the reinstallation process every time the user logs off and logs back again.

Cause:

We worked on the machine and found the following registry key that belongs to the ClickOnce isolation store was getting deleted during each logoff.

HKEY_CURRENT_USER\Software\Classes\Software\Microsoft\Windows\CurrentVersion\Deployment\SideBySide\2.0\PackageMetadata

When the user is logged in, a handle is created for the HKCU\Software\Classes hive, if a logoff could not unload this hive properly, it might get corrupted or hold incorrect data. This leads to get the corrupted data loaded back during logon.

In our case there was a problem with a single User Profile. These registry keys were getting removed or modified and was triggering the re-installation.

In a normal scenario, these registry keys do not get removed or modified, that provides the persistence to the application deployed using ClickOnce. In other words no re-installation occurs until there is a new update that is available and needs to be installed.

Possible Resolution:

System processes and applications occasionally maintain connections to registry keys in the UserProfile, even after a user logs off. In such cases, the user session fails to end entirely. When you use roaming user profiles in a network environment, this can result in problems like deletion or modification of registry hives.

To resolve this problem, install Microsoft User Profile Hive Cleanup Service (UPHClean). UPHClean monitors the computer while you log off, and then UPHClean unloads UserProfiles. The User Profile Hive Cleanup service helps us to make sure that user sessions are completely ended when a user logs off. (http://msdn.microsoft.com/en-us/library/aa910532.aspx)

The User Profile Hive Cleanup service monitors for users who have logged off and for whom registry hives are still loaded. When this occurs, the service determines which applications have handles that are opened to the hives and releases them. It logs the application name and what registry keys were left open. After this occurs, the system finishes unloading the profile.

For more information and for installing User profile Hive cleanup service we recommend the following KB: http://support.microsoft.com/kb/837115

Content by: Ajith Thomas

Error message “MSBuild.exe is not a valid Win32 application” is shown while trying to build using MSBuild.exe.

2013-04-26T01:56:30Z

While working on a recent customer case, we observed the following error message, MSBuild.exe is not a valid Win32 application.

Issue Description:

A project is build using the MSBuild.exe and the following error message is shown.

OS Environment:

Windows 7/Server 2008 R2/ Windows XP/ Server 2003 R2/ Server 2003 (with .NET Framework 4.0 Full installed)

Symptom and inference:

We started the troubleshooting by checking the size, digital signature and other attributes of the file “C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe”. In our case size of the file was 0 KB. Verified the same file in the other folder “C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe” and found the size was 129 KB (132,432 bytes). Which clearly indicates that the file ‘MSBuild.exe’ was corrupted.

Solution:

In order to fix this issue, the file was renamed to “MSBuild.exe.old” and then we started the repair of .NET Framework 4.0 Client Profile from ‘Programs and Features’. This process was able to replace the corrupted MSBuild.exe file with a new one.

A computer reboot may be necessary, if prompted by the setup, the computer must be restarted.

Verification:

The build process worked as expected after the repair and reboot.

Content by:
Keshav Jain.

Install cannot continue because some required components failed

2013-04-18T07:38:13Z

Microsoft Visual Studio 2012 Setup may fail on Windows 7 system with the below error screenshot:

As per the Setup failure log (dd_vs_***_58*****875_vs_professionalcore.log):

MSI (s) (A4:48) [18:08:37:579]: Executing op: CustomActionSchedule(Action=RollbackHttp.992B75DB_179A_4B48_B260_9FD0862C9A76,ActionType=3329,Source=BinaryData,Target=Uninstall,)
MSI (s) (A4:48) [18:08:37:580]: Executing op: ActionStart(Name=ReserveHttp.992B75DB_179A_4B48_B260_9FD0862C9A76,,)
MSI (s) (A4:48) [18:08:37:581]: Executing op: CustomActionSchedule(Action=ReserveHttp.992B75DB_179A_4B48_B260_9FD0862C9A76,ActionType=3073,Source=BinaryData,Target=Install,)
MSI (s) (A4:A8) [18:08:37:605]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIA1BF.tmp, Entrypoint: Install
04/15/13 18:08:37 DDSet_Entry: WcfToolsInstall
04/15/13 18:08:37 DDSet_Status: HttpReservation::PerformInstall
04/15/13 18:08:37 DDSet_Status: HttpReservation::IsInstalled
04/15/13 18:08:37 DDSet_Status: HttpLibrary::HttpInitialize
MSI (s) (A4!E8) [18:08:37:646]: Product: Microsoft Visual Studio Professional 2012 -- 04/15/13 18:08:37 DDSet_Error: Internal error: 1060.

I tried the below steps:

C:\>netsh http show urlacl

URL Reservations:
-----------------
The handle is invalid.

C:\>net start http
The service name is invalid.

I ran httpcfg.exe tool http://technet.microsoft.com/en-us/library/cc787508%28WS.10%29.aspx

c:\>httpcfg.exe set urlacl -u http://+:80/Temporary_Listen_Addresses/ -a DSadA;;GX;;;WD)

HttpInitialize failed with 1060.

C:\>net helpmsg 1060
The specified service does not exist as an installed service.

So I checked the HTTP driver properties and found that both Start & Stop buttons were disabled as shown below:

To open HTTP driver properties, please follow the steps indicated below:

1. Open Device Manager.
2. Click the View menu, and then click Show hidden devices.
3. In the list of devices, double-click Non-Plug and Play Drivers, right-click the device you want, and then click Properties.
4. On the Driver tab, click Start or Stop, and then click OK.

The above issue clearly indicated HTTP driver was not functional. After further debugging, I found that it was due to missing 32 bit Start DWORD value in the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP (below screenshot). Hence, I created it manually and rebooted the system.

Then I was able to install the Microsoft Visual Studio 2012 successfully on the system.

MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.

2013-04-05T04:28:10Z

You may find the below error message while trying to create or build a VC++ (Win32/MFC/ATL) project in Microsoft Visual Studio 2012:

MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.

Please check the following reg keys (I printed what should be there and nothing else):

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0]
"MSBuildToolsPath"="C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\"
"MSBuildToolsRoot"="C:\\Windows\\Microsoft.NET\\Framework64\\"
"FrameworkSDKRoot"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.0A@InstallationFolder)"
"MSBuildRuntimeVersion"="4.0.30319"
"SDK40ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.0A\\WinSDK-NetFx40Tools-x86@InstallationFolder)"
"SDK35ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Microsoft SDKs\\Windows\\v7.0A\\WinSDK-NetFx35Tools-x86@InstallationFolder)"
"MSBuildToolsPath32"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\MSBuild\\ToolsVersions\\4.0@MSBuildToolsPath)"
"VCTargetsPath"="$(MSBuildExtensionsPath32)\\Microsoft.Cpp\\v4.0\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0\11.0]
"FrameworkSDKRoot"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Microsoft SDKs\\Windows\\v8.0A@InstallationFolder)"
"SDK40ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Microsoft SDKs\\Windows\\v8.0A\\WinSDK-NetFx40Tools-x86@InstallationFolder)"
"SDK35ToolsPath"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Microsoft SDKs\\Windows\\v8.0A\\WinSDK-NetFx35Tools-x86@InstallationFolder)"
"WindowsSDK80Path"="$(Registry:HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Microsoft\\Microsoft SDKs\\Windows\\v8.0@InstallationFolder)"
"VCTargetsPath"="$([MSBuild]::ValueOrDefault('$(VCTargetsPath)','$(MSBuildExtensionsPath32)\\Microsoft.Cpp\\v4.0\\v110\\'))"
"VCTargetsPath10"="$([MSBuild]::ValueOrDefault('$(VCTargetsPath10)','$(MSBuildExtensionsPath32)\\Microsoft.Cpp\\v4.0\\'))"
"VCTargetsPath11"="$([MSBuild]::ValueOrDefault('$(VCTargetsPath11)','$(MSBuildExtensionsPath32)\\Microsoft.Cpp\\v4.0\\V110\\'))"

If the above settings are already set properly, then check if you have VCTargetsPath set as a global environment variable. If it is set system wide, then remove it as this is what might cause the above issue. On my system it was set as mentioned below:

VCTargetsPath=C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0

Installation of .net framework 3.5 sp1 fails with error codes 1714 and 1612

2013-03-26T13:50:32Z

ISSUE DESCRIPTION: The installation of .NET Framework 3.5 SP1 fails with errors 1714 and 1612 on a machine that already has .NET Framework 3.5 installed (with corresponding source files missing under the installer cache).

ENVIRONMENT: Windows Server2003/ Windows XP

Symptom and inference:

The installation of .net framework 3.5 sp1 fails during the installation.

Having enabled windows installer verbose logging on the machine (http://support.microsoft.com/kb/223300) you will see the following as part of the newly formed .net framework 3.5 sp1 failed installation log:

----------------------------------------------------------------------------------------------------------------

MSI (s) (24:FC) [02:54:11:910]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (24:FC) [02:54:11:910]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (24:FC) [02:54:11:910]: Note: 1: 1706 2: -2147483647 3: Netfx20a_x86.msi
MSI (s) (24:FC) [02:54:11:910]: SOURCEMGMT: Processing URL source list.
MSI (s) (24:FC) [02:54:11:910]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (24:FC) [02:54:11:910]: Note: 1: 1706 2: -2147483647 3: Netfx20a_x86.msi
MSI (s) (24:FC) [02:54:11:910]: Note: 1: 1706 2: 3: Netfx20a_x86.msi
MSI (s) (24:FC) [02:54:11:910]: SOURCEMGMT: Failed to resolve source
MSI (s) (24:24) [02:54:11:910]: Note: 1: 1714 2: Microsoft .NET Framework 2.0 Service Pack 2 3: 1612 MSI (s) (24:24) [02:54:11:957]: Product: Microsoft .NET Framework 2.0 Service Pack 2 -- Error 1714.The older version of Microsoft .NET Framework 2.0 Service Pack 2 cannot be removed. Contact your technical support group. System Error 1612.

Error 1714.The older version of Microsoft .NET Framework 2.0 Service Pack 2 cannot be removed. Contact your technical support group. System Error 1612.
MSI (s) (24:24) [02:54:11:957]: User policy value 'DisableRollback' is 0
MSI (s) (24:24) [02:54:11:957]: Machine policy value 'DisableRollback' is 0
Action ended 2:54:11: RemoveExistingProducts. Return value 3.

----------------------------------------------------------------------------------------------------------------

.NET Framework 3.5 SP1 is a major upgrade for .NET Framework 3.5 and so it tries to remove the older version i.e .NET Framework 3.5 during the installation.

.NET Framework 3.5 is a cumulative update for .NET Framework 2.0 SP1 , .NET Framework 3.0 SP1 and .Net Framework 3.5, where in .Net Framework 3.5 SP1 is the cumulative update for the .NET framework 2.0 SP2, .NET Framework 3.0 SP2 and .NET Framework 3.5 SP1.
So during the installation of .NET 3.5 SP1, it tries to uninstall .NET 2.0 SP1 , .NET 3.0 SP1 and .NET 3.5, however it was unable to do so due to missing source file from the installer cache evident by:

MSI (s) (24:FC) [02:54:11:910]: SOURCEMGMT: Failed to resolve source

RESOLUTION: To fix the issue, one needs to remove the .NET Framework 3.5, .NET Framework 3.0 SP1 , .NET Framework 3.5 using the .NET framework removal tool or the Uninstall utility.

Content by: Keshav Deo Jain

Visual Studio 2010 throws package load errors on launch and creation of new project fails

2013-03-21T13:57:00Z

ISSUE DESCRIPTION:

Visual Studio 2010 throws package load errors on launch and creation of new project in fails with more errors

ENVIRONMENT:

This is applicable to both 32 bit and 64 bit machines, running Windows 8/Widows 7/ Server 2012/ Server 2008/ Windows Server2003/ Windows XP

Symptom and inference:

Here is the error message that you will notice on launching Visual Studio:

Also, when you still go ahead and try to create a new project, it immediately fails with these error messages:

This happens because of Visual Studio is trying to load extensions that do no exist on the machine! (Well, at least not at the path that it is looking at).

Also, you will notice that in the IDE the Extension manager cannot be accessed. You get this error:

Resolution:

To resolve this, navigate following registry key, and make sure that the given paths (string values listed under this key) are valid.

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\ExtensionManager\EnabledExtensions

Alternately, you can just disable the extension if path does not exist if you are unsure of what the exact path needs to be. Later of course you can get this extension installed back again.

Here is how I was able to reproduce the issue, by prefixing the key under EnabledExtensions with ‘old_’

Content by

Ritwik Sinha

Visual Studio 2012 IDE shows “Failed to create a 'ImageSource' from the text '..\Images\Medium.png'. while accessing file New / file Open dialog boxes.

2013-03-19T01:04:00Z

Recently we worked on an interesting issue with a new installation of Visual Studio 2012. Where the IDE would open but trying create a new project or opening an existing project using the File > Open menu would fail with error an error message. Trying to use the Key board shortcut Ctrl + Shift + N would show the same dialog box with the following error message.

---------------------------
Microsoft Visual Studio
---------------------------

Failed to create a 'ImageSource' from the text '..\Images\Medium.png'.

---------------------------
OK
---------------------------

Note: Most of the error message dialog boxes allow the txt to be copied. Just press Ctrl + C to copy the text and then paste in email or notepad.

In this scenario, customer had Visual Studio 2008 and Visual Studio 2010 installed on the machine earlier. Then he said Visual Studio 2012 was installed. It was working fine, until he installed the Office 2013.

Per discussion, the picture viewing software got affected. He mentioned that the Print Screen copy and paste into the MS word would not work etc.

While searching on the internet we came across the following two links.

http://stackoverflow.com/questions/12257817/visual-studio-2012-failed-to-create-project

http://www.fastpictureviewer.com/forum/viewtopic.php?f=11&p=3806

On examining the computer we found that the computer had “FastPictureViewer Codec Pack 2.4” installed on the machine.

Latest version of the “FastPictureViewer” mentioned here on the web site http://www.fastpictureviewer.com/codecs/ is “FastPictureViewer” 3.4.

We discussed about the issue and as it was not very clear how this “FastPictureViewer Codec Pack 2.4” got installed on the machine. As there was no requirement we decided to uninstall the Viewer.

That required the machine to restarted for clean uninstall.

Once the machine was restarted, the Visual Studio IDE 2012 issue was resolved. There were no error messages shown on the IDE start.

Possibly, installing the “FastPictureViewer Codec Pack 3.4” could also be able to resolved the issue if Code pack is need.

Happy coding!!

Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) 'package'. MSI returned error code 1603

2013-03-18T13:57:24Z

The Microsoft .Net Framework 3.5 SP1 Setup may fail without any error message or the setup may crash almost at the end. You can find the below error messages in the log file:

[01/20/13,05:32:37] Microsoft .NET Framework 3.5 (x64) 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 (x64) 'package'. MSI returned error code 1603
[01/20/13,05:32:49] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 (x64) 'package' is not installed.

In the detail log file (dd_NET_Framework35_x64_MSI****.txt) at %temp% location, it had more information on the failure as mentioned below:

DDSet_Status: CExtensionElement::SetData szName=webHttp szType=System.ServiceModel.Configuration.WebHttpElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 szXPath=system.serviceModel/extensions/behaviorExtensions/add
DDSet_Status: CFxInstaller::SetupExtensions Adding System.ServiceModel.Configuration.WebHttpElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
DDSet_Status: CExtensionElement::AddToConfigFile _xPath=system.serviceModel/extensions/behaviorExtensions/add
DDSet_Status: CConfigEntry::IsPresent szPath=system.serviceModel/extensions/behaviorExtensions/add
DDSet_Status: CFxInstaller::SetupExtensions extensionElement.AddToConfigFile failed. value=System.ServiceModel.Configuration.WebHttpElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Error code: 0x80004005.
DDSet_Status: CExtensionElement::SetData szName=webMessageEncoding szType=System.ServiceModel.Configuration.WebMessageEncodingElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 szXPath=system.serviceModel/extensions/bindingElementExtensions/add
DDSet_Status: CFxInstaller::SetupExtensions Adding System.ServiceModel.Configuration.WebMessageEncodingElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
DDSet_Status: CExtensionElement::AddToConfigFile _xPath=system.serviceModel/extensions/bindingElementExtensions/add
DDSet_Status: CConfigEntry::IsPresent szPath=system.serviceModel/extensions/bindingElementExtensions/add
DDSet_Status: CFxInstaller::SetupExtensions extensionElement.AddToConfigFile() failed. Value=System.ServiceModel.Configuration.WebMessageEncodingElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, Error code: 0x80004005

After my initial review, I found that that the issue occurred due to the below lines being added in the 32-bit web.config file located at C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG

In general the <compilation tempDirectory…> is never set to a value like this. It used to be always under C:\Windows\Microsoft.NET\v2.0.50727\Temporary ASP.NET files. Later, I found WFServicesReg was barfing because the config file already contained the elements needed in the file so it was not able to re-add them, hence the failure code. Finally, I was able to resolve the issue after replacing the web.config files by web.config.default in both the locations (x86/x64 <C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG and C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG>. When I replaced the web.config with the default one, this allowed WFServicesReg to proceed as the elements weren’t there to begin with. The Microsoft .Net Framework 3.5 SP1 was installed successfully.

N.B.: Please take a back up of web.config files before replacing them. You may also have to repair applications which add custom entries in web.config files.