12-17-2012 03:43 AM
Hi,
I would like to ask about my problem above. I'm unable to start the BE Device & Media Service as it's giving me the said error. I've tried doing the solutions mentioned in the KB
http://www.symantec.com/business/support/index?page=content&id=TECH59527
until Solution 3 in which clicking OK give me an error:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)
Currently downloading WinServer 2003 SP2 to reinstall the service pack mentioned on Solution 4.
I've also tried doing a connectivity test for SQL as mentioned here:
http://www.symantec.com/business/support/index?page=content&id=TECH24708
But get an error when selecting the database on Step 5.b.
[DBNETLIB][ConnectionOpen(SECDoClientHandshake()).]SSL security error.
Logon failed. Catalog information could not be retrieved.
Has anyone faced this kind of error before? Would really love any ideas that could shed light on this and probably resolve the issue. Thanks.
This is happening on the backup server, if I may add. Don't want to do a full install again (as what my senior did before) just to fix the problem as much as possible.
Solved! Go to Solution.
12-24-2012 11:12 PM
12-17-2012 07:34 AM
Try this...From X:\Program Files\Symantec\Backup Exec, open BEUtility.exe
Highlight All Media Servers & choose your server in the right pane...Right-click & choose change database access...enter the account which is used for the Backup Exec services & choose grant access...
Alternatively, if you change the backup exec services to use a local system account, do the services start ?
12-17-2012 07:42 AM
Hi VJware,
I have tried changing the service account to Local System with the same error. And BEUtility is unable to grant access to the database for the domain account that we've been using before.
12-17-2012 07:49 AM
In addition, tried doing a repair install just to see if it would work. But during the installation phase, I was getting "can't establish a connection" error for 3x.
The dbrecover.log has this status:
Status: DBU_ERROR_DATABASE_ATTACH_FAILED.
Intially, it had a BAD_LINKAGE message.
12-19-2012 02:34 AM
Currently looking at a possible SQL access denial since I'm getting a 0x80004005 error code which, as what other people are saying from other threads here, is an Access Denied error on the SQL instance.
12-24-2012 11:12 PM