SQL DB Backup failed with "ACO5422E Received the following from the MS SQL server"

[etchingsj]

Ok, well here I am a month later and due to a enterprise password change I am getting this error again on one of my SQL servers.
I am working to resolve now. BUT the only thing that has changed between yesterday when the TDP backups were successful and today now that they are failing is the Enterprise Admin password change.

 

[moon-buddy]

Did you use the Enterprise Admin password to create the TDP Scheduler, or setup the TDP instance?

The TSM TDP backups should not be affected by this change if the account that backups up the SQL database has system access/rights.

 

[etchingsj]

These nodes were configured before I started with this shop but that was my first suspicion. I have since noticed that the .cmd scripts that TDP leverages run from the root of C:\ based on a scheduled task which was configured using the Enterprise admin password.

I have reconfigured them to run as System.

Thanks for the assistance,

 

[daya]

ACO5422E Received the following from the MS SQL server:07/03/2009 22:16:37 Could not load file or assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

 

[rodri-pit-bull]

Hello my friend,

I am having the same error in a SQL client node, which applied solution to the problem?

Then the error;

08/02/2010 19:14:34 Backup of SQL Database ASPState Will Not be attempted.
08/02/2010 19:14:34 ACO5422E Received the Following from the MS SQL server:
08/02/2010 19:14:34 Text is not compatible with this edition of SQL Server. (HRESULT: 0x80131500)


Client Node: TSM v6.1 baclient
TDP for SQL 5.3.3.0 data base

OS: Windows Server 2003

Thanks for the help :up:

 

[Hiten]

Hi,

I am having Windows 2000 OS with SQL TDP 5.2.1 i checked the vdi.log found below message.
2013/01/19 13:28:48 pid(2844)
Error on TDPSQL-00000B1C-0000
Error at TriggerAbort: invoked

 

[trolladin]

Hi,

Thanks Eric06, i chose to set the troubleing database on "false" for auto close and the full backup worked as a charm.

 

[Mehdi]

I was facing similar issue, but it is fixed now.

Could you please check if this issue is occurring on Windows cluster & if yes .. check if you are trying to run TDP job on correct cluster where the resource group is online

just 1 cent from me ......