VSS Error Event ID: 8193 and Application Popup 333

[Guest nja]

Hi!

 

I've got some trouble with our Fileserver. Everytime I restore a shadow copy

(I use shadow copys for shared folders), there are errors in the Eventlog.

First of all, the Eventlog is full of ApplicationPopup 333 errors.

During the Backup job for all the Server, there is an error at the

fileserver, and the backup Job aborts.

I use Symantec BackupExec for the Tape Backup.

This is the Event ID from the Fileserver Eventlog, wich generates the Backup

error:

 

Product: Windows Operating System

ID: 8193

Source: VSS

Version: 5.2

Symbolic Name: VSS_ERROR_UNEXPECTED_CALLING_ROUTINE

Message: Volume Shadow Copy Service error: Unexpected error calling routine

%1. hr = %2.

 

hr = 0x800703f8

 

The interesting thing is that this EventID is only in the Eventlog if the

AplicationPopup Event was there before.

The only way to stop the ApplicationPopup Error is to restart the Server.

 

Operating System: Windows Server 2003 R2 SP2. The Server is a file and print

server.

Can somebody help me?

 

Regards nja

[Guest Thee Chicago Wolf]

Re: VSS Error Event ID: 8193 and Application Popup 333

 

>I've got some trouble with our Fileserver. Everytime I restore a shadow copy

>(I use shadow copys for shared folders), there are errors in the Eventlog.

>First of all, the Eventlog is full of ApplicationPopup 333 errors.

>During the Backup job for all the Server, there is an error at the

>fileserver, and the backup Job aborts.

>I use Symantec BackupExec for the Tape Backup.

>This is the Event ID from the Fileserver Eventlog, wich generates the Backup

>error:

>

>Product: Windows Operating System

>ID: 8193

>Source: VSS

>Version: 5.2

>Symbolic Name: VSS_ERROR_UNEXPECTED_CALLING_ROUTINE

>Message: Volume Shadow Copy Service error: Unexpected error calling routine

>%1. hr = %2.

>

>hr = 0x800703f8

>

>The interesting thing is that this EventID is only in the Eventlog if the

>AplicationPopup Event was there before.

>The only way to stop the ApplicationPopup Error is to restart the Server.

>

>Operating System: Windows Server 2003 R2 SP2. The Server is a file and print

>server.

>Can somebody help me?

>

>Regards nja

 

See if any of the suggestions from here help:

http://www.eventid.net/display.asp?eventid=8193&eventno=1994&source=VSS&phase=1

 

- Thee Chicago Wolf

[Guest nja]

Re: VSS Error Event ID: 8193 and Application Popup 333

 

 

Thanks for the link, but nothing there helped =(

 

 

 

"Thee Chicago Wolf" wrote:

> >I've got some trouble with our Fileserver. Everytime I restore a shadow copy

> >(I use shadow copys for shared folders), there are errors in the Eventlog.

> >First of all, the Eventlog is full of ApplicationPopup 333 errors.

> >During the Backup job for all the Server, there is an error at the

> >fileserver, and the backup Job aborts.

> >I use Symantec BackupExec for the Tape Backup.

> >This is the Event ID from the Fileserver Eventlog, wich generates the Backup

> >error:

> >

> >Product: Windows Operating System

> >ID: 8193

> >Source: VSS

> >Version: 5.2

> >Symbolic Name: VSS_ERROR_UNEXPECTED_CALLING_ROUTINE

> >Message: Volume Shadow Copy Service error: Unexpected error calling routine

> >%1. hr = %2.

> >

> >hr = 0x800703f8

> >

> >The interesting thing is that this EventID is only in the Eventlog if the

> >AplicationPopup Event was there before.

> >The only way to stop the ApplicationPopup Error is to restart the Server.

> >

> >Operating System: Windows Server 2003 R2 SP2. The Server is a file and print

> >server.

> >Can somebody help me?

> >

> >Regards nja

>

> See if any of the suggestions from here help:

> http://www.eventid.net/display.asp?eventid=8193&eventno=1994&source=VSS&phase=1

>

> - Thee Chicago Wolf

>

[Guest Thee Chicago Wolf]

Re: VSS Error Event ID: 8193 and Application Popup 333

 

>Thanks for the link, but nothing there helped =(

 

There are more updates for VSS on non-R2 than there are for R2. You

might want to try a few of the hotfixes that are out there and at

least bring up the VSS components to as current as they could be to

see if it helps. Take a look at some of the KB hotfixes and apply them

if you like to see if they help any:

 

http://support.microsoft.com/kb/943669

http://support.microsoft.com/kb/940252

http://support.microsoft.com/kb/935460

http://support.microsoft.com/kb/956000

http://support.microsoft.com/kb/887013

 

- Thee Chicago Wolf