Knowledge Base - Technical Articles


Technical Article   Error:  Error 1935. An error occurred during the installation of assembly 'Microsoft VC90.OpenMP,processorArchitecture="x86",publicKeyToken="1fc8b9a1e18e3b"

Article ID: 37477
Software:  ArcInfo Workstation 9.3, 9.3.1, 10 ArcSDE 9.3.1, 10, 10.1, 10.2 ArcGIS - ArcEditor 9.3, 9.3.1, 10 PLTS 9.3.1, 10 ArcGIS - ArcInfo 9.3, 9.3.1, 10 ArcGIS - ArcView 9.3, 9.3.1, 10 ArcReader 9.3, 9.3.1, 10, 10.1, 10.2 ArcGIS Server (10.0 and prior) 9.3, 9.3.1, 10 ArcGIS Engine Developer Kit 9.3, 9.3.1, 10, 10.1, 10.2, 10.2.1 ArcGIS Engine Runtime 9.3, 9.3.1, 10 ArcGIS Image Server 9.3.1, 10 ArcGIS Explorer 900, 1200, 1500, 1700, 1750 Military Overlay Editor 9.3.1, 10 GIS Portal Toolkit 9.3 ArcGIS Business Analyst Server 9.3.1 ArcGIS Server Geoportal extension 9.3.1, 10 ArcGIS for Desktop Advanced 10.1, 10.2, 10.2.1 ArcGIS for Desktop Standard 10.1, 10.2, 10.2.1 ArcGIS for Desktop Basic 10.1, 10.2, 10.2.1 ArcGIS for Server 10.1, 10.2, 10.2.1, 10.2.2
Platforms:  Windows Windows 7

Error Message

When installing ArcGIS products on Windows 7, the following error message is returned:

"Error 1935. An error occurred during the installation of assembly 'Microsoft VC90.OpenMP,processorArchitecture="x86",publicKeyToken="1fc8b9a1e18e3b",version='9.0.21022.8,"type="win32". Please refer to Help and Support for note information."

This error message can also be related to the following error message:

"ArcGIS Desktop has encountered a serious application error and is unable to continue",

or it can be an error similar to:

"hresult 0x800736fd",

after the install of Microsoft SQL Server 2008 Native Client.

Cause

The error is returned when an incorrect registry setting prevents the Windows Modules Installer from running. The issue may be associated with Microsoft .NET Framework 3.5., but may also occur when installing other Microsoft products, such as MS Office.

This issue may be related to one or more of the following symptoms:

• When installing applications, error messages involving OpenMP are displayed, and the installation fails with a rollback:

Product: Microsoft Visual C++ 2005 Redistributable -- Error 1935. An
error occurred during the installation of assembly
'Microsoft.VC80.OpenMP,type="win32",version="8.0.50727.762",publicKeyTok
en="1fc8b3b9a1e18e3b",processorArchitecture="x86"'. Please refer to Help
and Support for more information. HRESULT: 0x800736FD. assembly
interface: IAssemblyCacheItem, function: Commit, component:
{1E507087-0819-45E0-A01F-C8B3B9A1E18E}

• Installing applications or trying to run Windows Update causes the
following entries to be added to the System log in Event Viewer:

The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with
DCOM within the required timeout.

The Windows Modules Installer service terminated with the following
error: Insufficient system resources exist to complete the requested
service.

Application popup: Windows - Low On Registry Space: The system has
reached the maximum size allowed for the system part of the registry.
Additional storage requests will be ignored.

• When trying to make changes to the Windows configuration the 'Turn Windows Features On and Off' dialog box is empty.

• Open the %windir%\logs\cbs directory and the cbs.log file. Look for failures concerning the TrustedInstaller initialization. The error might look something like this:

