asked on

sqlserver writer fails for MMSSEE database

Dear Experts,

I have an SBS2008 server and recently installed windows SP2 and exchange SP3 plus any other outstanding updates. The next scheduled backup and every one since have failed. The failure was caused by the vss sqlserverwriter. Vssadmin reports:

Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {cc18327c-615f-429b-ad99-16cdc1caa8ea}
State: [8] Failed
Last error: Non-retryable error

I have narrowed it down further to an SQL instance. The Service is called "windows internal database (MICROSOFT##SSEE)" When i stop this service and perform a backup (even with the "VSS SQL server writer" service started, ) the backup completes perfectly.
To my knowledge, this database is used by wsus, sharepoint and other services.

I can write a script to stop this service before the backup then start it again, but I would like to put it right properly.

How can I resolve this one?

I have posted this before on EE but it seems to have run out of interest - so sorry for double-posting!

Thanks in advance.

Bhavesh Shah

Hi,

check out this link.

http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/9cf42e8a-2a33-47c5-a797-269330e9ba1a

it may helps to solve your problem

Cruthin

ASKER

Certainly looks like there might be a solution in there somewhere! I will go through them and respond accordingly.

Thanks.

Cruthin

ASKER

I believe that the issue may lie with Sharepoint services. I need to restore a backup of the server to a non-production box to attempt a repair. I will be following the procedures here http://technet.microsoft.com/en-us/library/dd540850(WS.10).aspx

ASKER CERTIFIED SOLUTION

Cruthin

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Bhavesh Shah

=) Good.

All The Best

Glen Knight

This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.