RE: MSExchangeDSAccess 2115 Warning message
Hi Greg,
Thank you for posting here!
I notice that you have posted the same question in another newsgroup, to
which I have already responded. Please check my answer there, and if you
need any further assistance on this particular issue please reply to me in
that thread so I can follow up with you. In the future, please don't
cross-post the same question in multiple newsgroups. This will help our
engineers work on your question more efficiently. Your understanding and
cooperation is appreciated.
For your convenience, I have included my reply as follows:
------------------
Hi Greg,
Thanks for the input.
First of all, please verify if there are other DSAccess related events
logged and if the event only appears when you turn on the Diagnostic
Logging on the MSExchangeDSAccess. If so, we can safely ignore it as the
Exchange server is properly working.
Otherwise, if there are other MSExchangeDSAccess events logged without
diagnostic logging, there are problems on MSExchangeDSAccess. We can try
the following steps to troubleshoot it:
Step 1: 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 Wiindows 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
Step 2: 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.
Step 3. Checking if there are static configurations.
==================================
Starting the Microsoft System Attendant will initialize DSAccess and start
the topology detection. DSAccess checks registry keys for any static
configuration, it checks the profiles\default key and its subkeys for the
operational paramateres and list of DCs and GCs and then the
MSExchangeDSAccess\Instance0 key for the configDC
More information is here:
246228 XGEN: DSAccess Profiles
http://support.microsoft.com/?id=246228
In the meanwhile, please collect the following information for further
investigation:
1. Run netdiag and dcdiag on the Exchange server when the issue appears.
a. Run "netdiag /v > netdiag.log". Send me the copy of the output at:
v-asun@microsoft.com.
b. Run "dcdiag /v > dcdiag.log". Send me a copy as well.
For more information about these two utilities, please refer to the
following article in our knowledge base:
265706.KB.EN-US DCDiag and NetDiag in Windows 2000 Facilitate Domain Join
and DC Creation
http://support.microsoft.com/default.aspx?scid=KB;EN-US;265706
2. Send me the application log.
Thanks and have a nice day!
Best Regards,
Alan Sun
Microsoft Online Partner Support
------------------
Thank you and have a nice day!
Best Regards,
Alan Sun
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=%2finternational.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
date: Fri, 21 Oct 2005 03:29:13 GMT
author: (Alan Sun [MSFT])
