Cannot configure a server at FQDN [0.0.0.0] because another server is already configured there with a different server version number

Problem

Recently I was working on a Lync 2013 deployment, where trusted application servers (used for Remote Call Control with an NEC PBX) needed to be moved from 2010 to 2013. This work was carried out by an external contractor, who removed the trusted application servers from the Lync Topology, published, and then re-added them to the 2013 pool. I can’t be sure exactly what steps were followed, however shortly after it was discovered that all Lync Front End services across all Front End servers would not start:

1

Trying to manually start the services would result in the following error:

2

Checking the Event logs, I could see the following errors:

3

4  5

6

7

 

Again, I’m not sure how this occurred, but it would seem that CMS lost IP address configuration for the Front End servers.

Resolution

To fix the issue, I manually added the Front End server IP addresses to Topology Builder. To do this:

  1. Open Topology Builder,
  2. Right click on each Front End server in your pool, and select Edit Properties…
  3. Instead of using all configured IP Addresses, manually add the server’s IP address

8

  1. Publish the topology

Once replicated, I could once again start Lync Front End services.

Happy Lyn… Skyping!

Damien Margaritis

Insync Technology

5 thoughts on “Cannot configure a server at FQDN [0.0.0.0] because another server is already configured there with a different server version number

      • Well, if it works in your system, great. However I have seen such cases in the past (personally I have seen, not just simply heard from somebody), where a change seemed not to cause any regression, but after a couple of months some convoluted use-case surfaced sneaky ugly issues, that could be traced back to that particular change several months before. So I am by default very skeptic regarding any such change similar to what you described in this post, and the easy detectability of any regression it may cause. Lync is an ugly over-complicated beast.

  1. I blame RCC, Now you just need to convince the client to move to Skype4B and use Call Via Work instead.

    Sure it uses twice the call legs.. but hey, RCC is dead!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s