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 dow
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 wrote:
> Thursday morning I came to work and my exchange server was not receiving
> mail. The antivirus engine had stopped and af
Looks like your AV is the reason
From: Todd Lemmiksoo [mailto:tlemmik...@gmail.com]
Sent: Sunday, June 12, 2011 8:15 PM
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
on it.
Greg Sweers
CEO
ACTS360.com<http://www.acts360.com/>
P.O. Box 1193
Brandon, FL 33509
813-657-0849 Office
813-758-6850 Cell
813-341-1270 Fax
From: Jim Dandy [mailto:jda...@asmail.ucdavis.edu]
Sent: Sunday, June 12, 2011 2:14 AM
To: MS-Exchange Admin Issues
Subject: Exchange 2003 Crisi
e 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
wrote:
Thursday morning I came to work and m
ly pretty good and things disappeared on him twice so that is why
I'm questioning the integrity of my IS.
Curt
From: gswe...@acts360.com [mailto:gswe...@acts360.com]
Sent: Sunday, June 12, 2011 11:22 AM
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2003 Crisis
Are you unbinding the
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 [
t: Re: Exchange 2003 Crisis
The 8000 messages are for a bad appointment in his calendar. He needs to
delete (remove) the appointment and re-enter it. It will cause more
problems the long it is in his calendar.
The ESE messages are informational, and appear then Exchange maintenance
runs.
On Mon, J
Curt
>
>
>
> *From:* Todd Lemmiksoo [mailto:tlemmik...@gmail.com]
> *Sent:* Monday, June 13, 2011 10:13 AM
> *To:* MS-Exchange Admin Issues
> *Subject:* Re: Exchange 2003 Crisis
>
>
>
> The 8000 messages are for a bad appointment in his calendar. He needs to
> de
t info store or can I just assume
>> since there aren’t any unusual messages in the logs that the info store is
>> OK?
>>
>>
>>
>> Curt
>>
>>
>>
>> *From:* Todd Lemmiksoo [mailto:tlemmik...@gmail.com]
>> *Sent:* Monday, June 13,
I wouldn't run any tool against a mounted store.
John W. Cook
Systems Administrator
Partnership for Strong Families
From: Sean Martin
To: MS-Exchange Admin Issues
Sent: Mon Jun 13 19:15:18 2011
Subject: Re: Exchange 2003 Crisis
Can you run eseutil /mh agai
2003 Crisis
I wouldn't run any tool against a mounted store.
John W. Cook
Systems Administrator
Partnership for Strong Families
From: Sean Martin
To: MS-Exchange Admin Issues
Sent: Mon Jun 13 19:15:18 2011
Subject: Re: Exchange 2003 Crisis
Can you run es
4:12 PM
To: MS-Exchange Admin Issues
Subject: Re: Exchange 2003 Crisis
To do any testing you would dismount the store and use eseutil.
On Mon, Jun 13, 2011 at 3:30 PM, Jim Dandy
wrote:
Is there a way to test for a corrupt info store or can I just assume
since there aren't any unusual messa
13 matches
Mail list logo
