Hi, Please help.
I have backup exec 2012 and IBM 3572-TL backup tape. I've installed SP1 of backup exec and hotfix 180964, 189571, 194470, 199866, 200433. After installation and do inventory of the tape I'm receiving error: The request channel timed out while waiting for a reply after 00:09:59.9980000. Increase the timeout value passed to the call to Request or Increase the sendTimeout value on the Binding. The time alloted to this operation may have been a portion of a longer timeout.
Whenever I do inventory of the Tape im receiving error below. I hope you can help me resolve this issue.
...the only TN around this refers to a NAS, which you don't mention having.
Try removing the library completely from both BE and Windows, and restart the server. Run tapeinst.exe to install the drivers.
Also make sure that no firewall is blocking the BE services, and if so, either open those ports up or put in exclusions.
For the error above, check the TN:
backup exec database (bedb) schema does not match the installed version
did you perhaps upgrade from a previous version? If so, it looks like it didn't complete successfully!
Tried to run the command above. Here's the result:
[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused by
the fact that under the default settings SQL Server does not allow remote
I also run BE Utility and then run Diagnostic Tool and still received the 5 error above. When I test run backup job, it has no error, however, when run Inventory of the tape still got the Request Channel Timeout error,
...do you have any jobs configured, and have any of them run? If not, then you can use BEutility.exe to drop your existing database and load from base...this gives you a clean BEDB. Try running your task again that currently gives you your error.
If you already have jobs that have run, then you can still do the above, but you need to grab a copy of bedb.bak first...follow the TN below to do so, and then reload the bedb.bak once your testing is complete...
Just grab a copy to a different location...this will indicate any possible corruption in the BEDB.