Networks

Ask something
Question Locked

Exchange Services not starting

0 helpful
10 replies

by chcomputers

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Windows Server 2003 Exchange server, and when it boots, the Microsoft Exchange Information Store service does not start, so outlook will not open on the workstations. I have checked the properties for the service and it is set to automatic. Have rebooted four times, and it never starts. You have to go in and start it manually each time the server boots up. Any help would be greatly appreciated.

10 replies

by bart777

If the service is failing to start you should see an entry in the event log that will point you to the reason that it's failing.

Let us know what you find there and we'll give you a hand.

by chcomputers

The logs mentioned that the exchange server was low on virtual memory and referred me to this six page document from Microsoft.

http://support.microsoft.com/?kbid=815372

We just upgraded the memory in the server from 2 Gb to 4 Gb. So I think this document is definitely the fix for the problem. The only other issue, (and I didnt set this up, I'm just trying to clean it up) is that active directory and DNS are on the same server as exchange. No it is not integrated like in Small Business Server. The previous Administrator installed it that way!

In this document it says how to fix the problem unless the server contains AD and DNS. So I'm not sure what to do. It really seems to be a mess but were trying to get 1 more year out of these servers and then we will be replacing them will all new equipment! Let me know what you think.

by bart777

Let's take a smaller step.

If you upgraded the RAM did you also increase the size of teh swap file?

Verify that the virtual memory is set to somewhere between 4-6GB. Then try to start the services again. My geuss is that the virtual memory settings are currently set to some smaller amount like maybe 2-3gb.

Let me know what you find.

by dumphrey

Exchange server analyzer tool from MS?

Also, on technet article
http://technet.microsoft.com/en-us/library/aa996184(EXCHG.65).aspx

the intersting part,

"/3GB Boot.ini Switch

If your Exchange Server 2003 server has 1 GB or more of memory installed, and if the computer stores mailboxes or public folders, make sure that you add the /3GB switch to the Boot.ini file on the server. By default, the Windows Server 2003 and Windows 2000 Advanced Server operating systems reserve 2 GB of virtual address space for system usage and another 2 GB for the user address space. Each process is allocated this range of virtual addresses at startup. Typically, the actual memory usage (the working set) of a process is much less than the address space allocated to that process. On a computer that is running Exchange Server 2003 with 1 GB or more of memory, you should modify the Windows Server 2003 and Windows 2000 Advanced Server operating systems so that 3 GB of user address space is available to each process. You can do this by using the /3GB switch in the Boot.ini file."

I would bet this fixes the problem.

by daryl.thomas

Hi,

Is it the services which are not started or the mail store? If your services are started and your mail store is not mounted then check the size of your db and ensure it is less than 18GB, if it is more you will need to make a registry edit to increase the threshold.

Check your event viewer for logs which give an error along the lines of your database size is too large blah exchange will regularly unmount. I don't have the exact event ID but when I get back to work this morning I will follow up with specifics.

by chcomputers

The services them selves are not starting. As soon as you start the service the mail server works. Please read the update "After Checking the Log Files"

by Former member

This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.

The Microsoft? Exchange Server Analyzer Tool queries the Win32_Service Microsoft Windows? Management Instrumentation (WMI) class to determine the values set for the Started key of the Microsoft Exchange Information Store and the Simple Message Transfer Protocol (SMTP) services. A value of False indicates that the service is not running. A value of True indicates that the service is running.

The Exchange Server Analyzer also examines the Exchange_Server WMI class in the root\MicrosoftExchangeV2 namespace to determine the value of the IsFrontEndServer key. A value of False indicates that the Exchange Server computer is not a front-end server. A value of True indicates that the Exchange Server computer is a front-end server.

If the Exchange Server Analyzer finds the value of Started for the SMTP service is true, the value of Started for the Microsoft Exchange Information Store service is False, and the value for IsFrontEndServer to be True, a warning is displayed.

Exchange 2000 Server and Exchange Server 2003 use front-end servers to proxy POP3, IMAP4, and Microsoft Office Outlook? Web Access client requests. Additionally, they can be used as Internet-facing SMTP servers. If this front-end server accepts and routes SMTP messages, supports IMAP clients (which use SMTP for submitting messages), or if this front-end server is running Virus Scan API (VSAPI)-compliant software, the Microsoft Exchange Information Store service must be running. Otherwise, the front-end server will not be able to process SMTP messages, or scan messages using VSAPI.

Unless SMTP or VSAPI-compliant antivirus software is being used on a front-end server, the recommended configuration is to disconnect and delete all public folder stores on the front-end server, stop the Microsoft Exchange Information Store service, and then set the Microsoft Exchange Information Store service to disabled. In addition, the SMTP service should be stopped if it is not being used. On Exchange Server computers that use SMTP or VSAPI-compliant software, the Microsoft Exchange Information Store service must be running to deliver messages and service messaging clients.
To correct this warning

1. Open the Services MMC snap-in.

2. Right-click Microsoft Exchange Information Store service, and then click Properties.

3. On the General tab of the Microsoft Exchange Information Store property page, make sure that the Start-up type is set to Automatic. If it is not, set it to Automatic, click Apply, and then click OK.

4. Right-click Microsoft Exchange Information Store service, and then click Start.

5. Close the Services snap-in.

If attempts to start the Microsoft Exchange Information Store service fail, it could indicate a more serious problem on this Exchange Server computer. In this case, you should examine the event logs for details about the failure. You should also ensure that you are running the most recent service pack for your version of Exchange Server. You can obtain the latest service pack for Exchange Server at the Web site, "Microsoft Exchange Server home page" (http://go.microsoft.com/fwlink/?LinkId=21573).
http://technet.microsoft.com/en-us/library/aa996705(EXCHG.80).aspx
Is this information helpful to you?.

Please post back if you have any more problems or questions.

by chcomputers

Its currently managed by the system and the max is like 7 Gb

by bart777

Does it give you a more specific error?

Try hard coding the virtual memory to 4-6 GB at least as well to see if that helps.

If you don't get an error or the memory change doesn't solve it then you could try that article.

This discussion is closed to new replies.