Lync 2013 SE Install - Service Control Manager error

Lync 2013 SE Install - Service Control Manager error

  • Comments 16
  • Likes

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
  • This solved my problem perfectly, thank you!

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

  • Hi! Thank you, i had the same Problem, you saved my day too!

  • I got this exact error, but in my case the Standard Edition pool name already was the server name.

    THE PROBLEM for me was that on my Lync server, the FQDN (e.g.: lync.mydomain.local) was resolving to the ipv4 adres, where as the hostname (lync) was resolving to the ipv6 adres. So, browsing to the Lync file store share from the same Lync server using the FQDN (e.g.: \\lync.mydomain.local\share) popped up a credentials screen, instead of opening the share as I would've expected and as was the case when browsing to the share using just the hostname (e.g.: \\lync\Share). So the credentials for the FQDN were not known yet to the Lync server.

    I SOLVED this by going the computer/domain/workgroup etc settings (right-click computer -> Properties -> Change Settings -> Change -> More and set the 'Primary DNS Suffix for this computer' to the primary domain (e.g.: mydomain.local) and checked 'Change Primary DNS suffix....'

    After a reboot, the FQDN of the Lync server was resolving to the ipv6 adres and thus browsing to the Lync file store share worked without having to provide credentials and I was able to build the Lync Topology successfully!

    Not sure why the DNS suffix entry was missing though, but either way...it now works! ;)

  • I SOLVED with your help. TY

  • Thank you Joe, problem solved.

  • You absolute star. That had me stumped until I found this post.

  • Thanks that was exactly the problem I had too.

  • Thanks, this was our problem too!

  • Thanks for the post. Your a star

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

  • 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 ?

  • Thanks Joe.. Awesome information, that did the trick..

  • Thank you very much, "Name"

  • Thank you, thank you !!!!!!!!!! so much !!!!!!!!!!!!!!!!!!!!!!

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment