Thanks for your response back Here are some event log entries that may be of interest
There are a bunch of these. Although they may be more frequent, they aren't new. It's been happening for years. They are always in the early AM - perhaps backup related? Source: ESE Category: General Event ID: 101 Description: ESEUTIL (6048) The database engine stopped. Source: ESE Category: General Event ID: 100 Description: ESEUTIL (5372) The database engine 6.05.7638.0002 started. These have occurred in the past but not frequently. He uses an iPhone. I suppose it could have something to do with it. My concern is that these might be generated if the IS is corrupted and looses the time of an appointment? Source: EXCDO Category: General EventID: 8206 Description: Calendaring agent failed with error code 0x80040229 while saving appointment. Source: EXCDO Category: General EventID: 8239 Description: An appointment with the subject "Working Group Mtg." was saved to mailbox myu...@ucdavis.edu. The start time is missing, so the calendaring agent cannot publish the free/busy information for this appointment. To correct this, please delete the appointment and recreate it. Source: EXCDO Category: General EventID: 8241 Description: An existing appointment with the subject "Working Group Mtg." in mailbox myu...@ucdavis.edu was modified. The start time, or both the duration and end time of the existing appointment were missing. Other than that, there isn't anything out of the ordinary in the logs - certainly nothing really scary like your "Your IS is corrupt" or even "an IS error was detected and resolved." Curt From: Todd Lemmiksoo [mailto:tlemmik...@gmail.com] Sent: Sunday, June 12, 2011 8:15 AM To: MS-Exchange Admin Issues Subject: Re: Exchange 2003 Crisis before trying to do anything ...is the store still mounded, look in event log for Information store messages. Then post back On Sun, Jun 12, 2011 at 1:13 AM, Jim Dandy <jda...@asmail.ucdavis.edu> wrote: Thursday morning I came to work and my exchange server was not receiving mail. The antivirus engine had stopped and after that the event log registered thousands of entries that the Ninja VSAPI had refused Microsoft Exchange InfoStore request to scan a message because the Ninja Store Scanner is down. (I'm using Vipre E-mail Security for antivirus/antispam). No other unusual entries were found in the event log. I rebooted the server and it took a really long time to shut down. When it came back up the Ninja Store scanner service was not started but I was able to start it manually. Without going into a lot more detail I'll just say the info store wasn't working right. Subsequent attempts to stop the IS service failed. I disabled Vipre, rebooted again and everything resumed normal function (except no antivirus/antispam). I updated Vipre and reenabled its services. The following morning the server had crashed in the same way. When it crashes messages are not delivered to inboxes and the sender does not get an NDR. Since then I've had a user claim that he tried to move some messages from one folder to another and they disappeared. Later he told me that he had an important message in his inbox and when he tried to open it, it disappeared. So, the questions I have are 1) Could a corrupt info store cause the av scanner to fail like this? If so, how can I check for/repair the store? 2) Does this guy's claims seem possible that messages are just disappearing? Details Exchange Server 2003 with both front and backend servers. Vipre E-mail security latest version. Thanks for your help. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist -- T. Todd Lemmiksoo --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist