Home > IT Answers > Exchange > Exchange 2003 problems on DC
Amcdowell
0 pts.
 Exchange 2003 problems on DC
Exchange, Exchange 2003, Windows Server 2003
I have a windows 2003 standard server running as a DC and I also have Exchange 2003 installed on this. It is giving me all kinds of problems. I am getting errors with the ExchangeSA and ExchangeSA. It seems to work intermittenly. Outlook users sometimes can sync with Exchange and add appointments other times not. I know it is not reccomended to have Exchange on a DC, but I found that out after the fact. I also have a 2003 Enterprise Server running Terminal Server and I was wondering if I can install Exchange on this with out issues. Or do I need another friggin 2003 server. Specifically the errors I recieve are: MSExchangeIS ID: 9646 MSExchangeSA ID: 1031 and sometimes others Can anyone help guide me in the right direction?

Software/Hardware used:
ASKED: May 20, 2005  3:32 PM
UPDATED: May 23, 2005  12:32 PM
RELATED QUESTIONS
Answer Wiki:
I have Exchange 2003 running on Windows Server 2003 domain controller, and formerly on a Windows 2000 domain controller. It works fine although not "best practice". Look elsewhere for the cause of your problem. I cannot suggest anything since you don't describe it in any detail.
Last Wiki Answer Submitted:  May 21, 2005  12:59 pm  by  Dweston   0 pts.
All Answer Wiki Contributors:  Dweston   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

clients are only sometimes able to connect. A restart temporarily solves this. After awhile the clients get disconnected. It seems to be intermitten. Sometimes a restart will last a week sometimes only an hour.

Amcdowell
 0 pts.
 

clients are only sometimes able to connect. A restart temporarily solves this. After awhile the clients get disconnected. It seems to be intermitten. Sometimes a restart will last a week sometimes only an hour.

Amcdowell
 0 pts.
 

There are several problems that I recall related to these errors. However, I believe that many of them were fixed in Exchange 2003 Service Pack 1. Are you up to date on your Windows 2003 and Exchange service packs?

Also, do you have message tracking turned on? You may want to try turning it off temporarily to see if the problem goes away. Although you have only provided the Error numbers, I recall and confirmed in MS White papers that the 1031 is often related to issues with message tracking or an inability to create proper shares:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842203

Paul

PaulHinsberg
 0 pts.
 

Check-out the following MS Knowledge Base article: 830829

Your Exchange Server 2003 computer may stop responding after a MAPI client opens more than the default value of certain server objects

WayneT123
 0 pts.