SharePoint 2007 SP2 VSS backup error ?

Hi Everyone,

I've been getting this error below all the time regarding the VSS backup error in the event viewer, eventhough the VSS Writer status got no error in the cmd prompt.

and also Symantec Backup Exec 2010 R2 agent got error in backup the farm using the DOMAIN\SPService username which is the owner of this WSS_ContentDB and also member of the Farm admin group.

can anyone share your experience here to fix this error please ?

Thanks,
JJ
Log Name:      Application
Source:        Windows SharePoint Services 3
Date:          8/09/2010 10:11:31 PM
Event ID:      3760
Task Category: Database
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MOSSDEV01.domain.com
Description:
SQL Database 'SharePoint_AdminContent_f632e5bf-cbd9-4d9f-a819-1811feb4f2b6' on SQL Server instance 'MOSSDEV01\MOSSDB' not found. Additional error information from SQL Server is included below.

Cannot open database "SharePoint_AdminContent_f632e5bf-cbd9-4d9f-a819-1811feb4f2b6" requested by the login. The login failed.
Login failed for user 'DOMAIN\Administrator'.
#########################################################################################################################################################
Log Name:      Application
Source:        VSS
Date:          8/09/2010 10:08:52 PM
Event ID:      12289
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MOSSDEV01.domain.com
Description:
Volume Shadow Copy Service error: Unexpected error RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,...).  hr = 0x80070005. 

Operation:
   Initializing Writer

Context:
   Writer Class Id: {8d5f38cd-fb7a-49ca-ae1b-21d1f017d8f9}
   Writer Name: OSearch VSS Writer
   Writer Instance ID: {b87cc4be-935b-4479-ac5d-618a41767a0f}
#
#----------------------------------------------------------------------------------------------------------------------------------------------------# 
#Command Prompt
#----------------------------------------------------------------------------------------------------------------------------------------------------#
# 
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: {34de22c6-4a77-4af6-9ae6-1b4eee4d629b}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {c6074e09-4962-4290-9639-d8cc7d08f644}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {76d8b78a-0c87-464f-b538-4fee7c515f42}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {45b2f7f5-91e6-4607-a6df-ef85bebe8770}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {48f71749-817b-4f11-b97a-1f63f525626e}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch VSS Writer'
   Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
   Writer Instance Id: {9f4ab399-ff20-4dae-9063-7b737d52edd3}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {e9efb4dd-8e77-42c1-90ef-55b879ee60b2}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {db5e3151-2f42-4aa7-acb7-b1ffe169cd2a}
   State: [1] Stable
   Last error: No error

Writer name: 'OSearch VSS Writer'
   Writer Id: {8d5f38cd-fb7a-49ca-ae1b-21d1f017d8f9}
   Writer Instance Id: {b87cc4be-935b-4479-ac5d-618a41767a0f}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {9f5a29f8-93f8-48a6-8330-605423ad951b}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {c9bc929c-4357-4028-81d6-8b48e6b65c13}
   State: [1] Stable
   Last error: No error

C:\Windows\system32>

Open in new window

error.jpg
LVL 1
jjozAsked:
Who is Participating?
 
Justin SmithConnect With a Mentor Sr. System EngineerCommented:
try it temporarily.  i just don't know how this product is backing sharepoint up.  have you double checked all things in their setup guide?

what permissions does domain\admin have on the SQL box?  if you look at the properties of the acount, under mappings, what permissions does it have on the _admin database?
0
 
Justin SmithConnect With a Mentor Sr. System EngineerCommented:
Sidenote......Symantec products absolutely suck at backing up SharePoint.

Are you doing a SharePoint specific backup?  Or are you just trying to backup the SQL databases?  Is SPService an admin on your WFE server?
0
 
jjozAuthor Commented:
yes i must admit man :-|
at the moment SPService not a local admin ...
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
jjozAuthor Commented:
thanks man, you're right the problem was solved after making sure that the logon Admin right in the backup Exec is the same as the Farm Admin account and SQL Server DB Owner.
0
 
jjozAuthor Commented:
thanks man for the inspiration !
0
 
jjozAuthor Commented:
or like this in the most simplest form: Farm Admin = WSS_Content_DB Owner = BE Default Logon Account
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.