• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 427
  • Last Modified:

IMAP4 services on Exchange 2003

Every once and awhile I have a red X on my deafuly IMAP4 server within Exchange manager, however, the service is running.  I want to be notified when this is occuring.  What event ID is placed into the application log when a red X is or the default IMAP4 server is stopped???
0
gopher_49
Asked:
gopher_49
  • 4
  • 3
1 Solution
 
aa230002Commented:
Which Version of Exchange server is this?
By default, IMAP4 virtual server is disabled by default, Please check the following link to enable IMAP4
--->
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3ClientAccGuide/1d640734-7297-4e11-b4a3-cee794efa1fe.mspx?mfr=true

Thanks,
Amit Aggarwal.
0
 
gopher_49Author Commented:
I'm running Exchange 2003.  I've set the IMAP4 service to automatic.  I'm currently monitoring the service to assure it's started, however, even if the service is started sometimes the red X is on the IMAP default server within Exchange manager.  When the Red X is present I have to right click on it and start it.  I would like to know the event log that occurs so I can have my monitoring software watch for the event log to notify me.
0
 
aa230002Commented:
What service pack is applied on Exchange 2003?
Do you have stand alone server or Exchange cluster?
Do you have Front-end / Back-end configuration?

When you see a red X on default virtual server (IMAP4) and do a right click and start, do you see any event ID in Application log saying that IMAP4 server is started successfully?
IMAP4 runs under inetinfo.exe and i am not sure if it logs a separate event when it starts or fails.
Try searching your Application logs for the key word "IMAP4"

Thanks,
Amit Aggarwal.
0
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

 
gopher_49Author Commented:
I'm running sp2.  It's a domain controller/Exchange server.  It's also in a front-end/back-end configuration.  I've noted the event log that's posted when I start the IMAP4 server.  Should I just monitor that particular event ID?  
0
 
aa230002Commented:
Check the description of the Event Id that you noted when you started the IMAP4 server. There should be a key word you would be interested into, like the name of your IMAP4 virtual server or some thing unique about this IMAP4 virtual server. Now, search the same key word in your application logs. Right click - Application log - view - find and put this key word in the description field.
You should see all the events and half of them should belong to starting the IMAP4 virtual server and other half should belong to stopping the IMAP4 virtual server and then, you can find the event ID related and monitor them.

Thanks,
Amit Aggarwal.
0
 
gopher_49Author Commented:
The application log has been flushed.  This Friday I'll be bringing the server down to install a new battery system.  I believe the issue is occuring during the boot process.  The service starts, however, the actual IMAP4 server does not.  I'll search the application log for the keyword so I can then know the exact log to look for.

I"ll let you know something Friday afternoon.
0
 
gopher_49Author Commented:
When I rebooted the server Friday the IMAP default server started properly.  I was unable to see the event log that's posted when it does not start properly.  The next time the default IMAP server does not strat I'll search the application log for the 'default IMAP servername' keyword.  I'll place that into my monitoring system to notify me when an event ID with the specific keywords are found, or, the source and ID number matches the specific event id.  This will accurately notify me when the IMAP default server does not start.  

thanks.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now