Hi Del,
This ends up with that the DBA have turn on something called AUTO_CLOSE to 
TRUE, if we change it to FALES TSM for DB works fine.

When I read this artical 
http://blogs.msdn.com/b/buckwoody/archive/2009/06/24/sql-server-best-practices-autoclose-should-be-off.aspx
I think this could be a config that many DBAs are using for small applications.

Why can't TSM for DB handle this parameter?

Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
Supported Platform for CPU2TSM:: 
http://www.cristie.se/cpu2tsm-supported-platforms

________________________________________
Från: Del Hoobler [hoobler AT US.IBM DOT COM]
Skickat: den 3 oktober 2011 18:44
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Re: TDP SQL reports back ACO5422E

Hello Christian,

If you continue to have this issue, please open a PMR.
IBM Support can gather a trace to help pinpoint the problem.
HRESULT: 0x80004002 could point to a problem with Windows COM.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 09/27/2011
04:19:26 AM:

>> From: Christian Svensson <Christian.Svensson AT CRISTIE DOT SE>
>> To: ADSM-L AT vm.marist DOT edu
>> Date: 09/27/2011 04:43 AM
>> Subject: TDP SQL reports back ACO5422E
>> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>>
>> Hi,
>> I was hope to find some light here at the forum.
>> I have a Windows Server 2003 SP2 with a MS SQL Server 2005
>> Enterprise installed.
>> I have installed TSM BA Client 6.2.3.0 and TSM for MSSQL 5.5.5.1
>> and the TSM Server version is 6.2.3.0
>>
>> But when I try to run a backup of our MS SQL Server via GUI does a
>> got a ! sign on a couple of databases (only 5 of 50 db).
>> When I try to backup does databases I got an error "ACO5422E
>> Recived the following from the MS SQL Server: Specified cast is not
>> valid. (HRRESULT: 0x80004002)"
>> But when I try to backup the databases that doesn't have any marks
>> on them it works OK.
>>
>> I have look around on the web and found following artical but none
>> of them working for us.
>>
>> http://adsm.org/forum/showthread.php?24035-Some-database-of-MS-SQL-
>> Server-can-t-be-backed-up-using-TDP-for-database
>>
>> http://adsm.org/forum/showthread.php?23467-How-can-I-exclude-a-
>> single-database-from-a-TDP-MSSQL-backup
>>
>> We have also try to create a dedicated backup account in SQL that
>> has full access to everything but that has the same issue if I try
>> to use "Integrated" account option in TSM for DB.
>>
>> I have also involved some DBAs and they can dump the database to a
>> flat file without any issue. I have also ask them to compare the
>> databases that works and not working. But I haven't heard anything back
yet.
>>
>> Thanks in advanced for your help and suggestions that maybe solve this
issue.