WinServer 2003 SP2 X64 - VSS Problems

Hey

I have a production server running Windows Server 2003 SP2 X64.
This server also has Exchange 2007 installed (not SP1).

Recently the server failing its backup's... listing
Event ID: 12302
Volume Shadow Copy Service error: An internal inconsistency was detected in
trying to contact shadow copy service writers. Please check to see that the
Event Service and Volume Shadow Copy Service are operating properly.

Now upon trying to check the vss writers... there arnt any.
CMD > vssadmin list writers < BLANK

Upon checking a healthy server that can currently backup it has several VSS
Writers. I was wondering if there is a way to copy healthy VSS Writers from a
functioning server to this not so healthy server :)

From memory Exchange also has its own VSS writer does it not? Which
unfortunately this other server wouldnt have a copy of.

Is there a way to reinstall the VSS Writers? Thanks in advance.

In news:3E844B47-C23E-4AA0-AD93-B85284D82D6C@microsoft.com,
Nomad <Nomad@discussions.microsoft.com> typed:
> Hey
>
> I have a production server running Windows Server 2003 SP2 X64.
> This server also has Exchange 2007 installed (not SP1).
>
> Recently the server failing its backup's... listing
> Event ID: 12302
> Volume Shadow Copy Service error: An internal inconsistency was
> detected in trying to contact shadow copy service writers. Please
> check to see that the Event Service and Volume Shadow Copy Service
> are operating properly.
>
> Now upon trying to check the vss writers... there arnt any.
> CMD > vssadmin list writers < BLANK
>
> Upon checking a healthy server that can currently backup it has
> several VSS Writers. I was wondering if there is a way to copy
> healthy VSS Writers from a functioning server to this not so healthy
> server :)
>
> From memory Exchange also has its own VSS writer does it not? Which
> unfortunately this other server wouldnt have a copy of.
>
> Is there a way to reinstall the VSS Writers? Thanks in advance.

The VSS should be part of the Exchange installation. Did you uninstall
something recently that may have yanked out it's reference in the Content
Index Catalog in the registry? Kind of sounds like it. Look at
http://support.microsoft.com/kb/907574 to fix it if that may have happend.
Also the update in http://support.microsoft.com/kb/913648 may help.

Read this for more info:
http://eventid.net/display.asp?event...ce=VSS&phase=1

Install SP1, it works nicely. Lot's of new features that make admnistration
alot easier bringing back much into the GUI.

For more info, you are much better off posting to the Exchange newsgroups
for better *specific* Exchange help. THis is just a general server group and
many of the Exchange folks do not monitor this group.


--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Thanks Ace.

I know this isnt the Exchange Forum, this problem is more a Server 2003
problem since ALL the VSS Writers are missing. I am posting this before
checking out those links you sent me :)

As for why Exchange 2007 is not SP1 yet... its because I dont have a recent
enough backup INCASE something goes wrong ;)

As for installing / uninstalling something recently, no. This server has not
been touched installation wise since it was setup late last year.

Will check out the links and let you know how I go, thanks for the help :)

"Ace Fekay [MVP]" wrote:

> In news:3E844B47-C23E-4AA0-AD93-B85284D82D6C@microsoft.com,
> Nomad <Nomad@discussions.microsoft.com> typed:
> > Hey
> >
> > I have a production server running Windows Server 2003 SP2 X64.
> > This server also has Exchange 2007 installed (not SP1).
> >
> > Recently the server failing its backup's... listing
> > Event ID: 12302
> > Volume Shadow Copy Service error: An internal inconsistency was
> > detected in trying to contact shadow copy service writers. Please
> > check to see that the Event Service and Volume Shadow Copy Service
> > are operating properly.
> >
> > Now upon trying to check the vss writers... there arnt any.
> > CMD > vssadmin list writers < BLANK
> >
> > Upon checking a healthy server that can currently backup it has
> > several VSS Writers. I was wondering if there is a way to copy
> > healthy VSS Writers from a functioning server to this not so healthy
> > server :)
> >
> > From memory Exchange also has its own VSS writer does it not? Which
> > unfortunately this other server wouldnt have a copy of.
> >
> > Is there a way to reinstall the VSS Writers? Thanks in advance.
>
> The VSS should be part of the Exchange installation. Did you uninstall
> something recently that may have yanked out it's reference in the Content
> Index Catalog in the registry? Kind of sounds like it. Look at
> http://support.microsoft.com/kb/907574 to fix it if that may have happend.
> Also the update in http://support.microsoft.com/kb/913648 may help.
>
> Read this for more info:
> http://eventid.net/display.asp?event...ce=VSS&phase=1
>
> Install SP1, it works nicely. Lot's of new features that make admnistration
> alot easier bringing back much into the GUI.
>
> For more info, you are much better off posting to the Exchange newsgroups
> for better *specific* Exchange help. THis is just a general server group and
> many of the Exchange folks do not monitor this group.
>
>
> --
> Regards,
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
> MVP Microsoft MVP - Directory Services
> Microsoft Certified Trainer
>
> Infinite Diversities in Infinite Combinations
>
>
>

