Serious issue with BE 8.6 and SQL 2000

[Guest_imported]

I just upgraded to SQL 2000 and found that BE 8.5 would not back it up. So I upgraded to BE 8.6 with the Open Option Suite. I tried to back up my SQl database and I get the error message "Unable to attach to \\Servername. A network connection to the device could not be established." I am running Enterprise manager for SQL 2000 on the Backup server and I am able to register the SQL server in enterprise manager as well as set an ODBC source up for the server. I can Ping it and I can backup other files on the SQL server but just not the SQL database.... Does anyone have any idea what my problem is. I hope so because Veritas does not even address this issue.

 

[bobafet]

http://seer.support.veritas.com/docs/233862.htm

Troubleshooting basic "access denied" messages with Backup Exec for Windows NT and 2000.

What event ID's are you getting?

 

[jamkey]

There is an issue with 8.6 and sql 2000 where if you are running multiple instances of SQL and one of the instance names plus the computer name adds up to more than 15 characters then you get an "item not found" or "device not found" error which sounds like the equivalent of what you are getting. Go to support.veritas.com, then click on product listing > Backup Exec > Backup Exec for Windows NT and Windows 2000 > View all patches and updates.

On this next page choose the following filter options: Patch, English, 8.6. There you will see the SQL hotfix. If that doesn't help, then go back to the page where the "view all patches & updates" link was and instead choose "knowledge base search". Then search for the exact error you are getting. Definitley look at the help for the search engine, its not very intuitive in terms of how to do more complex searches.

 

[kevin12345]

Did you ever find a resolution to this? I'm having the exact same problem. None of the suggestions above, nor any of the tech docs on Veritas' site fix it. I'm using the domain admin account, I set up the services to log in with that id instead of as a service, I tried blowing out the password file and recreating, nothing works. This is a brand new install of Win2K Server sp2 with latest patches and Backup Exec v8.6 build 3878.

 

[chrissz]

I am seeing this also. I can connect to remote servers, but if I try to set up a job that backs up a remote server that has the remote agent pushed to it, I get the message asking me for an account to use to connect to this resource. I give it a domain admin account, or I try the Veritas service account (which also has administrative priveleges) and it refuses the connection.

What gives?

 

[jamkey]

Have you tried the SA account? I believe there was an issue w/ NT authentication in SQL that was supposedly addressed by one of the SQL service packs but from what I've heard not all issues were addressed. For instance, if you search "google" for 'SQL AND 10003 AND Microsoft AND error' you will find a workaround procedure for allowing an NT account to connect to a SQL db. That also brings to mind the aspect of SQL network libraries. Check the Network libraries for the 'Client Network Utility' that are part of the SQL client connectivity tools installed on the Backup server and compare the exact version #'s to the Network Libraries for the 'Server Network Utility' found in the SQL menu group on the SQL server itself. You might also want to try seeing if the MSSQL service is running on an actual account. As long as there aren't 2 SQL servers replicating data to each other via the SQL tools I would suggest stopping the MSSQL service, setting it to run on 'Local System Account' and then restart it.

The most recent BENTTOOL from Veritas also has a hand Password db editor (PWDBEDIT.EXE) that lets you see the custom account being used for each resource that is backed up with an account other than the BENT services account (did i use the word 'account' enough in that last sentence). Hope that's enough suggestions to tide you over. Other than that, I'd say you may have to give their tech support a call. (Don't forget to try logging on to the BENT server using the BENT account and open SQL Query analyzer to test the connection to the SQL server).