VSS Event Error 12289 when doing System State backup

[Duelund]

I have just installed two domain controller, with Windows Server 2003 Std.
with SP1 included.

On both servers I have setup Ntbackup to do a System State backup and on
both I get the following error in the Application event log:

--------------------------------------------------
Source: VSS
Category: None
Type: Error
Event Id: 12289
Description:
Volume Shadow Copy Service error: Unexpected error OpenService
(shSCManager, 'VSS', SERVICE_QUERY_STATUS). hr = 0x80070005.
--------------------------------------------------

Immediatey after come these two events:

--------------------------------------------------
Source: ESENT
Category: ShadowCopy
Type: Information
Event ID: 2001
Description:
Isass (552) Shadow Copy 6 freeze started.
--------------------------------------------------
and
--------------------------------------------------
Source: ESENT
Category: ShadowCopy
Type: Information
Event ID: 2003
Description:
Isass (552) Shadow Copy 6 freeze stopped.
--------------------------------------------------

and the backup log says:

--------------------------------------------------
Backup Status
Operation: Backup
Active backup destination: File
Media name: "SystemStateBackup.bkf created 07-08-2005 at 23:00"

Volume shadow copy creation: Attempt 1.
Backup (via shadow copy) of "System State"
Backup set #1 on media #1
Backup description: "Set created 05-08-2005 at 09:17"
Media name: "SystemStateBackup.bkf created 07-08-2005 at 23:00"

Backup Type: Copy

Backup started on 07-08-2005 at 23:00.
Backup completed on 07-08-2005 at 23:01.
Directories: 220
Files: 2540
Bytes: 523.864.456
Time: 1 minute and 20 seconds
--------------------------------------------------

so it seems like the backup is running Ok with ShadowCopy - so how do I get
rid of the 12289 error ?

--
Regards
Bjarne Duelund

[lukesh]

Hi,
This is a bug with VSS after installing SP1. This error is BENIGN, it
indicates no actual issues, the backups should work as expected without any
issues. This may be fixed in SP2.