Lync 2013 SE Install - Service Control Manager error

  • Article

So, ran into a little issue in my lab that I thought I'd share...since the solution wasn't readily apparent (at least at first).

So, I was trying to install a Lync 2013 Standard Edition server as the first server in an org.  The server name was Lync15SE (lync15se.contoso.com).  While going through the Lync Topology Builder, I got to the question about what the Pool name would be.  Not giving it a ton of thought, I entered "lyncpool.contoso.com".  I then finished configuring everything in Topology Builder that I needed and went to Publish Topology.  The publish failed with it complaining:

Error: Cannot open Service Control Manager on computer "lyncpool.contoso.com". This operation might require other privileges.

At the time, I was doing the install as the Enterprise Administrator...it has all the rights in the world, what permissions could be missing?  Or is something blocking an Enterprise Admin from doing this in Lync 2013 (I didn't remember a problem using that account with Lync 2010).

I tried uninstalling SQL Express, making sure lyncpool.contoso.com was in DNS, re-running the setup of the Configuration Manager, tried setting up and using a service account instead of the Enterprise Administrator account...all to no avail.  I searched Technet as well as our internal Microsoft Knowledge Bases...everything I found said it was a permissions issue.

Finally, it dawned on me...Standard Edition pool names MUST be the server name.  Only with Enterprise Edition can you create a separate pool name.

I went back into Topology Builder and changed the pool name to lync15se.contoso.com (the SE server's hostname) instead...and VOILA, I was able to publish.

I think (I haven't gone back and verified) that Lync 2010 Topology Builder checked (or prevented you) from using a different name for a Standard Edition server.  Lync 2013 RTM definitely does not.

Comments

  • Anonymous
    January 01, 2003
    Thanks for the post. Your a star

  • Anonymous
    January 01, 2003
    Thanks, this was our problem too!

  • Anonymous
    January 01, 2003
    Thanks a lot!

  • Anonymous
    January 01, 2003
    I SOLVED with your help. TY

  • Anonymous
    January 01, 2003
    I am also getting the same issue and i am installing lync 2013 on single Vmachine in my lab and the issue is with SQL server FQDN, under SQL Server stores, it is not allowing me to enter correct FQDN name, anything away from FQDN name in the FQDN field is not a problem but then unable to publish topology, any help ?

  • Anonymous
    January 31, 2013
    This solved my problem perfectly, thank you!

  • Anonymous
    April 18, 2013
    You saved my day, Joe. There was no indication in the logs where to search for this error.

  • Anonymous
    May 03, 2013
    Hi! Thank you, i had the same Problem, you saved my day too!

  • Anonymous
    May 24, 2013
    The comment has been removed

  • Anonymous
    July 26, 2013
    Thank you Joe, problem solved.

  • Anonymous
    November 05, 2013
    You absolute star. That had me stumped until I found this post.

  • Anonymous
    November 19, 2013
    Thanks that was exactly the problem I had too.

  • Anonymous
    February 12, 2014
    Hi Joe, you are the man!! You save my job and my Project, thank you so much.

  • Anonymous
    February 27, 2014
    Thanks Joe.. Awesome information, that did the trick..

  • Anonymous
    March 03, 2014
    Thank you very much, "Name"

  • Anonymous
    April 07, 2014
    Thank you, thank you !!!!!!!!!! so much !!!!!!!!!!!!!!!!!!!!!!

  • Anonymous
    April 07, 2014
    Thank you, thank you !!!!!!!!!! so much !!!!!!!!!!!!!!!!!!!!!!

  • Anonymous
    May 12, 2014
    Thanks, this was my problem too!

  • Anonymous
    June 11, 2014
    Thanks a lot...SOlved my Problem too....

  • Anonymous
    June 26, 2014
    The comment has been removed

  • Anonymous
    September 20, 2014
    Joe,

    Thanks very much for this, solved my issue!

    Tom

  • Anonymous
    September 24, 2014
    Thank you very much!!

  • Anonymous
    October 14, 2014
    after long time searching the solution was here .
    Thank you

  • Anonymous
    December 25, 2014
    Thank you Joe! You're genius!

  • Anonymous
    December 26, 2014
    Thank you it helped me too..

  • Anonymous
    March 23, 2015
    Excellent my buddy, I coud resolve the same issue!!!!

  • Anonymous
    September 08, 2015
    Thank you for the clue. Had the same issue with Skype for Business

  • Anonymous
    November 02, 2015
    Thank you very much for that !!

  • Anonymous
    November 06, 2015
    Name, Thank you very much

  • Anonymous
    November 10, 2015
    thanks! that solved my issue to with Skype for Business

  • Anonymous
    January 12, 2016
    Thank you so much!! Silly issue causing a big headache.

  • Anonymous
    February 01, 2016
    You a boss!

  • Anonymous
    February 05, 2016
    Thanks a lot ...

  • Anonymous
    February 25, 2016
    Thank You So much this was really helpful :)

  • Anonymous
    March 30, 2016
    Perfect threat! Helped so much! Thx :-)

  • Anonymous
    April 16, 2016
    Grazieeeee!!!! sei un genio!