Main Forum > Tweaking.com Support & Help
Registry Backup Fails
Shane:
No that is ok. Let me do more google searches for "Microsoft Writer (Service State)' is in failed state!" and see what I can come up with. I will post back in a few :wink:
Shane
Shane:
What is odd is the error you got matches perfectly with the sql errors.
--- Quote ---Symptoms
Consider the following scenario. In Microsoft SQL Server, you create a snapshot backup of many databases at the same time. To do this, you use the Volume Shadow Copy Service (VSS), or you use the Virtual Backup Device Interface (VDI). In this scenario, the snapshot backup operation fails. Additionally, you receive the following error message if you use the VSS to create the snapshot backup:
ERROR: Selected writer ‘Microsoft Writer (Service State)’ is in failed state!
– Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
- Writer Failure code: 0×800423f4 (<Unknown error code>)
- Writer ID: {WriterID}
- Instance ID: {InstanceID}You receive one of the following error messages if you use the VDI to create the snapshot backup:
Error message 1
--- End quote ---
Try the backup again. After it fails go to the event viewer and see if you have any errors from VSS and let me know what they are. I have to try to pin this down :wink:
I am heading out to a couple of customers to repair some systems. I will be back later today. :wink:
Shane
Charmin:
Hi Shane.
Here is the VSS error corresponding to the log I sent you earlier. I hope it helps.
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 5013
Date: 06/06/2012
Time: 16:26:37
User: N/A
Computer: CHARMIN
Description:
Volume Shadow Copy Service error: Shadow Copy writer ContentIndexingService called routine VsServiceChangeState which failed with status 0x80070424 (converted to 0x800423f4).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 57 53 48 43 4f 4d 4e 43 WSHCOMNC
0008: 32 32 39 32 00 00 00 00 2292....
0010: 57 53 48 43 49 43 00 00 WSHCIC..
0018: 33 37 32 00 00 00 00 00 372.....
Shane:
I found this
--- Quote ---It seems that when I was beta testing Office 11 (aka Office 2003), Visio
installed a key in the Content Indexing Service creating a separate index
catalog for Visio files. When I uninstalled Visio, that key didn't go away.
Because CISVC was disabled, it never made a difference to content indexing.
However, it certainly got on the wrong side of VSS.
I deleted
hklm\SYSTEM\CurrentControlset\Control\ContentIndex\Catalogs\visio
and now VSS seems to run OK.
--- End quote ---
Let me know if you have that reg key and if you do try the fix and let me know if it works :wink:
Shane
Charmin:
Hi Shane
Sorry for the delay but I am in the UK.
During my own investigation I was pointed to that reg key but found I did not have the "Catalogs" or "visio" sub keys. Just to see if that was the area of the problem I added the following, which, from information on the web site, was the default:-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\System
Entry name Data type Value
(Default) REG_SZ (value not set)
IsIndexingNNTPSvc REG_DWORD 0x0000000 (0)
IsIndexingW3Svc REG_DWORD 0x0000000 (0)
Location REG_SZ C:\System Volume Information
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex\Catalogs\Web
Entry name Data type Value
(Default) REG_SZ (value not set)
FilterFilesWithUnknownExtensions REG_DWORD 0x0000000 (0)
GenerateCharacterization REG_DWORD 0x0000001 (1)
IsIndexingNNTPSvc REG_DWORD 0x0000000 (0)
IsIndexingW3Svc REG_DWORD 0x0000001 (1)
Location REG_SZ c:\inetpub
MaxCharacterization REG_DWORD 0x00000140 (320)
W3SvcInstance REG_DWORD 0x0000001 (1)
Unfortunately it didn't help.
Sorry, not the source of the problem
Charmin (UK)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version