Steve-- had those errors on a clustered (in more senses of the word than one) 
file/print server.  According to the documentation provided by those that 
actually worked with MS and performed the fix:


Following changes were made to the registry:

Windows Registry Editor Version 5.00 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters] 
"MaxMpxCt"=dword:00000032 
"autodisconnect"=dword:00000000 (was ffffffff hex value) 
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session 
Manager\Memory Management] 
"PoolUsageMaximum"=dword:00000028 
"PagedPoolSize"=dword:ffffffff 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] 
"TcpTimedWaitDelay"=dword:0000001e 

Installed VSS patch in MS KB 940349
Reboot server 
Start Poolmon 
Start Perfwiz

No errors since update


thanks!
lisa 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Steven Harris
Sent: Wednesday, April 30, 2008 8:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] ANS9999E Win32 RC 1450

Hi All

I have a new client with an enormous file server, running Windows 2003.  We 
have had a string of problems, most have been fixed by upgrade to TSM client 
5.5.0.4 and OS upgrade to SP2.  We are using MEMORYEFFICIENTBACKUP=DISKCACHE  
but still get

ANS9999E Win32 RC 1450  as noted in
http://www-1.ibm.com/support/docview.wss?uid=swg21251903

Pointing at the Faulty OS or poor implementation doesn't solve the problem.
This is the client's main file server and hasn't yet had a clean backup.

Has anyone else seen this issue,  and developed a workaround that you'd like to 
share?  All I can think of at this point is a series of backups of various 
subtrees,

Thanks

Steve.

Steven Harris
TSM Admin, Sydney Australia