Error 4101unable to login to database engine

[xp2002]

I get this error lately:
E4101 Unable to login to database engine (DATABASE=CASDB, EC=-2005)

I've tried to stop and start the services using cstart.bat and cstop.bat, but no result.

Also a problem is that the logfile sometimes gets corrupted (rubbish in the log, looks like binary data)

Doen anyone have a solution, because it seems that the backup doesn't work.

Thanks,
Angelo

 

[xp2002]

Ok, the solution in _this_ case:
The C-drive where Brightstor resides was full. We had 3 mb free space, so that's the reason that
- logfile was corrupted.
- and the database couldn't be connected.

Hope this helps for anyone who has this problem too.

grtz,
Angelo

 

[Nightwatch]

This is a frequent problem with their DB, Best thing to do is either Reinitialize the database in the Server Admin - you lose everything! You will be required to Merge tapes to do a restore. Fun eh?


Have the guys at CA send you a new DB via e-mail and keep it handy, you're gonna need it every so often.

 

[mohamdr]

Hi
Use the below doc to repair your database

http://support.ca.com/techbases/as2000/as2k-1521.html

http://support.ca.com/techbases/as2000/as2k-18200.html

regards,
mohamdr

 

[davidmichel]

Here is the definition from the Velosis manual.
Error code -2005 = S_SVRUNAVAIL
Server unavailable (i.e., doesn’t exist).
The network has run out of resources (connections) and has rejected the connect request.

So in this case the first thing to check would be free disk space.

 

[xenotec]

Check the RNName Variable on the server. If it doesn't match the server name then you need to do that.
Also, Check the ARCserve account details in the Server Admin

 

[vaderborg1]

I have had a problem with a server causing this error. You can't even run rdsadm.exe. I stopped the database engine. Then, I went to the database directory, c:\progra~1\ca\Bright~1\database, and deleted the rAAAAAAE.chg, rdm.chi, and rdm.chk files. The rdm.chk was really large. There were a couple of server crashes before this error occurred. I restarted the database, and it is working properly again.

This used to be a fix for ARCServe 6.0! Good luck!