Skip to main content

Error 1937 - Visual Studio 2010 Ultimate Beta 2 Setup Failed - ERROR:Error 1937.An error occurred during the installation of assembly 'FSharp.Compiler

I face following issue while installing Visual Studio 2010 Beta 2 on Windows 7. I turn off the Norton Antivirus and re-run the Visual Studio 2010 Beta 2 installer. Also I uncheck the F# as log file show the error is related to F#.

I will try it to install it again meanwhile wanted to as if anyone face the similar issue or able to install F# with no issue.   Thanks for your help.

image

C:\Users\<username>\AppData\Local\Temp\dd_error_vs_vstscore_100.txt

[11/07/09,19:17:58] Microsoft Visual Studio 2010 Ultimate Beta 2 - ENU: [2] ERROR:Error 1937.An error occurred during the installation of assembly 'FSharp.Compiler,version="4.0.0.0",publicKeyToken="b03f5f7f11d50a3a",processorArchitecture="MSIL",fileVersion="4.0.21006.1",culture="neutral"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. 
[11/07/09,19:18:00] Microsoft Visual Studio 2010 Ultimate Beta 2 - ENU: [2] ACTION FAILURE:Action ended 19:17:59: InstallFinalize. Return value 3.See MSI log for details.
[11/07/09,19:21:06] Microsoft Visual Studio 2010 Ultimate Beta 2 - ENU: [2] ACTION FAILURE:Action ended 19:21:06: INSTALL. Return value 3.See MSI log for details.
[11/07/09,19:28:08] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InternalInstallManager() with HRESULT -2147023293.
[11/07/09,19:28:11] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2010 Ultimate Beta 2 - ENU is not installed.
[11/07/09,19:28:11] VS70pgui: [2] DepCheck indicates Microsoft Web Deployment Tool (x86) was not attempted to be installed.
[11/07/09,19:28:11] VS70pgui: [2] DepCheck indicates Microsoft ASP.NET MVC 2 - Visual Studio 2010 Tools was not attempted to be installed.
[11/07/09,19:28:12] VS70pgui: [2] DepCheck indicates Microsoft ASP.NET MVC 2 was not attempted to be installed.
[11/07/09,19:28:12] VS70pgui: [2] DepCheck indicates Microsoft Silverlight was not attempted to be installed.
[11/07/09,19:28:12] VS70pgui: [2] DepCheck indicates Microsoft Silverlight 3 SDK was not attempted to be installed.
[11/07/09,19:28:12] VS70pgui: [2] DepCheck indicates Visual Studio 2010 Tools for Office Runtime Beta 2 (x86) was not attempted to be installed.
[11/07/09,19:28:12] VS70pgui: [2] DepCheck indicates Microsoft Office Development Tools for Visual Studio 2010 (x86) was not attempted to be installed.
[11/07/09,19:28:13] VS70pgui: [2] DepCheck indicates Dotfuscator Software Services - Community Edition was not attempted to be installed.
[11/07/09,19:28:13] VS70pgui: [2] DepCheck indicates Crystal Reports templates for Visual Studio 2010 was not attempted to be installed.
[11/07/09,19:28:13] VS70pgui: [2] DepCheck indicates Microsoft SQL Server Compact 3.5 SP2 Beta ENU was not attempted to be installed.
[11/07/09,19:28:14] VS70pgui: [2] DepCheck indicates Visual Studio 2010 Beta 2 Tools for SQL Server Compact ENU was not attempted to be installed.
[11/07/09,19:28:14] VS70pgui: [2] DepCheck indicates Microsoft Sync Framework Runtime v1.0 (x86) ENU was not attempted to be installed.
[11/07/09,19:28:14] VS70pgui: [2] DepCheck indicates Microsoft Sync Services for ADO.NET v2.0 (x86) ENU was not attempted to be installed.
[11/07/09,19:28:14] VS70pgui: [2] DepCheck indicates Microsoft Sync Framework Services v1.0 (x86) ENU was not attempted to be installed.
[11/07/09,19:28:15] VS70pgui: [2] DepCheck indicates Microsoft Sync Framework SDK v1.0 (x86) ENU was not attempted to be installed.
[11/07/09,19:28:15] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2010 Performance Collection Tools (x86) was not attempted to be installed.
[11/07/09,19:28:15] VS70pgui: [2] DepCheck indicates Microsoft SQL Publishing Wizard 1.4 was not attempted to be installed.
[11/07/09,19:28:15] VS70pgui: [2] DepCheck indicates SQL Server System CLR Types was not attempted to be installed.
[11/07/09,19:28:16] VS70pgui: [2] DepCheck indicates SQL Server 2008 R2 Management Objects was not attempted to be installed.
[11/07/09,19:28:16] VS70pgui: [2] DepCheck indicates Data-tier Application Component Framework was not attempted to be installed.
[11/07/09,19:28:16] VS70pgui: [2] DepCheck indicates Data-tier Application Component Project System was not attempted to be installed.
[11/07/09,19:28:16] VS70pgui: [2] DepCheck indicates Transact-SQL Language Service was not attempted to be installed.
[11/07/09,19:28:17] VS70pgui: [2] DepCheck indicates Microsoft SharePoint Development Tools was not attempted to be installed.
[11/07/09,19:28:17] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2010 ADO.NET Entity Framework Tools was not attempted to be installed.
[11/07/09,19:28:17] VS70pgui: [2] DepCheck indicates Microsoft Help 3.0 Beta 2 was not attempted to be installed.
Labels:

