ARCSERVE 2000 Error (E8604) After SP3 & Fixes Applied

[Robbo19]

Arcserve 2000 on NT 4.0 SP5
Exchange Server 5.5 with Client Agent for NT

OK, so I've been following the threads here for a while now, and I thought Arcserve Guru had the fix for my problem, and I thought it would work, but it didn't. First, I was getting this error message...

E8602 Failed to read from database. (DBNAME=Individual Mailboxes\...\..., EC=Backup Agent Error --(69) "Read/Write error in named pipes.".)

... each individual's mailbox.

This happened for a few days, before I could do anything, the error message I started getting was this...

E8601 Failed to connect agent. (AGENT=dbaxchg2, EC=318)

... I wasn't sure if it would help or not, but I figured it couldn't hurt if I applied SP3 (for the main server and on the Exchange server as well) and the QO06202 patch. But, on my next backup, the job hangs at 99%, and I get this error message...

E8604 Failed to start backup. (DBNAME=\Individual Mailboxes\..., EC=Backup Agent Error -- (68) "Error status in named pipe.".)

... so, I am thinking that perhaps my Exchange database is corrupted, and while this may not be the right forum for this question, What should I do if that is the case?

Thanks in advance,

Rob

 

[ARCserveGuru]

hi Rob, the best thing to do would be to run the exchange database utilities such as isinteg or edbutil and the like this is good for checking database corruption.

However, I don't think your exchange database is corrupt. Do you have any exchange specific antivirus or any other antivirus running on there? If you do try a backup whilst it is disabled.

The chances of this resolving the issue is low, so get back to me if it doesn't work and I'll get right on asap.

Also after you do this, don't forget to bounce (stop and start) the backup agent RPC service on the exchange server.

good luck

guru

 

[Robbo19]

Thanks for the suggestions. However, due to other reasons, we had to shutdown the server for a while, and when we brought it back up, I decided to just delete and recreate all the Arcserve jobs and such. Well, everything is now back in working order. Go figure. Thanks for the help anyway.

- Rob