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

farooq

** WARNING: Banned **
Joined
Aug 12, 2006
Messages
24
Reaction score
0
Points
0
Website
Visit site
07-04-2007 14:06:13 Backup of AxProdSA failed.
07-04-2007 14:06:13 ACO5422E Received the following from the MS SQL server:
07-04-2007 14:06:13 [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'TDPSQL-00001374-0000'. Operating system error 0x80070002(The system cannot find the file specified.).
07-04-2007 14:06:13 [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is terminating abnormally. Microsoft SQL-DMO (ODBC SQLState: 42000) (HRESULT:0x80040c81)
07-04-2007 14:06:15 Backup of master failed.
07-04-2007 14:06:15 ACO5422E Received the following from the MS SQL server:
07-04-2007 14:06:15 [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'TDPSQL-00001374-0000'. Operating system error 0x80070002(The system cannot find the file specified.).
 
Problem has been resolved

here nothing to do with TDP it was an SQL issue
 
How did you fix this?

We're encountering the same problem after applying sp2 to the sql server...how did you resolve your issue? What was the problem? Thanks.
 
Sorry - I guess I didn't really mean ini - got Domino on the brain today... :(

The question is - does your MSSQL server know where it's datafiles are?
Is that related to your issue?
 
I hope so...sql server is up and the databases are available, and the datafiles didn't get relocated. The files mentioned in the error, like 'TDPSQL-00001374-0000', are just the names that TDP has come up with while backing up the databases, so I'm not sure why the OS would even need to know the location of those when a backup is attempted.
 
Last edited:
Well, I asked it that way b/c it appears - from the error - that the TDP is talking to the MSSQL server, right -
And that the MSSQL server passes back data of where the datafiles are -
Error being "(The system cannot find the file specified.)" is why I ask.

MSSQL may be able to start ok without knowing where anything but the default datafiles are located -
But if you tell it to back up something outside of that, would it generate an error similar to this?

Now I am just speculating by asking that question - I have not received that particular error. But are the end users of the database able to access anything other than the default db? Just a thought to ponder...

Hope this helps in some way.
-Chef.
 
The databases are completely available, I do not think that the datafiles are the files in question in regards to the "(The system cannot find the file specified.)" message.
 
Last edited:
after thought -

should have asked -

what OS, version of MSSQL & version of TDP are you using?
and have you tried uninstalling the TDP and reinstalling?

do the SQL Server error logs say anything?

-Chef
 
Last edited:
Windows 2003 Server SP 1, SQL Server 2005 SP 2, TDP 5.2.1.3. SQL Server error logs are clean, they just have errors logged each time a backup fails and it's the same error message that's in the output of the TDP backup. I've tried uninstalling and reinstalling TDP and still no luck...my last resort is to bounce the server.
 
Already tried surfing the web....that's how I came across this thread. The first link you provide is not helpful and gives a vague description of the error. The second link I had already found and was not helpful. I'm really just curious to hear from the person that originally started this thread as their error is exactly what I'm getting and they seem to have resolved it. Outside of that nothing else is really helpful.
 
Saw these notes in a TDP SQL ppt pres done by an IBM rep.
Just thought I'd share it with you...maybe you'll get something out of it.

Start by looking in the tdpsql.log.

Is there an HResult?
- Possibly SQL Server problem

Is there a Return Code and associated error from the TSM API?

The MS SQL log and vdierror.log are created in the logs directory for the SQL Server. For example:
c:\Program Files\Microsoft SQL Server\MSSQL\log

The vdierror.log is not created for all failures.

The windows event log should also be checked for any messages.
 
I'm getting same errors using 64bit Windows 2003 Server SP 1, SQL Server 2005, TDP 5.3.3.1. Tried re-installing, rebooting server.
 
see if you can try and register the sqldmo.dll file again...

also, would you happen to be in IA64? there is a MS hotfix that addresses some SQL issues on that platform, hotfix Q912021
 
Win 2008, SQL2005 Express, TDP 5.5 same error

Windows 2003 Sql2005 Express TDP 5.5

09/19/2008 14:59:02 ACO5422E Received the following from the MS SQL server:
09/19/2008 14:59:02 Full-text is not supported on this edition of SQL Server. (HRESULT:0x80131500)
09/19/2008 14:59:02 Backup of SQL Database master will not be attempted.
09/19/2008 14:59:02 ACO5422E Received the following from the MS SQL server:
09/19/2008 14:59:02 Full-text is not supported on this edition of SQL Server. (HRESULT:0x80131500)
09/19/2008 14:59:02 Backup of SQL Database model will not be attempted.
09/19/2008 14:59:02 ACO5422E Received the following from the MS SQL server:
09/19/2008 14:59:02 Full-text is not supported on this edition of SQL Server. (HRESULT:0x80131500)
09/19/2008 14:59:02 Backup of SQL Database msdb will not be attempted.
09/19/2008 14:59:02 ACO5422E Received the following from the MS SQL server:
09/19/2008 14:59:02 Full-text is not supported on this edition of SQL Server. (HRESULT:0x80131500)

I was told by IBM that they do not support express. But I know there has got to be a simple work-around.
 
Last edited:
Back
Top