Just recently I added another 2013 Front End Server to an Enterprise Pool and was subsequently presented with some interesting issues.
After adding the new Front End to the Topology and running the setup I moved on to migrating some test users and saw the following error:
Distributed Component Object Model (DCOM) operation SetMoveResourceData failed??
I checked the replication and all Lync servers were replicating.
Checking the Lync Topology servicers I found that my new Front End server wasnt in show room condition, see below:
The green check on the 3rd line shows replication OK but status not OK
So now I am wondering which services are not running, off to Front End number 3 to check the Lync services. As supected there are services that arent running.
Turns out both the Call Park Service and the Response Group Service wont start. Perhaps there is a hint as to why in the Event Log..
..and I found this clue. Seems that FE3 is unable to connect to the backend SQL. Also the little Inner exception reference (saw that in the DCOM reference).
Login failed for user was the real gem.
Checking with the SQL admin I got confirmation that FE3 was trying to connect to the Backend SQL database and failing the login about once every second (SQL guy not happy).
OK, so how come FE3 doesn’t have the permissions on the Backend SQL server??
Seems that my temporary SQL Admin rights were not in place when adding FE3 to the Topology, this is when the SQL permissions are set. Interestingly there were no errors when I published the Topology.
How to fix these permissions? Either get unhappy SQL admin to re-publish the Topology with his SQL Admin account or get temporary SQL Admin permissions and DIY.
…yes, and voila