VSS Error, EventID 5013

G

Guest

To make a long story short (don't ask...), after having installed the new version of Visio 2003 NTBackup is acting up, and cannot do Volume Shadow Copies anymore. The eventlog has two error messages from VSS, the first one saying

"Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine RegQueryValueExW which failed with status 0x80070002 (converted to 0x800423f4).

I have done a bit of research on this error message, but all I can find are a few postings that say that this is due to some problem with the HKLM\System\CurrentControlSet\Eventlo
keys. However, I cannot find anything wrong in any of the subkeys; I did a file-compare of the exported Eventlog hierarchy before and after the install of Visio, and I could not find any differences (oh, and the problem is irreversible: uninstalling Visio does not help...)

Does anybody have any ideas what else I should check, or how I could solve the problem? I also tried doing an audit for object access failures in the Eventlog key hierarchy, and in C:\Program Files\Common Files\ and C:\Windows\system32\, which came up emtpy

I really would like to be able to do full backups, and I would be immensely grateful for any pointers..

-- John
 
B

Bill

-----Original Message-----
John

http://www.eventid.net/display.asp?eventid=5013&source=VSS

Not too informative!

--
~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
(e-mail address removed)
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.

~~~~~~~~~~~~~~~~~~~~~~~~


"John Dalton" <[email protected]> wrote
in message (e-mail address removed)...installed the new version of Visio 2003 NTBackup is acting
up, and cannot do Volume Shadow Copies anymore. The
eventlog has two error messages from VSS, the first one
saying:ContentIndexingService called routine RegQueryValueExW
which failed with status 0x80070002 (converted to
0x800423f4)."but all I can find are a few postings that say that this
is due to some problem with the
HKLM\System\CurrentControlSet\Eventlogthe subkeys; I did a file-compare of the exported Eventlog
hierarchy before and after the install of Visio, and I
could not find any differences (oh, and the problem is
irreversible: uninstalling Visio does not help...).or how I could solve the problem? I also tried doing an
audit for object access failures in the Eventlog key
hierarchy, and in C:\Program Files\Common Files\ and
C:\Windows\system32\, which came up emtpy.
.
Isn't this the sort of thing that restore points were
supposed to fix?? They make it sound so easy - just roll
it back to a date before the install and there it isn't.

Bill :)
 
A

Adi Oltean [MSFT]

Hi John,

It looks like the Visio installation corrupted the Content Indexing
catalogs. The faulty registry key should be:
HKLM\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\visio

There you should have a value called "Location" that should point to a
valid directory. On my machine it shows:

Z:\>reg.exe query hklm\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\visio

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\visio
Location REG_SZ C:\Documents and Settings\All
Users\Application Data\Microsoft\VISIO\
FilterRetryInterval REG_DWORD 0x5
UsnReadMinSize REG_DWORD 0x1
MaxWordlistIoDiskPerf REG_DWORD 0x64
FilterDelayInterval REG_DWORD 0x2
DelayUsnReadOnLowResource REG_DWORD 0x0
FilterRemainingThreshold REG_DWORD 0x5
LowResourceSleep REG_DWORD 0x5
WordlistUserIdle REG_DWORD 0x0
MaxFreshCount REG_DWORD 0x7530
MaxWordlistIo REG_DWORD 0xffffffff

Z:\>dir "C:\Documents and Settings\All Users\Application
Data\Microsoft\VISIO\
Volume in drive C has no label.
Volume Serial Number is 3826-D6D2

Directory of C:\Documents and Settings\All Users\Application
Data\Microsoft\VISIO

09/18/2003 10:17 AM <DIR> .
09/18/2003 10:17 AM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 2,569,781,248 bytes free


To fix the NTBackup issue, you might just want to fix the Location
registry value above or even delete the Visio catalog registry key.
For example:

reg delete hklm\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\visio


Thanks, Adi

P.S. This posting is provided "AS IS" with no warranties, and confers
no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top