clueless: shim database in registry?

  • Thread starter Thread starter gs
  • Start date Start date
G

gs

what does the following mean?
Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 0
Date: 2006-05-29
Time: 09:39:27
User: N/A
Computer: myPC
Description:
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.
 
..NET 2.0, right? You also have office and VSTO (Visual Studio Tools for
Office) installed. Right?

Apparently this has to do with .NET requesting read/write access to a
registry key that it only needs read access on. If it is just an annoyance,
I would wait until MS fixes it (cannot find a KB on it yet). If it is
impacting work, sysinternals.com has a tool called regmon (registry
monitor). You can start this tool up and repeat the steps that throw the
error in question. Give the .NET account write rights to those keys with
regedt32.exe.

If you go into the registry, save the original keys before changing access,
so you can change it back when the patch comes out. No need to leave keys in
a "wrong" state.

--
Gregory A. Beamer

*************************************************
Think Outside the Box!
*************************************************
 
thx. your are right on
Cowboy (Gregory A. Beamer) said:
.NET 2.0, right? You also have office and VSTO (Visual Studio Tools for
Office) installed. Right?

Apparently this has to do with .NET requesting read/write access to a
registry key that it only needs read access on. If it is just an
annoyance, I would wait until MS fixes it (cannot find a KB on it yet). If
it is impacting work, sysinternals.com has a tool called regmon (registry
monitor). You can start this tool up and repeat the steps that throw the
error in question. Give the .NET account write rights to those keys with
regedt32.exe.

If you go into the registry, save the original keys before changing
access, so you can change it back when the patch comes out. No need to
leave keys in a "wrong" state.

--
Gregory A. Beamer

*************************************************
Think Outside the Box!
*************************************************
Click to expand...
 
Back
Top