Presence and Conferencing services are not available because the User Store is down or the connectivity to datacenter has been lost

Presence and Conferencing services are not available because the User Store is down or the connectivity to datacenter has been lost ;source=”yourSBS.domain.com”

This post is written for the possibilities that go along with this error. This article is written for the souls that scour the internet, looking for one thread of truth about what this error means. This text if for the weary, who search for meaning to their troubles.

Yes I spent 7 hours trying to find out what this was, but more importantly how to fix it. Fixing this issue is all in the realization of what had been done to create this issue.

Let me begin by saying its likely not your first rodeo. If you have this error in your Lync or Skype for Business Environment, You likely have deployed some Lync; and you have deployed some Survivable Branch appliances too. You did a great job. In fact, you may have been surprised, when one of your Survivable Branch Servers was acting oddly, compared to the others. Why is this SBS failing with a network issue. This network error occurs when you login and your user has been homed to a Survivable Branch Server (SBS) or appliance. The network error look like this:

network error

And the Lync Client has an error that indicates the connection to the main Pool is down:

Untitled

What makes all the more frustrating, is everything checks out and you have nothing to go on, but the error messages of the client and an error that shows up in the client log. The same error shows on the centralized logging, using Sip and S4 flags to the front end servers. Here is the error again:

Presence and Conferencing services are not available because the User Store is down or the connectivity to datacenter has been lost ;source=”yourSBS.domain.com”

This has all the appearances of a failed main site. Do you have a clue what is happening? Ok time to spill the beans.

Now I am going to generalize the answer, because I now see that a few things could all cause the same problem. This error of concealment occurs, when you do things out of order. You have to be very careful as Lync/SFB is not like Active Directory. Its objects are often nested. There are dependencies everywhere. This generally means there is process to do just about everything. In this case, we are covering a failure to completely destroy and re-create Branch Site Objects. I am listing the problem as it may Occur in several ways:

 

1. You put a New SBA (name) under an old Branch Site.

2. You re-used an old SBA name under an old Branch site and wiped the server or SBA and re-installed.

3. You put an old SBA  (name) under an old site name and old Branch name. 

3. You put the SBA under an old name with a new Site name.

4. The order that you do the 3 items above, and at what point did you demote the SBA/SBS?

5. Did you demote the SBS or did you flatten and use the same AD object?

6. Did you recycle objects? Why?

Hint – Recycle= bad

I think I am missing a possibility here but do you see the point? When Moving SBA/SBS devices form Lync 2013 to Skype for Business, It is best to simply tear the site down completely and Wipe your OS or SBA. Set up a new Site and a new SBA/SBC and then install your Appliance. Perform this move as a top down deployment.

In my situation, The customer had forgotten about the AD object relation to the site object. The result was a Branch site that was eternally cut off from the central site. The routing groups were not able to work with the Fabric or switch primary to secondary properly, and the result was:

“Presence and Conferencing services are not available because the User Store is down or the connectivity to datacenter has been lost ;source=”yourSBS.domain.com””

Don’t let it happen to you!!! Do your upgrade top down. At minimum, remove your SBC from the domain and remove everything from the topology. Get your Software converted properly. Now begin again!

You will be met with uncommon success in common hours.

Advertisements

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