Pages

Search

Server 2000 hang at shutdown due to "Microsoft Exchange Information Store" Service - Microsoft Exchange

Server 2000 hang at shutdown due to "Microsoft Exchange Information Store" Service - Microsoft Exchange

Server 2000 hang at shutdown due to "Microsoft Exchange Information Store" Service

Posted: 24 Sep 2004 01:51 PM PDT

MarkL wrote: 

Is the server also a domain controller? I believe its a known issue if so.

I'd create a batch file on the desktop to shut down the exchange services in
a timely manner and get into the habit of running it before a shutdown.

How do you regulate your Exchange domain?

Posted: 24 Sep 2004 08:21 AM PDT

I like what Mark says. Technically, he is correct in what to do first.
However, politically, I disagree on what to do first.

You don't want to come in and make enemies. Trust me on that.

The first thing that I would do is discuss, with your management, the option
of cutting down SPAM first. The users will be happy about that. Once the
user environment is happy...

Propose to them two options (note: I don't know the specifics of your
organization, so this is generic):

Option 1) Propose a purchase of a new server with plenty of disk. Note
that a rule of thumb that I use is ~150 people per spindle, dependent upon
utilization...more folks if I am using Outlook 2003 Cached Exchange Mode. I
generally use Windows 2000/2003 standard server and Exchange Server
2000/2003 Enterprise edition. Clustered environments are different.

Option 2) In lieu of this, propose moving some of the largest user's
information to .pst files and implement quotas. Remind management that the
loss of the user's local system could result in the loss of the .pst file if
it is stored on the system. Note that the upper limit of .pst files may be
1.85GB of 2.00GB on older versions (pre-2003) of Outlook.

That way you are leaving it up to management to make the decision on what to
do and you do not seem like the bad guy...and you are providing risk
mitigation information. They will talk to the managers and users, most
likely.

Stories:
I had a very large client in Georgia that would rather purchase more SAN
space than implement quotas for their users. We got a few new servers and a
nice beefy SAN.

On the flipside, I had a client in Virginia that did not want to purchase a
new server or software. They opted to implement quotas and their
management sent an e-mail regarding this. Obviously, there were exceptions
to the rule.

Either way, it was management's decision and I did not seem like the bad
guy.

Bob

"Andrew" <microsoft.com> wrote in message
news:com... 
mess. 
anything. 
your 

second mailbox or public folder

Posted: 24 Sep 2004 07:12 AM PDT

Take a look at http://www.ivasoft.biz/unisent.shtml


 
sent 
the 
managers 
sending 
to 
in 
for 

Exchange 2003 New Install

Posted: 23 Sep 2004 04:33 PM PDT

Outside email,....

ISP email set up hahahah
 
staff 
support 

SMTP Service

Posted: 23 Sep 2004 12:45 PM PDT



"Rodrigo" wrote:
 

Exchange Priv Info Store - Gooone

Posted: 23 Sep 2004 09:10 AM PDT

Thanks Mark.

I was able to point to a new location for the database, but unable to mount
(or force creation of new database).

An Internal Processing Error has occured (ID: c1041724)

I searched some MS KB's - the permissions are ok on the new database
location and there is plenty of disk space.

This msg:
Event 9175: The MAPI Call 'OpenMsgStore' Failed with the Following Error

Is registered in the application event log.

The information store is running and so is system attendant.

Where to from here?

note: I do have a back in which I will restore later.


"Mark Arnold [MVP]" <org> wrote in message
news:com... 

Messages marked as opened and read

Posted: 22 Sep 2004 08:44 AM PDT

 

I'm aware of this setting. I confirmed that it's not enabled.
 

The user can work in offline mode and the message will not open. The minute
he connects to the Exchange server, it will change to show as opened and
read.
We've also tested this by using Outlook WebAccess. The same thing will
occur. Also, regardless of which computer he uses to connect to Exchange,
the same issue occurs so I know that it's not computer specific.