In news:D4B95D55-F55F-434D-8CEA-16CC9C24DE0C@microsoft.com,
Nomad <Nomad@discussions.microsoft.com> typed:
> Thanks Ace.
>
> I know this isnt the Exchange Forum, this problem is more a Server
> 2003 problem since ALL the VSS Writers are missing. I am posting this
> before checking out those links you sent me :)
>
> As for why Exchange 2007 is not SP1 yet... its because I dont have a
> recent enough backup INCASE something goes wrong ;)
>
> As for installing / uninstalling something recently, no. This server
> has not been touched installation wise since it was setup late last
> year.
>
> Will check out the links and let you know how I go, thanks for the
> help :)

Ok, sounds good.

Ace

Hi Ace

Checked out those links and a few others I found in passing.
I have tried reregistering DLL's and several other things. Nothing works...
the Server was freshly installed with SP2 R2 Disc's a couple of months ago.
It's not an old server with lots of baggage =P
I think I am just about ready to bite the bullet and call Microsoft =P
Unless you have anymore idea's? Thanks :)

"Ace Fekay [MVP]" wrote:

> In news:D4B95D55-F55F-434D-8CEA-16CC9C24DE0C@microsoft.com,
> Nomad <Nomad@discussions.microsoft.com> typed:
> > Thanks Ace.
> >
> > I know this isnt the Exchange Forum, this problem is more a Server
> > 2003 problem since ALL the VSS Writers are missing. I am posting this
> > before checking out those links you sent me :)
> >
> > As for why Exchange 2007 is not SP1 yet... its because I dont have a
> > recent enough backup INCASE something goes wrong ;)
> >
> > As for installing / uninstalling something recently, no. This server
> > has not been touched installation wise since it was setup late last
> > year.
> >
> > Will check out the links and let you know how I go, thanks for the
> > help :)
>
> Ok, sounds good.
>
> Ace
>
>
>

In news:F937C2B7-75B9-4818-B47C-56567F0356FE@microsoft.com,
Nomad <Nomad@discussions.microsoft.com> typed:
> Hi Ace
>
> Checked out those links and a few others I found in passing.
> I have tried reregistering DLL's and several other things. Nothing
> works... the Server was freshly installed with SP2 R2 Disc's a couple
> of months ago. It's not an old server with lots of baggage =P
> I think I am just about ready to bite the bullet and call Microsoft =P
> Unless you have anymore idea's? Thanks :)

No, I'm tapped out of ideas on this one other than seeing what the folks in
Exchange would say, even if it is an OS issue. Maybe related, who knows.

Ace

In news:%23Ycak%23AVIHA.4880@TK2MSFTNGP03.phx.gbl,
Ace Fekay [MVP] <PleaseAskMe@SomeDomain.com> typed:
> In news:F937C2B7-75B9-4818-B47C-56567F0356FE@microsoft.com,
> Nomad <Nomad@discussions.microsoft.com> typed:
> > Hi Ace
> >
> > Checked out those links and a few others I found in passing.
> > I have tried reregistering DLL's and several other things. Nothing
> > works... the Server was freshly installed with SP2 R2 Disc's a
> > couple of months ago. It's not an old server with lots of baggage =P
> > I think I am just about ready to bite the bullet and call Microsoft
> > =P Unless you have anymore idea's? Thanks :)
>
> No, I'm tapped out of ideas on this one other than seeing what the
> folks in Exchange would say, even if it is an OS issue. Maybe
> related, who knows.
> Ace

One more:

You may want to rebuild the VSS. This post may help.

How to rebuild VSSYou may want to Rename the System Volume Information
Folder that will rebuild the VSS. The following case is regarding the
problem of backing up VSS, ...
http://www.chicagotech.net/netforums...a13930483f52db

Ace

I having a problem with VSS also, I currently have a Microsoft support call
opened for it.

We are a BackupExec shop and it seems like ever since VSS came out we had
nothing but problems with it. I can say over the years and updates it is
getting better, when it works it is great but when it does not it can be a
pain.

I will post if and when Microsoft resolve my problem. They have yet
mention to rebuild anything yet.

Is VSS in improved in Windows 2008? I just wish their was better tools for
VSS to troubleshoot for us admins.