2009-08-27 00:05:20, Info CBS Starting TrustedInstaller initialization.
2009-08-27 00:05:20, Info CBS Loaded Servicing Stack v6.1.7600.16385
with Core: C:\Windows\winsxs\x86_microsoft-windows-
servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\cbs
core.dll
2009-08-27 00:05:20, Info CBS Failed to load the COMPONENTS hive from
'C:\Windows\System32\config\COMPONENTS' into registry key
'HKLM\COMPONENTS'.

[HRESULT = 0x800705aa - ERROR_NO_SYSTEM_RESOURCES]
2009-08-27 00:05:20, Info CBS Failed to load WCP DLL. [HRESULT =
0x800705aa - ERROR_NO_SYSTEM_RESOURCES]
2009-08-27 00:05:20, Info CBS Failed to initialize the Core DLL:
C:\Windows\winsxs\x86_microsoft-windows-
servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\cbs
core.dll [HRESULT = 0x800705aa -

This issue may be confirmed if any of the above symptoms are encountered, and one or more of the following tests fails:

Test 1. Run the .NET Framework Setup Verification Tool. For more information or to download the .NET Framework Setup Verification Tool, click on the following link: .NET Framework Setup Verification Tool User's Guide.

After running the .NET Framework Setup Verification Tool, there should be three Frameworks listed: 2.0 SP2, 3.0 SP2, and 3.5 SP1.

Validate each Framework starting with 2.0 SP2, then 3.0 SP2, and lastly 3.5 SP1. The only one that should fail is 3.5 SP1.

Test 2. As an Administrator, open a Command Prompt and run 'SFC /SCANNOW'. A failure regarding the Windows Resource Monitor should be returned.

Solution or Workaround

After confirming the issue, if the 'Low Registry Space' error is returned, reset the Registry Size Limit using the following procedure.

 WARNING: The instructions below include making changes to essential parts of the operating system. It is recommended to backup the operating system and files, including the registry, before proceeding. Consult with a qualified computer systems professional, if necessary.

Esri cannot guarantee results from incorrect modifications while following these instructions; therefore, use caution and proceed at your own risk.



  1. In Windows, click Start > Run.
  2. In the Run window, type 'regedit'.
  3. In the Registry Editor window, navigate to the following location:

    HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control

  4. In the Registry Editor dialog box, double-click RegistrySizeLimit. This opens the Edit DWORD Value dialog box.

     If unable to find the RegistrySizeLimit key in the above path, click Edit > Find and search for RegistrySizeLimit. -show me-

    [O-Image]


    If still unable to find the RegistrySizeLimit key, then create the key using the following steps:

    a. Create the key by Right-Click > New > DWORD (32 or 64 –bit) Value.
    b. Enter ffffffff as the 'Hexadecimal' value. Click the Decimal radio button
    c. Enter 4294967295 as the Decimal value.
    d. Select OK and proceed to Step 6, below.

  5. In the Edit DWORD Value dialog box, enter ffffffff as the Hexadecimal value. Click on the Decimal radio button, and enter 4294967295 as the Decimal value. Click OK.
  6. Reboot the machine.
  7. Log in as an Administrator and open a Command Prompt and run 'SFC /SCANNOW'.

Related Information


Created: 12/29/2009
Last Modified: 3/5/2014

Article Rating: (15)
If you would like to post a comment, please login

Comments

By belcogis - 06/05/2013 5:49 AM

Great article! It helped a lot!

Increasing the RegistrySizeLimit to ffffffff solved the install problem for 10.1 on a Win 7 32-bit computer. The install should warn of this problem before it's nearly complete and then throwing an error and rolling back. Suspected freeware, etc. until found this solution.

Rating:

By npai - 03/13/2013 7:02 AM

The article needs to be updated.

I was able to fix the error on my Windows 7 (SP1), 32-bit computer by changing the RegistrySizeLimit and performing SFC /SCANNOW as mentioned in this article. However, the section of article starting from "If any of the above symptoms...." could be written more clearly. Also, it would be great if ESRI could build the registry fix within their installation package itself.

Rating:

By wthughes - 09/02/2012 4:43 AM

Great article! It helped a lot!

I have run into this issue on 3 ArcGIS 10.1 Desktop installs on Windows 7 32bit machines. The solutions works great!!! Thanks.

Rating:

By njames1272 - 07/18/2012 8:03 AM

Great article! It helped a lot!

Awesome! Finally a walk-through that works... Of course I believe I created my issue by not copy all of the install media to the desktop and still trying to run the 9.3 install. This bombed the 9.3.1 update install. Changing the registry and running the scannow worked. (Win7 32bit)

Rating:

By jasonwix - 06/29/2012 1:12 PM

Great article! It helped a lot!

I would like to know if this is only seen in Windows 7 32bit. I have not been able to produce with the 64bit OS.

Rating:

By rlwatson - 06/29/2012 12:41 PM

Other - See details below.

juniper - Try creating the key if it does not exist.

By juniper - 06/26/2012 12:44 PM

The article needs to be updated.

I ran into the same problem trying to install 10.1 on Windows 7. I tried the checks for verifying the installers and the registry scan, both of which showed the system had no problems. Since there is no key to increase registry size as suggested, I was not able to solve the problem using your suggested solution. What do you do in that situation? Any other suggestions.

Rating:

By smccarron - 03/07/2012 5:58 AM

Great article! It helped a lot!

Fantastic, thanks a million, worked like a charm. Much appreciated.

Rating:

By gmpmapper - 01/12/2012 12:24 AM

Great article! It helped a lot!

Worked great for me too! Windows 7, ArcGIS v10.

Rating:

By plattecounty - 10/18/2011 10:00 AM

Great article! It helped a lot!

Worked PERFECT for v10.0 on Win7

Rating:

By lgxdw - 10/17/2011 7:59 AM

Great article! It helped a lot!

This worked great for me. I also had the same issue with Map Info 11, not sure what is causing it. "this does not solve the problem for win 7. There is no RegistrySizeLimit key in 7" Are you on a 64bit machine? Have you tried opening the 32 bit registry? See How to view the system registry by using 64-bit versions of Windows support.microsoft.com/kb/305097

Rating:

By slewers - 10/11/2011 9:46 AM

The article is incorrect or the solution didn’t work.

this does not solve the problem for win 7. There is no RegistrySizeLimit key in 7

Rating:

By GFLOYD - 06/02/2011 9:09 AM

Great article! It helped a lot!

I bypassed all the techno-preamble and went right to the solution. I changed the RegistrySizeLimit as instructed and presto problem(s) fixed. I was trying to fix a Windows 7 (32-bit) laptop that was upgraded from Vista. I checked another Windows 7 (32-bit) workstation and also our (64-bit) versions and the RegistrySizeLimit key does not exist in the registry. It does in the XP versions. Therefore I think this situation was caused by the upgrade from an upgrade from a prior OS to Windows 7. The fresh installs of Windows 7 that I can tell do not have the RegistrySizeLimit in the registry. Is this weird or what?

Rating:

By Anonymous - 03/20/2011 6:32 PM

The article needs to be updated.

GOD BLESS YOU SO MUCH!! I had my desktop partitioned just because I could not install 10 on my win7 and so had to switch to winXP just to use it. Now I'm on my 7 installing ArcGis 10 as I type!!!!

Rating:

By Anonymous - 03/17/2011 10:23 PM

The article needs to be updated.

I did not go through the entire post as I was in a hurry. I just focussed on the "Solution" section and it worked like a charm. Thanks a lot.

Rating:

By Anonymous - 11/07/2010 11:32 AM

The article is incorrect or the solution didn’t work.

Step 4. of the Solution or Workaround, second sentence is not necessary. Having completed the Edit DWORD Value as ffffffff Hex, the decimal value of 4294967295 will auto populate. No entry necessary. Perhaps just a note that selecting Decimal radio button would show the value.

Rating: