Discussion Locked

Exchange 5.5 Store.exe app. error.

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

For the past few days now we have been receiving a Dr. Watson: Application error in store.exe - access violation (0xC0000005) .... on our Exchange 5.5 Service Pack 4 server. After some searching, we discovered that the error occurs when the IS maintenance procedures begin.

I took down the server and made a copy of the database files (pub.edb, priv.edb, dir.edb) and their respective logs. I began running the eseutil.exe utility with the /g switch to check for consistency. The pub and dirdatabases checked out ok, but the priv database generated another Dr. Watson. I tried the /d switch to defrag, as well as the /p switch to repair. Another Dr. Watson (same application error, access violation). I'll note here that the utility has been run on two different boxes, and the same errors arise.

When looking at the Dr. Watson log file, the faults appear in exactly the same place in the function "jetsetcolumns" at a particular "move" call.

Anyone have any ideas? The server itself seems to be processing mail just fine; however, I'd like to get this error resolved, and I'm worried that this problem might lead to an even larger one.

Thanks in advance.

Jim Likovic

3 replies

by jimapp

Have you checked the service accts? When you installed Exchange there is a system acct created. Is this the acct being used? Administrator acct "no,no"May be a permissions thing. Hope this helps. I had a similar experience some time ago and thats where I went wrong

by jlikovic

I'm not sure exactly what "permissions thing" you are talking about. Permissions on the actual priv.edb database?

This mailserver has been running for about a year and a half now. No new users have been added for approximately 6 months.

Also, let me reiterate that when running the eseutil.exe on another machine against the priv.edb database (copied to that particular machine), a dr. watson arises with an access violation, and the same fault is indicated in the dr. watson log in the function "jetsetcolumns." I'm wondering if there is a particular area of the database that is corrupt.

Thanks for the prompt reply.

This discussion is closed to new replies.