"Ace Fekay [MVP]" <PleaseAskMe@SomeDomain.com> wrote in message
news:uAmVHSMVIHA.4360@TK2MSFTNGP06.phx.gbl...
> In news:%23Ycak%23AVIHA.4880@TK2MSFTNGP03.phx.gbl,
> Ace Fekay [MVP] <PleaseAskMe@SomeDomain.com> typed:
>> In news:F937C2B7-75B9-4818-B47C-56567F0356FE@microsoft.com,
>> Nomad <Nomad@discussions.microsoft.com> typed:
>> > Hi Ace
>> >
>> > Checked out those links and a few others I found in passing.
>> > I have tried reregistering DLL's and several other things. Nothing
>> > works... the Server was freshly installed with SP2 R2 Disc's a
>> > couple of months ago. It's not an old server with lots of baggage =P
>> > I think I am just about ready to bite the bullet and call Microsoft
>> > =P Unless you have anymore idea's? Thanks :)
>>
>> No, I'm tapped out of ideas on this one other than seeing what the
>> folks in Exchange would say, even if it is an OS issue. Maybe
>> related, who knows.
>> Ace
>
> One more:
>
> You may want to rebuild the VSS. This post may help.
>
> How to rebuild VSSYou may want to Rename the System Volume Information
> Folder that will rebuild the VSS. The following case is regarding the
> problem of backing up VSS, ...
>
> http://www.chicagotech.net/netforums...a13930483f52db
>
> Ace
>

In news:%23mvtw6SVIHA.5208@TK2MSFTNGP04.phx.gbl,
Sabo, Eric <sabo_e@cup.edu> typed:
> I having a problem with VSS also, I currently have a Microsoft
> support call opened for it.
>
> We are a BackupExec shop and it seems like ever since VSS came out we
> had nothing but problems with it. I can say over the years and
> updates it is getting better, when it works it is great but when it
> does not it can be a pain.
>
> I will post if and when Microsoft resolve my problem. They have yet
> mention to rebuild anything yet.
>
> Is VSS in improved in Windows 2008? I just wish their was better
> tools for VSS to troubleshoot for us admins.

I am curious what Microsoft PSS has to say as well. As far as 2008, haven't
used it yet in production or tested it with Veritas. But my hopes are up
because there are many improvements in 2008.

Ace

Hey

Okay Microsoft Support Call opened.
Will let you's know how it goes...

Thanks for the help everyone so far! :)

"Ace Fekay [MVP]" wrote:

> In news:%23mvtw6SVIHA.5208@TK2MSFTNGP04.phx.gbl,
> Sabo, Eric <sabo_e@cup.edu> typed:
> > I having a problem with VSS also, I currently have a Microsoft
> > support call opened for it.
> >
> > We are a BackupExec shop and it seems like ever since VSS came out we
> > had nothing but problems with it. I can say over the years and
> > updates it is getting better, when it works it is great but when it
> > does not it can be a pain.
> >
> > I will post if and when Microsoft resolve my problem. They have yet
> > mention to rebuild anything yet.
> >
> > Is VSS in improved in Windows 2008? I just wish their was better
> > tools for VSS to troubleshoot for us admins.
>
> I am curious what Microsoft PSS has to say as well. As far as 2008, haven't
> used it yet in production or tested it with Veritas. But my hopes are up
> because there are many improvements in 2008.
>
> Ace
>
>
>

In news:BB8F0E27-2E0C-45DD-90D4-F3FA001272EB@microsoft.com,
Nomad <Nomad@discussions.microsoft.com> typed:
> Hey
>
> Okay Microsoft Support Call opened.
> Will let you's know how it goes...
>
> Thanks for the help everyone so far! :)
>

You are welcome. Waiting on what they say. :-)

Okay... problem / solution is!

The COM+ subscription information for VSS writers, stored in the registry
under the
HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key, is corrupted.

The exact cause and nature of this corruption is not always known as some
cases have been caused by running the 32-bit NewSID tool (from Sysinternal)
on an x64 version of Windows Server 2003.

Steps to fix it! :)

1. Export the contents of the HKLM\Software\Microsoft\EventSystem key to a
..registry file (as a backup).

2. Delete the
HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
key. (Just delete the Subscriptions subkey; leave the EventClasses key.)

3. Restart the server.

4. Run the "VSSADMIN LIST WRITERS" command.

This causes the VSS entries in the
HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key to be rebuilt when the writers initialize.

---

So really its my own fault for hitting it with NewSID and not doing a
SysPrep =P

"Ace Fekay [MVP]" wrote:

> In news:BB8F0E27-2E0C-45DD-90D4-F3FA001272EB@microsoft.com,
> Nomad <Nomad@discussions.microsoft.com> typed:
> > Hey
> >
> > Okay Microsoft Support Call opened.
> > Will let you's know how it goes...
> >
> > Thanks for the help everyone so far! :)
> >
>
> You are welcome. Waiting on what they say. :-)
>
>
>

