Sign in
 
HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs
TechCenter >
> 
> 
Error publishing topology or making changes (duplicate object in AD)

Answered Error publishing topology or making changes (duplicate object in AD)

  • Monday, December 12, 2011 2:48 PM
     
     
    Sign In to Vote
    0

    Hi there,

    I've been trying to get Lync/OWA integration going in a lab. As part of that, it looks like Lync has inadvertently created multiple objects in AD to represent the trusted application, which is now generating errors when I try and publish a topology update, or just run even run a cs-enabletopology.

    I've tried running remove-CsTrustedApplication to remove the object, but it again throws up the same error (see below).

    I believe somewhere I've inadvertently created this object twice in AD, and it's now complaining. Does anyone know how I might forcibly remove it?

    Regards, James.

    The exact error is:

    Enable-CsTopology : Command execution failed: Found multiple objects with identity "server.fqdn,exchangeowa" in Active Directory.
    At line:1 char:18
    + Enable-CsTopology <<<<
        + CategoryInfo          : InvalidOperation: (:) [Enable-CsTopology], ActiveDirectoryException
        + FullyQualifiedErrorId : ProcessingFailed,Microsoft.Rtc.Management.Deployment.ActivateTopologyCmdlet

    James Frost
     

All Replies

  • Monday, December 12, 2011 5:51 PM
     
     
    Sign In to Vote
    0

    Have you tried to open the topology builder, and remove the objects from there-in?

    You can do this, then recreate your objects.

    Lasse Wedø,
    Blog:Tech@work, Twitter: @lawedo

    Please take a second to hit the green arrow on the left if the post was helpful, or mark it as an answer if it resolved your issue.
     
  • Monday, December 12, 2011 8:16 PM
     
     
    Sign In to Vote
    0

    The only related objects in the topology builder is the Trusted Application Pool/servers. Whilst it lets me delete them from the topology, it doesn't let me publish the amended topology back again, citing the same error I provided above.

     

    Is there some other way to remove the object, or at least identify which duplicate object in AD it's referring to?

    James Frost
     
  • Monday, December 12, 2011 8:59 PM
     
     
    Sign In to Vote
    0

    Have you delteted it, published the topology after deleting it.

    Invoke the management replication. Then try republish it.

     

    You could also, from Powershel try to remove the trusted app pool (this will remove the app as well), then enable the cs topology, before recreating the pool and app.

    I have done so a couple of times my self, had no problems with it. (You just need to publish your deletion, wait for replication and then re create things).

    Lasse Wedø,
    Blog:Tech@work, Twitter: @lawedo

    Please take a second to hit the green arrow on the left if the post was helpful, or mark it as an answer if it resolved your issue.
     
  • Monday, December 12, 2011 10:11 PM
     
     Proposed
    Sign In to Vote
    0

    This is what I've tried:

    1. Just downloading the topology in Topology Builder - then publishing it back (no change). The Publish works, but fails at the last stage Enabling Topology, citing the same error about duplicate objects. This is the same error I get if I just ran get the Enable-CsTopology PS command
    2. I've tried deleting the Trusted Application Pool from the topology, and publishing the changes back. Fails at the first Publishing Topology stage , citing the duplicate object error.
    3. I've tried deleting the Trusted Application Pool, and recreating it with same and a different name. Fails at the first Publishing Topology stage , citing the duplicate object error
    4. I've tried deleting both the Trusted Application Pool and Trusted Application using Powershell, both attempts fail, citing the same duplicate object error

    I can provide a log file if you think it would help. I'm stumped as to how I can fix this.

    Thx. James.

    James Frost
     
  • Tuesday, December 13, 2011 12:21 AM
     
     Answered
    Sign In to Vote
    0

    I have resolved this. There were two objects for the same application pool under the CN=Trusted Services,RTC Service, CN=Microsoft path.

    Once I deleted one of them using ADSIEdit.msc I was able to re-publish my topology, and continue maintaining the environment.

    ... not ideal. I have no idea why this happened, probably because I was publishing changes in quick succession and not waiting for replication to finish.

    James Frost
    • Marked As Answer by James Frost Tuesday, December 13, 2011 12:21 AM
    •