Event Viewer Error: Unable to Open Shim Database Version Registry Key .

On your XP workstation, you may find the following error registered in Event Viewer:

Event Type: Error
Event Source: .NET RuntimeEvent
Category: None
Event ID: 0
Date: 02-05-2006
Time: 22:36:30
User: N/AComputer: ComputerName
The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Unable to open shim database version registry key – v2.0.50727.00000.

Cause of Error (as explained at MSDN forum)
There is a known issue in the v2.0 runtime that is causing this but in general it does not have any negative effects on the machine. What’s going on is that there is a “shim database” in the registry that the runtime reads to determine if an application that is about to load the runtime via COM interop really needs an earlier vesion instead.

The problem is that the runtime was incorrectly asking for read/write permission to these reg keys rather than the read access it needed and so if you try to load managed code via com interop in a process that does not have administrator privilages you will get this in your event log and we will choose the runtime for this process as we normally do. This only impacts applications if you are running one of the applications that is in the list that needed the earlier runtime.

The only time we expect this to occur is if you are running Word or Excel 2003 as a non-admin user and you have VSTO 2003 applications installed on the machine. If this is the case for you, you can go to Office Update and the latest critical updates will fix the issue and your applications will work as always (you will still get this entry in the event log).
We plan on addressing this issue as early as possible in an SP we don’t know when that would occur.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: