none
Error while attempting to publish topology.. RRS feed

  • Question

  • i currently have an ocs 2007 r2 environment and im trying to install lync server. i was able to get through all steps in the wizard up to the publishing the topology section. when i open the topology builder and begin the wizard, it bombs out on the 2nd step, "setting central management store location" i have a link to a screen shot of the error iam getting.. any help here is greatly appreciated.

     

    http://i21.photobucket.com/albums/b290/5royce9/error.jpg

    Monday, January 10, 2011 2:12 PM

Answers

  • Hm.  This needs a scalpel (netmon trace of the ldap and whatnot) but we're confined to hammers on the forums.  Here are the hammers in the order they should be tried.

    1.  Delete that conflict object.  Force AD replication and wait for it to complete.

    2.  Run Get-CsAdServerSchema.  If it does not say "schema_version_state_current" then re-run schemaprep and wait for replication (you'll see me say this a lot...it's an important step especially with these symptoms).  This creates the msRTCSIP-GlobalTopologySetting class that we're ultimately trying to populate.

    3.  Run Enable-CsAdForest, Enable-CsAdDomain, wait for replication to finish.  Run Get-CsAdForest, Get-CsAdDomain to confirm the change took.

    4.  Retry publishing the topology.

    5.  If still no luck, remove "Topology Settings" altogether.  Wait for replication.  Try steps 3-4 again.

    Note: it's safe to re-run schema/forest/domain prep over the top of itself over and over.  At no time during our troubleshooting should you disable or unprep.  It could cause problems with your existing R2 install.

     If you're still stuck let me know if any symptoms changed.  We might need to get you directed over to support.

    • Proposed as answer by Josh - MSFT Thursday, January 20, 2011 7:02 PM
    • Marked as answer by Ben-Shun Zhu Friday, January 21, 2011 9:37 AM
    Tuesday, January 18, 2011 9:38 PM

All replies

  • Hi,

    R U installing it with OCS 2007 or on new AD ?

    Also check event viewer and let us know if there is any error.

    Regards.

     

    Shafaquat Ali.

     


    M.C.I.T.P Exchange 2007/2010, M.C.I.T.P Windows Server 2008, M.C.T.S OCS Server 2007 R2, URL: http://blog.WhatDoUC.net Phone: +923008210320
    Monday, January 10, 2011 7:26 PM
  • yea, i already have ocs 2007 r2 set up in my AD environment...

     

    when i run the publish topolgy wizard, after the wizard fails there are 4 events in event viewer, dont look like anything serious though, here are the links as to what they are...

     

    http://i21.photobucket.com/albums/b290/5royce9/msg1.jpg

    http://i21.photobucket.com/albums/b290/5royce9/msg2.jpg

    http://i21.photobucket.com/albums/b290/5royce9/msg3.jpg

    http://i21.photobucket.com/albums/b290/5royce9/msg4.jpg

    http://i21.photobucket.com/albums/b290/5royce9/msg5.jpg

    Monday, January 10, 2011 7:46 PM
  • Whether you are setting up a Standard or Enterprise Edition Lync 2010 Server, it is essential to get the Central Management Store (CMS) ready beforehand. This is true for both Lync only installation or Lync + OCS 2007 / R2 coexistence scenarios. Check out the series of installation walkthrough here that may be of help to you.

    Please share with us if this helps. Thanks.

     


    TechNet Forum Moderator (Unified Communications) - http://www.leedesmond.com
    Monday, January 10, 2011 9:43 PM
    Moderator
  • thanks desmond, i will check this stuff out now, i will follow up as soon as i get through it all.
    Monday, January 10, 2011 9:45 PM
  • ok, i just read through all of them, i cant really find anything in there that is of any help to me. to be honest, it looks like my CMS does not exist, i have no idea why it wasnt created during the setup, from what i saw, it was supposed to be already created if i got this far. is there any way i can set it up manually or something?  it seems thats my only problem right now

    Monday, January 10, 2011 10:03 PM
  • The Lync 2010 deployment considerations are outline here . Assuming you are creating the first Lync 2010 Server using the Standard Edition, you will need to run the step "Prepare first Standard Edition Server". This creates the database necessary for the new CMS component. Next, install, author and publish the desired Lync topology into the CMS. Only then should you begin with the steps in sequence under "Install or Update Lync Server System".

    The previous link provides a detailed installation walkthough and explanation of some of the new technologies/features in Lync could be overwhelming at first for some.

    Hope this helps. Do let us know. Thanks.

     


    TechNet Forum Moderator (Unified Communications) - http://www.leedesmond.com
    Tuesday, January 11, 2011 10:36 AM
    Moderator
  • ive actually already ran through all these steps, in the order provided. it seems something missed along the way though, hence my dilemma now..  im on the publish topolgy step and that is where this is failing...
    Tuesday, January 11, 2011 2:03 PM
  • while running the lync server deployment wizard, theres a step in there labled "install or update lync server system"...

     

    am i to run that before or after i try to publish the topology, because iam trying to run it now and im getting an error that states, "automatic collection of configuration data failed"

    Tuesday, January 11, 2011 9:40 PM
  • Are you installing a Standard Edition Server?

    Did you prep AD and then perform the step "prepare for the first Standard Edition server"? This will install the management store on the Standard Edition server and publish it in AD.

    Topology builder uses an AD lookup to locate the Central Management Store and this fails on your side.

    If you did prepare the first Standard Edition and it still doesn't work, please use the following command to set the AD service connection point:

    Set-CsConfigurationStoreLocation

    SYNOPSIS

        Sets the Active Directory service control point for the Central Management store.

    SYNTAX

        Set-CsConfigurationStoreLocation -SqlServerFqdn <Fqdn> [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-GlobalSettingsDomainController <Fqdn>] [-Report <String>] [-SkipLookup <SwitchParameter>] [-SqlInstanceName <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]


    Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
    If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.
    Wednesday, January 12, 2011 8:37 AM
  • this will be a standard edition server, and yes, i ran all prior steps in the wizard.  i will give that command a try now. ill post back the results shortly
    Wednesday, January 12, 2011 4:24 PM
  • ok, so when i run the set-csconfigurationstorelocation cmdlet, followed by the required parameter of -sqlserverfqdn <fqdn>, i still get the same error about active directory global settings container not being found. i have the link to a screenshot here..

     

     

    http://i21.photobucket.com/albums/b290/5royce9/error-1.jpg

    Wednesday, January 12, 2011 4:32 PM
  • Lets check the location by hand.

    1. Run ADSIEdit.msc
    2. Right click the root of the tree and select "Connect to".
    3. In the "select a well known..." dropdown choose "Configuration" and hit ok.
    4. Expand the configuration container, then services, RTC Service, Toplogy Settings
    5. You'll find a GUID looking object there.  Right click it and choose properties.
    6. Find the msRTCSIP-GlobalTopologySetting attribute in the list.  It should have a value that corresponds to your CMS (your SE server in this case).

    Given the trouble you're having you'll more than likely hit more trouble while executing these instructions but hopefully the error you hit will give us a better clue.

    If you find something missing as you're drilling down through the above then check your DCs for any replication related errors.  Also confirm if your schema, forest, and domain are prepped with: Get-CsAdServerSchema, Get-CsAdForest, Get-CsAdDomain

    If you hit some other problem please post details again.

    Thanks,

    Josh

     

     

    Monday, January 17, 2011 7:45 PM
  • thx josh, i think this is exactly what i was looking for.. i dont see that attribute in the properties for the "topology settings" container, but i posted a screen shot just to make sure i am looking at the right thing before we even go any further...

     

     

    http://i21.photobucket.com/albums/b290/5royce9/shot.jpg

    Monday, January 17, 2011 8:19 PM
  • You'll need to look in the folder above the one you selected now, just the "Topology Settings" entry. If you click on it, you should see an object on the right pane. If it does not exist, you'll need to re-register it.

    You can create the object using the following Lync Shell command:

    Set-CsConfigurationStoreLocation -SqlServerFQDN "the.fqdn.of.your.server.hosting.central.management.store"


    Technical Specialist Microsoft OCS/Lync & UC Voice Specialisation - http://www.uwictpartner.be
    If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.
    Tuesday, January 18, 2011 5:50 AM
  • ok, its good we got to that.. bc THAT is exactly where im getting an error that keeps looping back to this point... the topology settings container is indeed empty, so when i try to run that command i get an error, here is what the error looks like..

     

    http://i21.photobucket.com/albums/b290/5royce9/lyncerror.jpg

     

    its stating that it cannot locate the configuration store location in AD global settings container.. and just so you know where im at in my deployment, here is what my deployment wizard looks like..

     

    http://i21.photobucket.com/albums/b290/5royce9/wiz.jpg

     

    i do appreciate all your help here...

    Tuesday, January 18, 2011 4:54 PM
  • thx josh, i think this is exactly what i was looking for.. i dont see that attribute in the properties for the "topology settings" container, but i posted a screen shot just to make sure i am looking at the right thing before we even go any further...

     

     

    http://i21.photobucket.com/albums/b290/5royce9/shot.jpg


    You're in the right place but you have two of them in there.  One is a conflict (CNF) object which means AD replication trouble of some sort.  Often this is seen by proceeding to later steps before AD replication has finished... An identical object gets created while pointed to two different DCs.  When replication happens they bump heads and a CNF is created.

    Expand each, see if one has the correct data.  If it does, you should be able to delete the other and (if necessary) rename the good one.  Let me know if this gives you any trouble.  I might have to ping some folks with heavier AD kung-fu than I.

    Tuesday, January 18, 2011 7:45 PM
  • thx josh, i think this is exactly what i was looking for.. i dont see that attribute in the properties for the "topology settings" container, but i posted a screen shot just to make sure i am looking at the right thing before we even go any further...

     

     

    http://i21.photobucket.com/albums/b290/5royce9/shot.jpg


    You're in the right place but you have two of them in there.  One is a conflict (CNF) object which means AD replication trouble of some sort.  Often this is seen by proceeding to later steps before AD replication has finished... An identical object gets created while pointed to two different DCs.  When replication happens they bump heads and a CNF is created.

    Expand each, see if one has the correct data.  If it does, you should be able to delete the other and (if necessary) rename the good one.  Let me know if this gives you any trouble.  I might have to ping some folks with heavier AD kung-fu than I.


    hey josh, theres no data in either one of those containers   :(
    Tuesday, January 18, 2011 8:18 PM
  • Hm.  This needs a scalpel (netmon trace of the ldap and whatnot) but we're confined to hammers on the forums.  Here are the hammers in the order they should be tried.

    1.  Delete that conflict object.  Force AD replication and wait for it to complete.

    2.  Run Get-CsAdServerSchema.  If it does not say "schema_version_state_current" then re-run schemaprep and wait for replication (you'll see me say this a lot...it's an important step especially with these symptoms).  This creates the msRTCSIP-GlobalTopologySetting class that we're ultimately trying to populate.

    3.  Run Enable-CsAdForest, Enable-CsAdDomain, wait for replication to finish.  Run Get-CsAdForest, Get-CsAdDomain to confirm the change took.

    4.  Retry publishing the topology.

    5.  If still no luck, remove "Topology Settings" altogether.  Wait for replication.  Try steps 3-4 again.

    Note: it's safe to re-run schema/forest/domain prep over the top of itself over and over.  At no time during our troubleshooting should you disable or unprep.  It could cause problems with your existing R2 install.

     If you're still stuck let me know if any symptoms changed.  We might need to get you directed over to support.

    • Proposed as answer by Josh - MSFT Thursday, January 20, 2011 7:02 PM
    • Marked as answer by Ben-Shun Zhu Friday, January 21, 2011 9:37 AM
    Tuesday, January 18, 2011 9:38 PM
  • MONEY!! looks like that worked, i guess that confilict was what was stopping it from going through.. i got to your step 4 and the publish topology step passed, along with everything else after that. i now have it successfully set up and running, however im faced with anther small issue.. now im working in the control panel trying to enable users for lync server and when i try to search for users its not returning all the users in my domain, it looks like i just need to change the domain controller as to where it is searching on, when i run a search for a specific user it gives me an error saying it cant find that user on the domain controller...  i cant seem to figure out how to do that here..
    Thursday, January 20, 2011 2:33 PM
  • nvm, i got it.. haha, looks like it only randomly returns 200 users by default.. i have to manually search for others...
    Thursday, January 20, 2011 4:57 PM
  • Glad to hear you're fixed!  I hope you dig the product!
    Thursday, January 20, 2011 7:03 PM
  • THany it solved my Problem
    Monday, September 3, 2018 1:36 PM