Jump to content

Something about SQL server screwing up VSS in Win2k3 x64 R2 SP2


Recommended Posts

Posted

Hello,

 

I see a lot of issues in my event viewer all seem to be related to SQL

errors. There have been a lot of hands touching this server and I see

software installed on it that I didn't install but that may not be related.

I don't see the items listed under program files - e.g. Microsoft SQL Server

2005. I see the SQL manager running in the bottom right hand but there is

no SQL database that it is attached to, it wants me to select one. I can't

list the server that it is on in the drop down.

 

I'm not sure what to do.

 

 

Here is the issue in the event viewer -

Source VSS Event ID 6013

 

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.

 

 

 

 

 

I tried running vssadmin -

 

C:\Temp>Vssadmin list writers

 

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

 

© Copyright 2001 Microsoft Corp.

 

 

 

Waiting for responses.

 

These may be delayed if a shadow copy is being prepared.

 

 

 

Writer name: 'MSDEWriter'

 

Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

 

Writer Instance Id: {8866fde9-6f64-4229-9553-3d8f932e3f61}

 

State: [1] Stable

 

Last error: Non-retryable error

 

 

 

Writer name: 'System Writer'

 

Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

 

Writer Instance Id: {67463211-6303-453f-ac5e-84bb8b0d35fd}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'FRS Writer'

 

Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

 

Writer Instance Id: {30d9f1c5-947e-4e86-a828-aade2286d170}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'FSRM Writer'

 

Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}

 

Writer Instance Id: {30907b60-9ce8-42b2-a2c2-7476f3bc0a30}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'IIS Metabase Writer'

 

Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

 

Writer Instance Id: {5a841fda-d678-4eba-a927-2f2b4ef2b53a}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'WINS Jet Writer'

 

Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}

 

Writer Instance Id: {b8fd7e21-2096-4a4b-8c25-b48c3d1cae25}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'Registry Writer'

 

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

 

Writer Instance Id: {663e9532-5ca8-4724-b466-aa62c0870d7c}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'Event Log Writer'

 

Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}

 

Writer Instance Id: {848bfc36-5a46-4f0d-b4cf-35d35e644bb4}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'COM+ REGDB Writer'

 

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

 

Writer Instance Id: {3509932d-6cbd-480b-a212-e8aedc89f61e}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'NTDS'

 

Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

 

Writer Instance Id: {d7071b0e-27e1-46a2-970b-d359a8af18a2}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'Dhcp Jet Writer'

 

Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

 

Writer Instance Id: {52faa5f3-13e5-4bfe-8114-73f129652f97}

 

State: [1] Stable

 

Last error: No error

 

 

 

Writer name: 'WMI Writer'

 

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

 

Writer Instance Id: {9189c27a-1ccd-4a29-b8b9-ad33b61a313f}

 

State: [1] Stable

 

Last error: No error

  • Replies 1
  • Created
  • Last Reply

Popular Days

Posted

Re: Something about SQL server screwing up VSS in Win2k3 x64 R2 SP2

 

I think I may have it - I think it might have been backup exec - had to

rename the backup exec sql dll to .old

 

"boe" <boe_d@hotmail.com> wrote in message

news:O2fGnyPBIHA.1356@TK2MSFTNGP03.phx.gbl...

> Hello,

>

> I see a lot of issues in my event viewer all seem to be related to SQL

> errors. There have been a lot of hands touching this server and I see

> software installed on it that I didn't install but that may not be

> related. I don't see the items listed under program files - e.g. Microsoft

> SQL Server 2005. I see the SQL manager running in the bottom right hand

> but there is no SQL database that it is attached to, it wants me to select

> one. I can't list the server that it is on in the drop down.

>

> I'm not sure what to do.

>

>

> Here is the issue in the event viewer -

> Source VSS Event ID 6013

>

> 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.

>

>

>

>

>

> I tried running vssadmin -

>

> C:\Temp>Vssadmin list writers

>

> vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

>

> © Copyright 2001 Microsoft Corp.

>

>

>

> Waiting for responses.

>

> These may be delayed if a shadow copy is being prepared.

>

>

>

> Writer name: 'MSDEWriter'

>

> Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}

>

> Writer Instance Id: {8866fde9-6f64-4229-9553-3d8f932e3f61}

>

> State: [1] Stable

>

> Last error: Non-retryable error

>

>

>

> Writer name: 'System Writer'

>

> Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

>

> Writer Instance Id: {67463211-6303-453f-ac5e-84bb8b0d35fd}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'FRS Writer'

>

> Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

>

> Writer Instance Id: {30d9f1c5-947e-4e86-a828-aade2286d170}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'FSRM Writer'

>

> Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}

>

> Writer Instance Id: {30907b60-9ce8-42b2-a2c2-7476f3bc0a30}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'IIS Metabase Writer'

>

> Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

>

> Writer Instance Id: {5a841fda-d678-4eba-a927-2f2b4ef2b53a}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'WINS Jet Writer'

>

> Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}

>

> Writer Instance Id: {b8fd7e21-2096-4a4b-8c25-b48c3d1cae25}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'Registry Writer'

>

> Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

>

> Writer Instance Id: {663e9532-5ca8-4724-b466-aa62c0870d7c}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'Event Log Writer'

>

> Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}

>

> Writer Instance Id: {848bfc36-5a46-4f0d-b4cf-35d35e644bb4}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'COM+ REGDB Writer'

>

> Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

>

> Writer Instance Id: {3509932d-6cbd-480b-a212-e8aedc89f61e}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'NTDS'

>

> Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

>

> Writer Instance Id: {d7071b0e-27e1-46a2-970b-d359a8af18a2}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'Dhcp Jet Writer'

>

> Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}

>

> Writer Instance Id: {52faa5f3-13e5-4bfe-8114-73f129652f97}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

> Writer name: 'WMI Writer'

>

> Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

>

> Writer Instance Id: {9189c27a-1ccd-4a29-b8b9-ad33b61a313f}

>

> State: [1] Stable

>

> Last error: No error

>

>

>

>


×
×
  • Create New...