In news:532A0694-F9DC-4D17-902D-FD3B781B0B95@microsoft.com,
Nomad <Nomad@discussions.microsoft.com> typed:
> Okay... problem / solution is!
>
> The COM+ subscription information for VSS writers, stored in the
> registry
> under the
> HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
> key, is corrupted.
>
> The exact cause and nature of this corruption is not always known as
> some
> cases have been caused by running the 32-bit NewSID tool (from
> Sysinternal)
> on an x64 version of Windows Server 2003.
>
> Steps to fix it! :)
>
> 1. Export the contents of the HKLM\Software\Microsoft\EventSystem key
> to a .registry file (as a backup).
>
> 2. Delete the
> HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
> key. (Just delete the Subscriptions subkey; leave the EventClasses
> key.)
>
> 3. Restart the server.
>
> 4. Run the "VSSADMIN LIST WRITERS" command.
>
> This causes the VSS entries in the
> HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
> key to be rebuilt when the writers initialize.
>
> ---
>
> So really its my own fault for hitting it with NewSID and not doing a
> SysPrep =P

Wow, cool. So you ran NewSID? I would have never thought of asking if this
is a cloned/ghosted machine. Good reason why I believed SID changers are not
reliable. Sysprep is the key!!

Did they reference and follow a KB article to help you?

I thank you for posting the info too. I am going to save this in my resource
pile to hopefully help me or future folks if the problem ever arises.

If you have any other concerns, please post back!

Hey

Yeah it had been NewSID'd.
Its a VM box... that had been copied from a generic install, but I forgot to
hit it with SysPrep and after the fact just did NewSID... now I know better.

Pretty happy with Microsoft of late, at least they have gotten over the
whole "its VMware its not supported go away" attitude. Most of the world
these days runs on VMware or similar software and Microsoft obviously see
this with Hyper-V for Server 2008 & are no longer turning people away from
support 'simply because you virtualize the box rather than run it physically'.

Thanks Ace for your help earlier in regards to this problem, much
appreciated! :)

"Ace Fekay [MVP]" wrote:

> In news:532A0694-F9DC-4D17-902D-FD3B781B0B95@microsoft.com,
> Nomad <Nomad@discussions.microsoft.com> typed:
> > Okay... problem / solution is!
> >
> > The COM+ subscription information for VSS writers, stored in the
> > registry
> > under the
> > HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
> > key, is corrupted.
> >
> > The exact cause and nature of this corruption is not always known as
> > some
> > cases have been caused by running the 32-bit NewSID tool (from
> > Sysinternal)
> > on an x64 version of Windows Server 2003.
> >
> > Steps to fix it! :)
> >
> > 1. Export the contents of the HKLM\Software\Microsoft\EventSystem key
> > to a .registry file (as a backup).
> >
> > 2. Delete the
> > HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
> > key. (Just delete the Subscriptions subkey; leave the EventClasses
> > key.)
> >
> > 3. Restart the server.
> >
> > 4. Run the "VSSADMIN LIST WRITERS" command.
> >
> > This causes the VSS entries in the
> > HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
> > key to be rebuilt when the writers initialize.
> >
> > ---
> >
> > So really its my own fault for hitting it with NewSID and not doing a
> > SysPrep =P
>
> Wow, cool. So you ran NewSID? I would have never thought of asking if this
> is a cloned/ghosted machine. Good reason why I believed SID changers are not
> reliable. Sysprep is the key!!
>
> Did they reference and follow a KB article to help you?
>
> I thank you for posting the info too. I am going to save this in my resource
> pile to hopefully help me or future folks if the problem ever arises.
>
> If you have any other concerns, please post back!
>
>
>

In news:8CD914E6-8041-4288-B05A-7A04100BA3EF@microsoft.com,
Nomad <Nomad@discussions.microsoft.com> typed:
> Hey
>
> Yeah it had been NewSID'd.
> Its a VM box... that had been copied from a generic install, but I
> forgot to hit it with SysPrep and after the fact just did NewSID...
> now I know better.
>
> Pretty happy with Microsoft of late, at least they have gotten over
> the
> whole "its VMware its not supported go away" attitude. Most of the
> world these days runs on VMware or similar software and Microsoft
> obviously see this with Hyper-V for Server 2008 & are no longer
> turning people away from support 'simply because you virtualize the
> box rather than run it physically'.
>
> Thanks Ace for your help earlier in regards to this problem, much
> appreciated! :)

Yes, I agree, so many are now using VMWare. Our own company is using it for
hosting clients' systems.

No prob for the help. It was my pleasure to try. After all the years I've
been in the groups, I still learn new things, and this was one of them.

Cheers!

Ace