Problem solve Get help with specific problems with your technologies, process and projects.

Solutions to common Exchange problems

Two common problems with Exchange server and how to solve them.

 

Solutions to common Exchange problems
Adesh Rampat

Sometimes it's the more common problems that cause us the most difficulty. And while a problem may be a common one, if you haven't seen it before, then it's not a simple thing. This tip tells how to deal with two common Exchange problems you are likely to encounter at some point.


Name Server Data Inconsistency

When sending Internet mail to another server the sender of the e-mail may get an error message that says "name server data inconsistency" after a certain period of time. Usually this happens with one particular server. The problem here, in most cases, is that the remote server is not specified in the DNS name listing of the firewall in use. If the name server were added in the DNS name listing, it would resolve the problem.

Another issue could be that the ISP for the domain the sender's e-mail was trying to contact had time to live set (TTL) too short. Therefore, there is a possibility that the mail message would expire before it had a chance to process. You can't solve this problem; the sender needs to resend.

Exchange 5.5 Services Won't Start

Sometimes after a premature shut down of the Exchange server, some of the major services may fail to start. A straightforward approach in getting the services to start is just to double-click on the particular service. Once the startup screen appears, retype the Exchange service account password (you must know the password when retyping), then try to start the service (ensure that the service is set to automatic before starting). If the service does not start (the information store might be a good candidate for this), then go to the command prompt and type isinteg -patch (the isinteg command is located in c:srvappsexchsrvrbin). This should successfully resolve any errors in the information store database. Exit from the command prompt and then start the information store service.


Adesh Rampat has 10 years experience with network and IT administration. He is a member of the Association of Internet Professionals, the Institute for Network Professionals and the International Webmasters Association. He has also lectured extensively on a variety of topics.


This was last published in November 2001

Dig Deeper on Microsoft messaging and collaboration services

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchServerVirtualization

SearchCloudComputing

SearchSQLServer

SearchEnterpriseDesktop

SearchVirtualDesktop

Close