Comments

Post a Comment

Popular posts from this blog

SharePoint WebPart Error - Unable to add selected web part (s) – MOSS 2007

ISSUE: Recently I faced this issue that when I try to deploy my WebPart.  Unable to add selected web part(s). WebPartName: Cannon unregister UpdatePanel with ID ‘ctl00RTMPanel’ since it was not registerd with the ScripManager. This might occure if the UpdatePanel was removed from the control tree and later added again, which is not supported. Parameter name: updatePanel.   I faced this issue twice and both the time the issue was not what display here. This could be sure to any error in the WebPart. Following are list resolution from multiple instances.   RESOLUTION: 1. Check the WebPartName.webpart file. Check whether you have a proper PublicKeyToken value. When I face the issue the value was PublicKeyToken=$PublicKeyToken$. If you have used WSP builder then in the Visual Studio you will find this file at \WebPartsProject\12\TEMPLATE\FEATURES\WebPartName\WebPartName.webpart. Sometime when you create a new WebPart using WSP builder then you do not get
4 comments
Read More >>>

Could not open virtual machine – vmx is not a valid virtual machine configuration file

I recently faced an issue with one of my VMWare virtual machine that when I try to run this virtual machine it did not work. VMWare display this message that “Could not open virtual machine: .vmx. ".vmx" is not a valid virtual machine configuration file.” ISSUE: Could not open virtual machine: G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx. "G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx" is not a valid virtual machine configuration file. I try to open .vmx file [G:\VPC\RakhiQAXPProfQtp\Windows XP Professional.vmx] in notepad then I found it was empty (0 KB). Resolution: I wanted to resolve it quickly so I try following method and it worked very well. But this is not a valid documented process so please try with caution. Following are the steps 1. First of all go to the folder where you have your virtual machine and delete all .lck folders. 564df2d4-03de-04e8-d1c3-bd2d53dcb1b7.vmem.lck Windows XP Professional.vmdk.lck
13 comments
Read More >>>

How To Create Virtual Machine Using Existing vmdk file in VMWare Workstation

vmdk file is hard disk of the VMWare virtual machine. There are many scenarios where you may need to create a new virtual machine for an existing vmdk file. This is also an alternate Method to the “ vmx is not a valid virtual machine configuration file – Could not open virtual machine ” issue. Please refer to the previous post “ Could not open virtual machine – vmx is not a valid virtual machine configuration file ” for a full list of possible resolution. This post is to describe one of the solution in more details. How To Create a new virtual machine & attach the existing .vmdk file: 1. Open VMware and select create a new virtual machine with custom (advanced) configuration option. 2. Chose “I will install the operating system later”. and chose “I will install the operating system later”. 3. Select the operating system that matches the operating system in your existing .vldk file. 4. Select a location of the new virtual machine 5. Chose “Use an exis
8 comments
Read More >>>