Re: Exchange Won't Start Automatically Upon Reboot
- From: v-chacez@xxxxxxxxxxxxx (chace zhang)
- Date: Thu, 24 Aug 2006 06:14:47 GMT
Hi Ted,
Thank you for posting here. I appreciate jesmin's input, you can try the
steps that deviled by him.
From your post, I understand your Exchange server can not start afterReboot, and you encountered Event 2114 error.
First, I would like to suggest that you monitor your Exchange Server after
reboot, are there any exchange related services not started? Or just
Information Store dismounted.
Based on my research, This issue seems related to the DSAccess of
Exchange. MSExchangeDSAccess is the core component of Exchange, which
detects the AD topology. DSAccess related issue is usually complex and time
consuming, as it has multiple causes, such as AD problems, network problems
or Exchange misconfiguration. Hence, we need to spend much time on
troubleshooting so as to get the root cause. Your understanding is
appreciated.
Let's perform following steps to narrow down this issue.
I. This error occurs if the following registry values are not present
under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<EXCHANGE
SERVER>\Private-<Guid-of-private-mdb>
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<EXCHANGE
SERVER>\Public-<Guid-of-private-mdb>
Where <EXCHANGE SERVER> is the name of your Exchange server and
'Private-<Guid-of-private-mdb>' is the GUID of your private store. For
example:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VPC-SBS2K3
\Private-dc3f8acc-d0e3-48c7-8b45-6551e532d94c
Under both the public and private keys, add the following two values (total
of 4 values):
Name: Gateway In Threads
Type: Reg_Dword
Value: 0
Name: Gateway Out Threads
Type: Reg_Dword
Value: 0
Restart the Exchange services.
II. Disable antivirus applications
==========================
The problem may be caused by the Anti-virus software on the server. I
suggest you temporarily disable the antivirus software on the server, and
test if the problem occurs.
In addition, the following Microsoft Knowledge Base article is for your
reference.
Overview of Exchange Server 2003 and Antivirus Software
http://support.microsoft.com/?id=823166
III. Verify DSN setting on Exchange
==============================
On the Exchange 2003 server, run "ipconfig /all" command at the command
prompt. Verify that DNS server is correct.
IV. Checking Service Principal Names (SPN) for LDAP
============================================
1. Download the Setspn utility, visit the following Microsoft Web site:
http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/setspn-o
asp
Note: The Setspn Utility is applied to both Windows 2000 and Windows 2003.
2. Run setspn utility to list the registered Services Principal Names on
Exchange Virtual Server:
setspn -l <Exchange Virtual Server name>
3. Verity if you can see entries about Service Principal Names (SPN) for
LDAP? If no, please continue with the following steps to register them
manually:
setspn -a ldap/<Exchange Virtual Server name> <Exchange Virtual Server
name> setspn -a ldap/<Exchange Virtual Server name>.xxxxxx.local <Exchange
Virtual Server name>
The format is much similar to the entries below which you can see by setspn
-l <Exchange Virtual Server name> command.
exchangeMDB/<Exchange Virtual Server name> exchangeMDB/<Exchange Virtual
Server name>.xxxxxx.local
For instance:
run setspn utility to list the registered Services Principal Names on
Exchange Server (MAIL):
setspn -l MAIL
Registered ServicePrincipalNames for
CN=MAIL,CN=Computers,DC=xxxxxx,DC=local:
exchangeRFR/MAIL
exchangeRFR/MAIL.xxxxxx.local
exchangeMDB/MAIL
exchangeMDB/MAIL.xxxxxx.local
MSClusterVirtualServer/MAIL.xxxxxx.local
MSClusterVirtualServer/MAIL
HOST/MAIL.xxxxxx.local
HOST/MAIL
As you can see... there are no principal name for ldap. So registered them
manually:
setspn -a ldap/MAIL MAIL
setspn -a ldap/MAIL.xxxxxx.local MAIL
V. Verifying DSAccess detection setting.
===================================
1. Start ESM.
2. Navigate to the Exchange 2003 server object, and open its Properties.
3. On the Directory Access tab, check if all the DCs/GCs are listed
properly. Make sure the option "Automatically discover servers" is checked.
VI. Did you install the SBS 2003 SP1 and Exchange 2003 SP2? If not, please
refer to the following information to install them, and then check if the
issue persists.
Microsoft Windows Small Business Server 2003 Service Pack 1 (SP1)
http://www.microsoft.com/downloads/details.aspx?FamilyId=B6F8A4C0-B707-4161-
ADEB-44F1B756119F&displaylang=en
Exchange Server 2003 Service Pack 2
http://www.microsoft.com/downloads/details.aspx?FamilyId=535BEF85-3096-45F8-
AA43-60F1F58B3C40&displaylang=en
Hope this helps, if you have any other concerns or need more help on this
issue, please feel free to let me know.
Have a nice day!
Best Regards,
Chace Zhang (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "jesmin ningthoujam" <jesmin.ningthoujam@xxxxxxxxx>
| References: <1C5D4A66-3387-487F-B852-D8AA061A6F15@xxxxxxxxxxxxx>
| Subject: Re: Exchange Won't Start Automatically Upon Reboot
| Date: Thu, 24 Aug 2006 04:36:04 +0530
| Lines: 204
| MIME-Version: 1.0
| Content-Type: multipart/alternative;
| boundary="----=_NextPart_000_0152_01C6C736.CF0069B0"
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.3790.2663
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757
| Message-ID: <eKoRikwxGHA.3632@xxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: spectra-smart-10-d.spectranet.com 203.122.39.10
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:292425
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Are these the Errors and Event Id's ??
|
****************************************************************************
*************
| Event ID : 2114
| Event Category : Topology
| Event Source : MSExchangeDSAccess
| Event Type : Error
| Computer : Server_Name
| Description : Process (Process_Name) (Process_ID). Topology Discovery
failed, error 0x80040a02.
| For more information, click
http://search.support.microsoft.com/search/?adv=1.
| Additionally, you may find that the following warning events were logged
in the Application log earlier:
| Event ID : 2112
| Event Category : Topology
| Event Source : MSExchangeDSAccess
| Event Type : Warning
| Computer : Server_Name
| Description : Process (Process_Name) (Process_ID). Exchange Server
Server_Name.Domain_Name.Root_Domain does not have Audit Security Privilege
on Domain Controller Server_Name.Domain_Name.Root_Domain. This Domain
Controller will not be used by DSAccess.
| For more information, click
http://search.support.microsoft.com/search/?adv=1.
|
****************************************************************************
***************
| You might want to take a look at the following Articles :
| Exchange services do not start, and event IDs 2114 and 2112 are logged in
the Application log in Exchange Server 2003 or in Exchange 2000 Server
| http://support.microsoft.com/?kbid=919089
| Also refer :
| - Error code: 0x80040a02 - This problem can occur because the Exchange
security groups do no have the appropriate user rights to enable the
Directory Service Access (DSAccess) component to communicate with Active
Directory.
|
http://eventid.net/display.asp?eventid=2114&eventno=2458&source=MSExchangeDS
Access&phase=1
| If this is not the correct Source, would appreciate if you could be a
little more specific with the Event ID and the source !!
| --
| jesmin ningthoujam
| "Ted" <Ted@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C5D4A66-3387-487F-B852-D8AA061A6F15@xxxxxxxxxxxxxxxx
| I have one SBS client who has had to manually start Exchange services
upon
| reboot for some time now (unfortunately, I don't know for how long,
which
| exact service, etc). I do know it's been going on since at least
April, by
| looking at the last entry in the App logs. I looked in the logs,
around the
| time of reboot, and found this:
| Process INETINFO.EXE (PID=1512). Topology Discovery failed, error
0x80040952.
| Event ID is 2114. You see this a handful of times. But when goes to
start
| the services, they all start fine. Not entirely sure what is going on
there.
| Anyone else run in to this?
| Thanks in advance!
|
.
- References:
- Re: Exchange Won't Start Automatically Upon Reboot
- From: jesmin ningthoujam
- Re: Exchange Won't Start Automatically Upon Reboot
- Prev by Date: Re: SBS in alreay existing Active directory
- Next by Date: RE: Fax monitor incoming + outgoing calls?
- Previous by thread: Re: Exchange Won't Start Automatically Upon Reboot
- Next by thread: Sharepoint and SQL?
- Index(es):
Relevant Pages
|
