If this is a systemstate backup error, it's not surprising.  Even with all
the MS patches on, and with VSSADMIN LIST WRITERS showing no error, you'll
occasionally have issues with VSS doing system state backups.
It will either clear up on its own, or you'll have to schedule a reboot to
make it go away.

OTOH, do you have TSM Open File Support enabled on teh Win2K3 client?  And
are you using it for something in particular?

I tell my customers NOT to enable Open File support on Windows except in
very rare cases.

Open File Support does not give you valid backups of most Windows locked
files (like SQL DB's, for example).  The only time you should use it, is if
you have a particular application that you know you can get valid backups
with Open File Support, and no other way.  And the reason to have it turned
off, is that if it is enabled you tend to get bogus errors like this from
it.

"VSS is like a Nose, sometimes it Runs, sometimes it Blows" -- me


On Mon, Jul 13, 2009 at 7:09 AM, Markus Engelhard <
markus.engelhard AT bundesbank DOT de> wrote:

> Dear all,
>
> has anyone come across the following eventlog error message while backing
> up a W2K3 client?
>
> Volume Shadow Copy Service error: Unexpected error calling routine
> MoveFileExW
>
> TSM backups work, nothing in the TSM error log or schedlog. No change,
> client has been working happily for quite a while like 1000+ others.
> VSSADMIN LIST WRITERS returns no error.
> I don't believe it is a TSM issue in the end.
>
> I'm just curious as MS, IBM, google and the forum don´t come up with much
> apart from NetBackup stuff from 2005 and Windows 2000 cluster errors dating
> way back.
>
> VSSADMIN LIST WRITERS returns no error.
>
> TSM Server is Solaris9, TSM Version 5.5.2.1
> TSM Client is Window2003, current os patches (deemed essential for VSS to
> work, been through that)
> TSM Client Version 5.3.4.0 (I know, out of service, but hard to keep up in
> a large environment)
>
> Thanks for your help, all the stuff on the forum is really appreciated!
>
> Markus
>
>
> --
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.
>
> Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
> Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
> raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
> Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
> grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
> virenbefallene Software oder E-Mails aus.
>
> Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
> schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
> irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
> ______________________________________________________________________
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of  the material in this
> e-mail or of parts hereof is strictly forbidden.
>
> We have taken precautions to minimize the risk of transmitting software
> viruses but nevertheless advise you to carry out your own virus checks on
> any attachment of this message. We accept no liability for loss or damage
> caused by software viruses except in case of gross negligence or willful
> behaviour.
>
> Any e-mail messages from the Bank are sent in good faith, but shall not be
> binding or construed as constituting any kind of obligation on the part of
> the Bank.