Volume Shadow Copy Service & BackupExec 9.1

Hi all

I have recently had to run a repair install of Win2003 Server, which appeared to go well.  I then installed BackupExec 9.1 but I cannot get it to work with VSS.  Everytime the backup runs, it fails at 99% with an 'out of memory' error, despite having run (apparently) perfectly well on a previous installation.  It makes no difference whether the backup is set to 'verify' or not.

I have obtained two patches from Microsoft, which are supposed to address a known memory leak in VSS which is alleged to cause this problem with 3rd party backup software.  They have not made any improvement - and that's where MS's support ends. Thanks a lot fellas!!

I've read various notes about this, but I cannot seem to get to the nub of the problem - possibly due to my own inexperience.

The log from vssadmin, run just after a failed job (as per MS suggestion) reads thus:

VSSADMIN LIST WRITERS
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {52a13681-47d7-40ca-b278-12cb8d19e0f6}
   State: [9] Failed
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {81754435-c4a2-47b4-a764-8647e8a8653d}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {8cb5e2e7-66a6-4d9b-a391-03f93d660044}
   State: [9] Failed
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {78b4156f-eea1-460d-ab2d-bf7d26af47c7}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {9532e961-cbff-4dc4-a12c-507e396823b9}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {e09e2539-7d54-4219-a457-70f5d2f968ed}
   State: [9] Failed
   Last error: No error

Writer name: 'Removable Storage Manager'
   Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
   Writer Instance Id: {7f1d8b1a-9c47-411b-b1f7-2d39fe6c837a}
   State: [9] Failed
   Last error: Non-retryable error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {d64c3b1e-cadf-4929-8577-ea70c0a31314}
   State: [9] Failed
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {e96b7901-8063-4357-88ac-1454b4cc3705}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {8e9fdd83-fc5c-481d-82af-353718745bdc}
   State: [9] Failed
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {aa61d240-d5ab-468a-bca2-3b28ee4663cd}
   State: [9] Failed
   Last error: No error

Event Logs:

tcpsvcs (2732) The backup has been stopped because it was halted by the client or the connection with the client failed.

Backup Exec Alert: Job Failed
(Server: "AML-SERVER") (Job: "Full Backup") Full Backup -- The job failed with the following error: Ran out of memory
 
BE Job log:

Backup - AML-SERVEROFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
OFO: Snapshot error (0x8007000e): Ran out of memory
(Open file option is not available on the version we have of BE, but they say on their website that it comes up anyway when it fails in this way.)

In addition, although I check that the VSS is running before starting the backup, it stops during the backup, though at precisely which point, I don't know.

Does any of you have any ideas on this?
One thought that occurred to me is that, as it all used to work ok under the previous installation, could it be a recent Windows update which has caused the problem?

Thanks very much.