RE: SBS 2003 - Exchange LDAP Error
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Tue, 28 Mar 2006 03:07:17 GMT
Hi David,
Thanks for your update. I appreciate your time.
How you demote the secondary DC from domain? Could you describe me more
detail information about your customer's network topology? Before you
physically retired the secondary DC from the network, have you run the
Dcpromo.exe program to remove this computer from the domain?
If a domain controller is physically removed and the Active Directory
Installation Wizard (Dcpromo.exe) is not run first to demote the domain
controller to a member server, the computer object still exists as a domain
controller in Active Directory. The previous computer object must be
removed from Active Directory.
For more detail information about how to manually remove the configuration
data for the domain controller from Active Directory, you can check the
following article:
216498 How to remove data in Active Directory after an unsuccessful domain
controller demotion
http://support.microsoft.com/kb/216498/
I am happy to be of assistance to you.
Have a nice day!
Sincerely,
Jenny Wu
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.
--------------------
Thread-Topic: SBS 2003 - Exchange LDAP Error<1#qj79VUGHA.4332@xxxxxxxxxxxxxxxxxxxxx>
thread-index: AcZRrm1s6HSZ3r6JQEeTBHHS1kCeCw==
X-WBNR-Posting-Host: 129.61.46.16
From: =?Utf-8?B?RGF2aWQgRGF2aXM=?= <DavidDavis@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <EC9C7BDD-F93C-4D04-9BCA-9E5E420A9FA1@xxxxxxxxxxxxx>
Subject: RE: SBS 2003 - Exchange LDAP Errorand
Date: Mon, 27 Mar 2006 06:55:02 -0800
Lines: 214
Message-ID: <01A0EBC2-D0CE-44CC-9D5E-C2C2A626C141@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:255909
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs
Thanks for replying. I am headed over to the customer site this afternoon
will work on getting you the requested information.and
This error started occuring after we demoted their secondary domain
controller. I thought that it may be related to a bug in AD but DCDIAG,
DCDIAG /test:dns and NETDIAG all run clean. I went through DNS manually
confirmed that there is no reference to the old DC. I also removed thesite
entry in sites and services that contained the site info where the otherDC
was located.perform
Due to the nature of the client's business, I have not been able to
a clean reboot. I will schedule some time this afternoon to complete thatthat
also.
--
David Davis [MCSE, CCNA, Security +]
""Jenny wu [MSFT]"" wrote:
Hi David,
Thanks for using the SBS newsgroup!
I am sorry for the delayed response due to weekend. Please understand
tothe newsgroups are staffed weekdays by Microsoft Support professionals
contactanswer your systems and applications questions. Your understanding is
greatly appreciated!
For time critical issues (not business down), we encourage you to
warningCSS directly for more immediate assistance:
International Support (non-US/Canada):
http://support.microsoft.com/common/international.aspx
US and Canada:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone
To continue working with me in the newsgroups, please see the following:
From your description, I understand the issue to be: you get many
letevent 2392 in Event Viewer. If I am off base, please don't hesitate to
someme know.
Before we go any further on the issue, please kindly help me collect
exchangeinformation to isolate the issue:
1. Please double check if the event ID is 2392. And also for your
toserver work well and it is Warning event, you can ignore them.
2. What you have changed on the SBS server box before the warning begins
box?appear? Have you installed any third party application on the server
thatPlease disable all third party application on the server box and then
perform a clean boot to see if the issue still persists:
A Clean Boot will allow us to isolate any device drivers or programs
duringare loading at startup that may be causing a conflict with other device
drivers or programs that are installed in your computer.
1) Run MSCONFIG.EXE.
2) In the Services tab, click "Hide All Microsoft Services" and click
"Disable All".
3) In the Startup tab, click "Disable All". Click OK. (This will
temporarily prevent third-party programs from running automatically
tostart-up.)
4) Restart the computer and check whether the problem still persists.
If the problem does not occur, it indicates that the problem is related
toolone application or service we have disabled. You can use the MSCONFIG
theagain to re-enable the disabled item one by one to find out the culprit.
3. If you would like to trouble shoot the issue, please help me collect
Iffollowing information:
A. What is your SBS 2003 server version? Have you applied SBS 2003 SP1?
correspondingnot, I suggest that you apply the SBS 2003 SP1 to see if it helps. Since
the SBS 2003 SP1 includes many hotfixes and updates to current SBS 2003
server. Please refer to the following article to apply the SBS 2003 SP1.
Installing Windows SBS 2003 with SP1, "Getting Started" at the Microsoft
Web site http://go.microsoft.com/fwlink/?LinkId=51143
B. Please a save a text copy of application and system log for analyze:
To save a text copy of Application /System log:
A. Open Event Viewer: Start -> All Programs -> Administrative Tools ->
Event Viewer.
B. Right-click on Application/System log and select "Save Log File As?".
I appreciate your time! I am happy to be of assistance to you and look
forward to your reply.
Have a nice day!
Sincerely,
Jenny Wu
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
manner.newsgroups so that they can be resolved in an efficient and timely
theYou 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
are"Notify me of replies" box to receive e-mail notifications when there
newsreader,any updates in your thread. When responding to posts via your
doingplease "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
Pleaseso, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly.
rights.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
<DavidDavis@xxxxxxxxxxxxxxxxxxxxxxxxx>
--------------------
Thread-Topic: SBS 2003 - Exchange LDAP Error
thread-index: AcZPG+WuStH6c3KaRzmmUT4aXA4LMw==
X-WBNR-Posting-Host: 65.41.230.38
From: =?Utf-8?B?RGF2aWQgRGF2aXM=?=
description;Subject: SBS 2003 - Exchange LDAP Errorcomputer.
Date: Fri, 24 Mar 2006 00:21:06 -0800
Lines: 54
Message-ID: <EC9C7BDD-F93C-4D04-9BCA-9E5E420A9FA1@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:255446
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs
My application log is filling up with the following two events:
Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2392
Date: 3/23/2006
Time: 11:02:15 PM
User: N/A
Computer: SERVER
Description:
The description for Event ID ( 2392 ) in Source ( MSExchangeDSAccess )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
You may be able to use the /AUXSOURCE= flag to retrieve this
description;see
Help and Support for details. The following information is part of theevent:
WMIPRVSE.EXE -EMBEDDING, 3892, 35.computer.
and
Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2392
Date: 3/23/2006
Time: 11:01:45 PM
User: N/A
Computer: SERVER
Description:
The description for Event ID ( 2392 ) in Source ( MSExchangeDSAccess )
cannot be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
You may be able to use the /AUXSOURCE= flag to retrieve this
ideas?see
Help and Support for details. The following information is part of theevent:
MAD.EXE, 3924, 35.
I have confirmed that Domain, DNS and Global catalog are function using
dcdiag. I have been able to find zilch on Technet. Anyone have any
AdvancedExchange seems to be functioning fine, however my backups running onSymantec
Backup Exec 10d are grabbing the information store. I keep receiving:
AOFO: Initialization failure on: "Microsoft Information Store".
found,Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE00084AF): The directory or file was not
backup.or could not be accessed.
I turned on the VSS service provider and have kicked off another
In
theory the backup problem should be resolved, but I am still unable tostop
the events from occurring.
--
David Davis [MCSE, CCNA, Security +]
.
- Follow-Ups:
- RE: SBS 2003 - Exchange LDAP Error
- From: David Davis
- RE: SBS 2003 - Exchange LDAP Error
- References:
- SBS 2003 - Exchange LDAP Error
- From: David Davis
- RE: SBS 2003 - Exchange LDAP Error
- From: "Jenny wu [MSFT]"
- RE: SBS 2003 - Exchange LDAP Error
- From: David Davis
- SBS 2003 - Exchange LDAP Error
- Prev by Date: Wireless access on LAN and WAN side
- Next by Date: Re: Exchange user mailbox properties problem
- Previous by thread: RE: SBS 2003 - Exchange LDAP Error
- Next by thread: RE: SBS 2003 - Exchange LDAP Error
- Index(es):
Relevant Pages
|
Loading