Exchange Server Forums

Exchange System Manager

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Information Stores >> Exchange System Manager

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Exchange System Manager - 30.May2007 9:24:16 AM

Akhoshbin

Posts: 37
Joined: 13.Jun.2001
Status: offline

hi all

we are using exchange 2000 in our system.users use Outlook 2003 to fetch emails via pop3 from servers ,now some users get into trouble that they receive 2 to 3 same email from server & then their system hangs ,we have to delete emails from M drive of server & after a while they can get rest of emails.
My question : when i delete the email directly from M drive of user's mailbox & it shows that 5 email resist in mailbox & i go back to Exchange system manager i see that it's showing 6 emails .when i go & come back after 3 to 4 hours in Exchange System Manager it shows 5 emails .i wanted to know that how i can speed up this process ?

Many thanks in advance

Post #: 1

Featured Links*

RE: Exchange System Manager - 31.May2007 2:41:33 PM

jassyca

Posts: 227
Joined: 20.Jul.2006
Status: online

um... deleting messages directly from the M: drive is the Exchange equivalent of juggling knives that don't have handles: If you keep doing it, your luck will run out some day and you will end up getting hurt. The M: drive is only really there to let you see what's going on if you *really* need to. You do NOT want to directly delete or change anything in that drive.

If you need to delete a message in someone's mailbox that seems to be causing problems, use Outlook (but not configured for POP3) to open the other person's mailbox and delete the message.

Sorry if I sound overly harsh but I want to be sure that you understand that you could cause yourself some serious problems if you make changes directly to the M drive.

(in reply to Akhoshbin)

Post #: 2

RE: Exchange System Manager - 2.Jun.2007 3:26:04 AM

Akhoshbin

Posts: 37
Joined: 13.Jun.2001
Status: offline

hello
thanks for your comment .i wanted to know that if in your organization users have problems in getting emails via POP3 in Outlook2003 ; ,i mean that they receive an email several times & then system hangs ?

thanks again for your useful comment .

(in reply to jassyca)

Post #: 3

RE: Exchange System Manager - 2.Jun.2007 2:04:38 PM

jassyca

Posts: 227
Joined: 20.Jul.2006
Status: online

We're not using POP3. No, my users only get a message once. But I have seen Outlook hang at times. Although, usually not while Outlook is receiving a message. As for why, in our situation, Outlook hangs? My theory is: it seems to happen most often to users who are using their calendar to pop up an alert (you know, "big meeting in 15 minutes" where you can either tell it to dismiss the alert or 'sleep' and tell you again in a little while). I think the alert window pops up behind Outlook where the users cannot click on it and that's why Outlook "freezes": it's waiting for the user to click the alert which is hiding. But that's my situation, not what you're seeing.

Issues caused by a backup or scan of the Exchange 2000 M: drive
http://support.microsoft.com/kb/298924/en-us
(Take note that the article specifically mentions these issues can even be caused by a backup. A backup doesn't delete anything.. it's just copying files. Yet here's Microsoft telling you that directly taking a backup of the M: drive could cause corruption.)

Moving Items within Drive M of Exchange can remove item properties
http://support.microsoft.com/kb/281673/en-us
(More problems if you mess around with messages in the M: drive.. blah blah blah)

Okay, enough of that. Let's concentrate on fixing the problem. You might want to check your Exchange databases with ESEUtil.

Exchange 2000 Server ESEUtil Command Line Switches
http://support.microsoft.com/kb/317014/en-us

Use the /G option ("integrity" check) which will just look at the database and tell you if it finds any problems but it won't try to fix them. Make sure, before you run it, that you have a recent backup of your Exchange server. It will need to take your databases offline so that means users won't be able to receive or send email until ESEUtil finishes. So you probably want to run it after working hours. Also, running ESEUtil with the /G option will be a lot quicker than if you use the /P (Repair) option.

Good luck. Let us know how it goes.

(in reply to Akhoshbin)

Post #: 4