More on thread478-1238477 - entitled "E8602 Failed to read from database". Regrettably, it got closed, but I learned more today. thread478-1238477 discusses why, in spite of everything, the Sql Agent stubbornly uses named pipes, which is utterly wrong for backing up a Sql Server 2005 database.
When the Sql Agent is installed on Windows Server 2003, I believe the key issue/answer is, under Control-Panel->Firewall, to explicitly add the TCP Port 6070 (guessing the port number from memory; y'better check).
You can find a key clue in the middle of page 31 (of 112) in the PDF Backup for Sql Server Agent manual which you can get from the Agent install. There it says the backup FIRST tries TCP/IP and, if that fails, it then tries Named Pipes.
That explains the behavior discussed in "E8602 Failed to read from database". If, under the WinServe 2003 firewall, the [expletive deleted] port is not explicitly opened, then the backup tries named pipes, in spite of upwards of 3 settings to the contrary!
While the Registry Edit reply is interesting, I do not think it's the answer. For me, fixing the firewall port worked far better!
Cringe!!
When the Sql Agent is installed on Windows Server 2003, I believe the key issue/answer is, under Control-Panel->Firewall, to explicitly add the TCP Port 6070 (guessing the port number from memory; y'better check).
You can find a key clue in the middle of page 31 (of 112) in the PDF Backup for Sql Server Agent manual which you can get from the Agent install. There it says the backup FIRST tries TCP/IP and, if that fails, it then tries Named Pipes.
That explains the behavior discussed in "E8602 Failed to read from database". If, under the WinServe 2003 firewall, the [expletive deleted] port is not explicitly opened, then the backup tries named pipes, in spite of upwards of 3 settings to the contrary!
While the Registry Edit reply is interesting, I do not think it's the answer. For me, fixing the firewall port worked far better!
Cringe!!