VSS unexpected error

I am getting the following error in my logs when I try and launch SBS backup (2008 version) manually. The backup has been failing for almost a week and seems to be associated with this error. Any thoughts on what the problem is?

If relevant I have ACT! doing daily backup and Backup exec system restore (installed but not currently doing auto backups). I also have an offsite backup utility (Jungle Disk) doing nitely data archiving offsite.

Log Name:      Application
Source:        VSS
Date:          3/24/2010 7:26:33 PM
Event ID:      12289
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SVR-SBS2008.parson.local
Description:
Volume Shadow Copy Service error: Unexpected error VSS_E_WRITER_STATUS_NOT_AVAILABLE. An older active writer session state is being overwritten by a newer session. The most common cause is that the number of parallel backups has exceeded the maximum supported limit.  hr = 0x80042409.

Operation:
   PostSnapshot Event

Context:
   Maximum supported sessions: 64
   Completed sessions: 8
   Active sessions: 64
   Aborted sessions: 0
   Writer failed sessions: 1
   New snaphot set: {dd7f2eb2-39b6-472d-9e2e-28cff5223fd4}
   Old snapshot set: {7c6b869e-0eba-4c97-a434-4f451023a75b}
   Old operation: 1003
   Old state: 9
   Old failure: 0x800423f2
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2005:SQLWriter
   Writer Instance ID: {2a4e96c3-1779-4a57-9d8f-09960d3aa837}
Operation:
   PostSnapshot Event

Context:
   Maximum supported sessions: 64
   Completed sessions: 8
   Active sessions: 64
   Aborted sessions: 0
   Writer failed sessions: 1
   New snaphot set: {dd7f2eb2-39b6-472d-9e2e-28cff5223fd4}
   Old snapshot set: {7c6b869e-0eba-4c97-a434-4f451023a75b}
   Old operation: 1003
   Old state: 9
   Old failure: 0x800423f2
   Execution Context: Writer
   Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Name: SqlServerWriter
   Writer Instance Name: SQL Server 2005:SQLWriter
   Writer Instance ID: {2a4e96c3-1779-4a57-9d8f-09960d3aa837}</Data>
   
LVL 2
pmckenna11Asked:
Who is Participating?
 
ConchCrawlConnect With a Mentor Commented:
Please make sure you have install SP2 for server 2008. This can be an issue for this problem and is usually fixed by SP2. You did not mention it in your post so I may be stating the obvious.
0
 
laceratorConnect With a Mentor Commented:
May want to look at this technet article. Hope it fixes it. Backups are crucial.

http://technet.microsoft.com/en-us/library/cc734302.aspx

http://technet.microsoft.com/en-us/library/cc734302(WS.10).aspx

--------------------------

Resolve

Check the operation of the VSS hardware providers

Possible resolutions include:

Open Event Viewer and check for events related to Volume Shadow Copy Service (VSS) that mention hardware providers.
Make sure that VSS hardware providers are operating properly.
To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Open Event Viewer and view events related to VSS hardware providers

To open Event Viewer and view events related to VSS hardware providers:

If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click Application.
To filter the events so that only events with a Source of VSS are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources drop-down list, select the checkbox for VSS. Select other options as appropriate, and then click OK.
To sort the displayed events by date and time, in the center pane, click the Date and Time heading.
Note any events that mention VSS hardware providers.
Make sure that VSS hardware providers are operating properly

To make sure that VSS hardware providers are operating properly:

Open an elevated Command Prompt. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type vssadmin list providers, and then press Enter.
If a provider is missing from the list of registered providers, try reinstalling it.
For each provider that appears in the list, use the vssadmin create shadow command to create a shadow copy of the volume for which the provider is responsible. For more information, see http://go.microsoft.com/fwlink/?LinkId=105248.
If a provider is unable to create a shadow copy, contact Microsoft Customer Service and Support. For more information, see http://go.microsoft.com/fwlink/?LinkId=102491. You should provide the entire event log message as it appears in the Event Viewer.

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Volume Shadow Copy Service is started:

Click Start, point to Administrative Tools, and then click Services.
In the results pane, double-click Volume Shadow Copy.
In Service status, make sure that the status is Started. If the status is not Started, click Start.
Make sure Startup type is set to Manual.
Click OK.

0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
laceratorCommented:
try the second post first, it is easier and quicker to test.
0
 
pmckenna11Author Commented:
Thanks for the tips but I am still having issues. First this is SBS2008 with all available patches installed. Also I stopped and then restarted to VSS service. I then tried to run the backup. It again failed. When I checked the logs I found these errors

The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShadowCopy228.

Backup started at '3/25/2010 3:55:21 AM' failed with following error code '2155348009' (The read from volume shadow copy on source failed.). Please rerun backup once issue is resolved.

BTW, the time stamp is completely wrong on the error message. It was actually written in the log at 9pm

I have another post going related to the hard disk error showing up on hardisk\volume2. Not sure how all this ties together.
0
 
ConchCrawlConnect With a Mentor Commented:
You have installed SP2 for server 2008?
Have run the command "vssadmin list writers", if it is not stable then re-register the VSS binaries?
Report the errors back to here.
Restart the server.
0
 
pmckenna11Author Commented:
Well I have been saying that SP2 is installed but apparently it is not. If I go to control panel->system I see Windows server SP1.
I see no signs of SP2 being available through Windows update. I can download Windows Server 2008 SP2 and install it but why isn't it showing up through the windows update? If I didn't say elsewhere this is an SBS2008 machine.

I ran vssadmin list writers and got no errors. The lengthy results are posted below

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {5dbc8981-9f01-4f6a-b64f-0f1a46f31428}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {db8b00a7-5902-410d-b88f-8dda0381e96a}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch VSS Writer'
   Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
   Writer Instance Id: {2c3498c9-dbf3-4be6-8a24-2b0160b9dd5b}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {37d0b1da-f12e-43cf-a12f-30b517838e9d}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {0dd34497-97ea-4fe1-85ed-696eb0fc8a6b}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {2a4e96c3-1779-4a57-9d8f-09960d3aa837}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {624e419c-90fe-414e-a809-3f1ae65bdbc6}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {4d698da1-57fc-409a-b5c0-76e6ae8d1815}
   State: [1] Stable
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {c2f52614-5e53-4858-a589-38eeb25c6184}
   Writer Instance Id: {1b50072f-43d9-4ba4-94ed-bb01ade21834}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {e7c61161-c201-47f1-b8bc-ef8190495ac5}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {f440fced-abfe-49c8-a5b1-6c21e05c842b}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {0030f33b-0058-48fb-a6c3-005b9c22ea52}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {6b16a45c-d954-40f1-aab9-c1d81fcdf978}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {1f7b1a57-07f0-4086-97a7-b77957087f90}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {7904bb3a-a002-4c6d-be9e-3254edd34ef8}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {fb4b5230-dc83-4ae7-b38f-4911b13a806b}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {a5c5deb7-b6ae-426a-aae2-4fb68e70ac7a}
   State: [1] Stable
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {7fd46633-86f2-48be-8f78-5828c7288329}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {230e8fdc-4609-459e-8075-276b9dc1eeaf}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {96f474c5-b8da-4f02-90e1-77f4060e9b09}
   State: [1] Stable
   Last error: No error
0
 
ConchCrawlCommented:
OK, then I understand, but I would definately try and install/reinstall SP2 if it not there, don't know why.
Your VSS Binaries look fine, so maybe install SP2 and see where we go from there, no since in chasing our tails if this fixes the problem :-).
I knew you were running SBS 2008 I just never saw anywhere you posted that you were on SP2.
0
 
pmckenna11Author Commented:
The problem is not yet solved but I am closing the question and will repost in a different thread where I can add more information. The responses given are relevant.
0
All Courses

From novice to tech pro — start learning today.