RE: C10312e7 Error

There could be some latency, but I would only expect about 5 mintues worth.

Make sure you are running the netmon trace from the Exchange server and that you capture all traffic. I would filter the trace AFTER
the capture and then include LDAP, SMTP, and TCP/IP. You can filter the LDAP specifically and look for the query like they show in
the article if you wish but with the other you can see additional trafic that may be worth looking at.

The LDAP query will show you the address you are looking for in the SearchResponse frame.
--------------------
>Thread-Topic: C10312e7 Error
>thread-index: AcU67AWIsq4yF0d8Qf2eJFH8HveJwA==
>X-WBNR-Posting-Host: 206.194.127.112
>From: "=?Utf-8?B?U2FuZHkgV29vZA==?=" <sandy.wood@xxxxxxxxxx>
>References: <815ADB31-972A-4FAE-9410-33619D54EF4D@xxxxxxxxxxxxx> <4o94PNtOFHA.3136@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: C10312e7 Error
>Date: Wed, 6 Apr 2005 14:03:02 -0700
>Lines: 69
>Message-ID: <F6710804-BEC7-4F4E-923A-ED1B4CA8EA88@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.0
>Newsgroups: microsoft.public.exchange.admin
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.admin:58193
>X-Tomcat-NG: microsoft.public.exchange.admin
>
>Thanks for the link Robert. I did see that kb article and ran Method one
>prior to this post. I ran through Method two and from my workstation to our
>Exchange 2003 server, I got no LDAP captures at all. Mind you, I'm doing all
>the moving and changing in ADUC. I changed the capture to between my
>workstation and our Global Catalog server, which did capture some LDAP stuff,
>but nothing that had any SMTP in it.
>
>"Robert Baker [MSFT]" wrote:
>
>> Hi Sandy,
>>
>> This is documented in the Microsoft article 280765. You can view it and the resolution at http://support.microsoft.com/kb/280765.
>>
>> Glad to help
>> --------------------
>> >Thread-Topic: C10312e7 Error
>> >thread-index: AcU6xTN8CfqEp9GlSKCI6yO+s5IkWw==
>> >X-WBNR-Posting-Host: 206.194.127.112
>> >From: "=?Utf-8?B?U2FuZHkgV29vZA==?=" <sandy.wood@xxxxxxxxxx>
>> >Subject: C10312e7 Error
>> >Date: Wed, 6 Apr 2005 09:25:09 -0700
>> >Lines: 19
>> >Message-ID: <815ADB31-972A-4FAE-9410-33619D54EF4D@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.0
>> >Newsgroups: microsoft.public.exchange.admin
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.admin:58131
>> >X-Tomcat-NG: microsoft.public.exchange.admin
>> >
>> >I've been moving users to new containers in ADUC and after I move a user and
>> >make a change to their Group Membership and click OK, I get a message saying:
>> >
>> >This email already exists in this organisation.
>> >
>> >ID No. C10312e7
>> >
>> >Microsoft Active Directory - Exchange Extension.
>> >
>> >
>> >I've search for duplicates and they don't exist in our Windows 2000 domain /
>> >Exchange 2003.
>> >
>> >
>> >Could this be because Active Directory still thinks the user object exists
>> >in it's former container and is now moved/duplicated in the new container?
>> >--
>> >Sandy Wood
>> >Orange County District Attorney
>> >
>>
>>
>> --
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms
>> specified at http://www.microsoft.com/info/cpyright.htm
>>
>> Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
>> which they originated.
>>
>>
>


--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

.

Relevant Pages

  • RE: C10312e7 Error
    ... > Make sure you are running the netmon trace from the Exchange server and that you capture all traffic. ... > the capture and then include LDAP, SMTP, and TCP/IP. ... >>Thanks for the link Robert. ...
    (microsoft.public.exchange.admin)
  • Re: LDAP versus HP Laserjet MFP 4345
    ... connect to your DC (what is listed in Active Directory Users & Computers, ... > Ip address and host name of exchange server ... >>>But the printer does not find the LDAP server and the Global address ...
    (microsoft.public.exchange.admin)
  • Re: LDAP issues, Please help!
    ... In order to make the Barracuda server ... >more efficient we must set it up with the LDAP from the DC ... >install the LDAP in my DC or Exchange server 2003. ...
    (microsoft.public.exchange.admin)
  • Re: Global Address List unavailable in Entourage! Help?!
    ... > Exchange Server. ... > How do I set up Entourage to find the GAL, ... I have tried every variation of the ldap information my MIS ... tell you the LDAP server to put in your Entourage Exchange account dialog. ...
    (microsoft.public.mac.office.entourage)
  • Re: LDAP - howto get linux to talk to exchange/AD
    ... I agree - problem is DEFINITELY ldap authentication; ... my exchange server is setup to accept clear text, ... and my exchange server. ... My setup is a Novell Netware server hidden from the ...
    (Debian-User)