E8602 Failed to read from Database

[eripley]

I'm trying to backup an Exchange Server on my Cluster. It worked fine when we had ArcserveIT 6.6 installed, but since the Arcserve 2000 upgrade ... I keep getting the above error when trying to backup Exchange (not at brick level).

Have looked on CA's site, but can find no solution. Actual error reads - E8602 Failed to read from Database (DBNAME=Information Store, EC=). So I'm not even getting an error code either.

Any ideas? Any help appreciated.

 

[cgwillard]

Did you upgrade your ArcServe Exchange agent when you upgraded ArcServe? When you set up your backup jobs in ArcServe, did you set up the security for that backup agent (I think ArcServe suggests "dbagent&quot? Can you try a brick-level backup just to test the communication? cgwillard
Only 25 years until retirement!

 

[Guest_imported]

I have the same problem!

It is very strange that exchange agent (on cluster too) worked fine for about one year! There is also an MS article (Q297172) but it did not help me too.

 

[eripley]

To cgwillard:

Thanks for your reply. I didn't really upgrade, because the older versions were installed before I worked for the Company. Therefore, I uninstalled all agents, then installed the new Arcserve 2000 Exchange Agent as new.

Yeah, I created an account for the Exchange Agent, and granted it all the necessary rights and permissions. The daft thing is, that the log shows that the account can connect to the database, but it cannot READ from it?!?!

Haven't tried a brick level yet, no. Was planning to do so at some point, but I really need to sort out this problems with the Exchange database first.

 

[skimmilk]

We had this same problem about two years ago using ArcServeIT 6.61. We ended up doing a defrag (Eseutil.exe) on the exchange Private Info. Store (Priv) and the Public store (Pub),that fixed the problem up until two weeks ago. We tried the defrag thing twice and it hasn't fixed the problem yet. Still searching for answers. Good Luck

 

[drizzits]

I have been having simular problems. I set the approperate permisssions for my backup account SRCarcserver but then when I run the dbagent it tells me it can't use that account. I will put in a user account and it will except it. Confused. I am gettign these errors

395 E8604 Failed to start backup. CDNAME = dbaexchis, EC= Backup Agent Error - (331)" Insufficient privelege. Please check user privelege",)

393 E8602 Failed to read from database (DBNAME = Individual Mailboxes\Administrator\Inbox, EC = EXCH Exchange Agent - (418) "Application run out of memory",)


Any Ideas

 

[cyberchef]

I am getting an 8602 error as well. Mine relates to failing to read from individual mailboxes though- "DBNAME=Individual Mailboxes\%username%\"
The backup stalls over these mailboxes and I end up stopping the job and resetting it. I have tried excluding the boxes from the backup as a test but it still pulled the error..Any thoughts?

 

[Shad007]

Cyberchef, go through the restore process on the cancelled job, it should tell you roughly where the individual mailboxes stopped/hung...then open up the user(s) mailboxes and have a look, I guarantee you you'll find someone with an email that has been used as a catalyst for multiple emails (ie the user has dragged other emails and inserted them as objects into the email)...find the culprit email and 'KILL IT'.

p.s eripley...I'm assuming you're using an e2k agent for your backup?

 

[ottm]

I also have the problem of job hanging when trying to read some mailboxes. But is there no other way of solving this problem than manually removing the culprit mails?
This occours almost daily here, without any consistency in which mailboxes is affected, so it would be impossible to check EVERY mailbox on the server before EVERY job, as there are quite a lot of them.

The general prosess is:
Job works fine until it reaches exchange.
Then it spends several hours trying to read some mailboxes, eventually returning "Failed to read from DB" and "Application run out of memory", indicating some mailboxes (no constistency which).

Could there be some other reason for this happening?

Magnus

 

[Stacy12]

We had a similar error a few months ago. We actually found that it was corruption on the exchange side and the exc. box was complely redone. That was our last resort.There were also a few helpful items that people gave such as permissisions being entered with the domain name/username, ensure that the virus services are not interefering with any of the services, delete the job and reenter the job.