Re: VSS event 6013

Brandy,

I am experiencing a similar issue where VSS tries to access my SQL
Server every time I perform a system state backup. For security
reasons we remove Local System and Builtin Administrators from all of
our SQL Server installations. The VSS error is the same as documented
here. Can you explain why VSS tries to make a connection to SQL
Server? I reviewed the documentation on what is backed up with system
state and databases are not listed.

Thanks

John



"Brandy Nee [MSFT]" wrote:
Hello Neil,

Thank you for posting back. Sorry to keep you waiting since I was ill
yesterday.

I need to confirm with you if you have contacted our PSS to download
hotfix915331?

I understand that you cannot run the command to stop the VSS service. In
this case, please go to the Service console (services.msc), right click
"Volume Shadow Copy Service" and select stop. Can you stop the VSS in this
method? If no, what is the exact error message you encounter? Please type
the full content of the error message word by word to the Newsgroup. if you
can stop VSS, please continue performing the suggestions in my previous
reply to register those .dll files.

I reviewed the whole thread, in your previous reply, you mentioned "But I'm
not actually trying to back up SQL Server, which is why I suggested
uninstalling it". Do you mean you have SQL install?

If you have SQL Server, please make sure the system account is a member of
the SQL Administrators group.

Also, since you have SBS 2K3 SP1 installed, please reinstall COM+ to see
how the issue goes:

1. Backup and then delete HKEY_LOCAL_MACHINE\Software\Microsoft\COM3
2. Boot to Recovery console and rename clbcatq.dll to ~clbcatq.dll. Be
sure to use the tilde.
3. Boot to normal mode and in Control Panel, open the Add or Remove
Programs tool, and then open the Add/Remove Windows Components tool. Do not
make any changes, just click "Next". This reinstalls COM+.

Please take your time to perform the steps. If you have any further
updates, please feel free to let me know. I am looking forward to your
reply!

Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.



--------------------
Date: Wed, 28 Jun 2006 12:27:59 +0100
From: Neil Rashbrook <neil@xxxxxxxxxxxxxxx>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Gecko/20040113 Netscape7/7.05
X-Accept-Language: en-gb, en, en-us
MIME-Version: 1.0
Subject: Re: VSS event 6013
References: <eDNHNmElGHA.896@xxxxxxxxxxxxxxxxxxxx>
<QBB2aSPlGHA.4928@xxxxxxxxxxxxxxxxxxxxx>
<e8NseltlGHA.4076@xxxxxxxxxxxxxxxxxxxx>
<0BBvDsOmGHA.4928@xxxxxxxxxxxxxxxxxxxxx>
In-Reply-To: <0BBvDsOmGHA.4928@xxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <#UDKsXqmGHA.4816@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
NNTP-Posting-Host: parkwaycs-218.adsl.newnet.co.uk 80.175.250.218
Lines: 1
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:277923
X-Tomcat-NG: microsoft.public.windows.server.sbs

Brandy Nee [MSFT] wrote:

Net stop vss


The Volume Shadow Copy service could not be stopped.

1. On the server, run "eventvwr" (without quotation marks), check
whether there are any errors. If yes, double click it, click the Copy
button and paste the full content to the Newsgroup.

2. Can you manually run NTbackup to SBS Server Local Hard Disk?

No. As long as I try to back up the system state, then either way
produces the following events:

Event Type: Information
Event Source: NTBackup
Event Category: None
Event ID: 8018
Date: 28/06/2006
Time: 12:00:10
User: N/A
Computer: #########
Description:
Begin Operation

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Information
Event Source: ESENT
Event Category: Logging/Recovery
Event ID: 210
Date: 28/06/2006
Time: 12:00:10
User: N/A
Computer: #########
Description:
certsrv.exe (656) A full backup is starting.

Event Type: Error
Event Source: ESENT
Event Category: Logging/Recovery
Event ID: 215
Date: 28/06/2006
Time: 12:00:10
User: N/A
Computer: #########
Description:
certsrv.exe (656) The backup has been stopped because it was halted by
the client or the connection with the client failed.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: NTBackup
Event Category: None
Event ID: 8019
Date: 28/06/2006
Time: 12:05:10
User: N/A
Computer: #########
Description:
End Operation: Warnings or errors were encountered.
Consult the backup report for more details.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The VSS events are then logged some time later, they all look like this:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6013
Date: 28/06/2006
Time: 12:20:15
User: N/A
Computer: #########
Description:
Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize.
hr = 0x80004005. SQLSTATE: 08001, Native Error: 17
Error state: 1, Severity: 16
Source: Microsoft OLE DB Provider for SQL Server
Error message: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not
exist or access denied.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 20 43 6f 64 65 3a 20 - Code:
0008: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0010: 30 30 30 30 30 34 39 31 00000491
0018: 2d 20 43 61 6c 6c 3a 20 - Call:
0020: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
0028: 30 30 30 30 30 33 39 37 00000397
0030: 2d 20 50 49 44 3a 20 20 - PID:
0038: 30 30 30 30 38 30 37 36 00008076
0040: 2d 20 54 49 44 3a 20 20 - TID:
0048: 30 30 30 30 37 39 30 38 00007908
0050: 2d 20 43 4d 44 3a 20 20 - CMD:
0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
0060: 57 53 5c 53 79 73 74 65 WS\Syste
0068: 6d 33 32 5c 76 73 73 76 m32\vssv
0070: 63 2e 65 78 65 20 20 20 c.exe
0078: 2d 20 55 73 65 72 3a 20 - User:
0080: 4e 54 20 41 55 54 48 4f NT AUTHO
0088: 52 49 54 59 5c 53 59 53 RITY\SYS
0090: 54 45 4d 20 20 20 20 20 TEM
0098: 2d 20 53 69 64 3a 20 20 - Sid:
00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18


.