VSS restarts server

Every update is done to my server but SP1

I get this right before a reboot:
The Microsoft Software Shadow Copy Provider service entered the running state.

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

Then:
The previous system shutdown at 10:31:57 PM on 4/10/2006 was unexpected.

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

This is the time when Symantec (Veritas) Backup Exec 10d is running a backup on the server.

Anyone seen this issue before?
rceballosAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TheCleanerCommented:
Haven't seen that one...i have 10d.

Is there any event errors or hex code errors in the backup job when it runs?
0
rceballosAuthor Commented:
i get this error on backup job:
Backup- BBCORP6AOFO: Initialization failure on: "\\BBCORP6\C:". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
0
rceballosAuthor Commented:
it does not happen everyday...only on occasion...and only on this server.
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

TheCleanerCommented:
Try changing the backup start times slightly just to make sure it's being caused by the backup.

Also, check the application log and system log for any errors that occured before the backup start time.

That's pretty strange...
0
rceballosAuthor Commented:
tried that as well...it is most definitely veritas when it is pre processing the AOFO agent.
0
TheCleanerCommented:
Do you have the advanced file option installed on the client server?  Are you checking the box for AOFO without the agent installed?
0
rceballosAuthor Commented:
yes i do, and yes i have tried that and it works fine. The AOFO uses the VSS to create a snapshot.
0
TheCleanerCommented:
Have you tried forcing it to use the Veritas Snapshot provider instead?  Just to test.
0
rceballosAuthor Commented:
havent tried that...but will give it a try.
0
rceballosAuthor Commented:
I will try that
0
hstilesCommented:
It's a Symantec Antivirus CE v 10.01 bug - it causes Windows 2003 servers to BSOD.  The Symantec website is devoid of any articles on this topic, but you need to obtain an update for SAV that patches the symevnt.dll.

If you want to test, try scheduling ntbackup to back up system state to a file and remove shadow copy components from your server back ups for a couple of nights.  I can pretty much guarantee the servers won;t BSOD.
0
TheCleanerCommented:
Well, he never said he was running Symantec A/V, so I wouldn't guarantee your answer is right hstiles.  But if it is, you are one intuitive EE expert.
0
rceballosAuthor Commented:
haha...hstiles has some voodoo with him because i am running Symantec AV 10.01...ill get the update from symantec and let you guys know.

BTW, tried different snapshot provider and micrsoft said screw you, you can only use ourse since your backing up system state.
0
rceballosAuthor Commented:
hstiles i can not find that .dll file on the server.
0
hstilesCommented:
rceballos - an error on my part, I believe the affected file is symevent.sys.  Symantec should be shot for not publicising the issue more on their website.  It took several calls to get them to ackonwledge the error and supply the patch, which fixed the problem instantly.

TheCleaner - inuititive expert - no.  I just had the misfortune of coming in one morning to find that nearly every one of my servers BSODed one night after rolling out SAV CE 10.01.  There's an argument for having a proper test procedure.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rceballosAuthor Commented:
Thanks hstiles...no reboot so far...ill hunt you down if it happens though! :P
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

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.