question

christmascactus avatar image
0 Votes"
christmascactus asked SharonZhao-MSFT commented

Error when publishing on premise Skype for business topology

I am trying to decomission our hybrid on premise S4B and Lync systems. I've followed this guide decommission-remove-on-prem
. When i come to publish the topology i get the following error:

Error: An error occurred: "System.InvalidOperationException" "Central Management store does not match configured Central Management store database."

I can't find anything after googling it and my knowledge of Skype isn't great. Can anyone help with what his error means?


office-skype-business-server-deployment
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SharonZhao-MSFT avatar image
0 Votes"
SharonZhao-MSFT answered SharonZhao-MSFT commented

@christmascactus,

Which step do you get this error message?

Please note that the official document in your question applies only if you are using Method 2 for managing user attributes, as described here.

In addition, before decommissioning on-premises Skype for Business environment, please complete the first three steps:

Step 1. Move all required users from on-premises to online.

Step 2. Disable your hybrid configuration.

Step 3. Move hybrid application endpoints from on-premises to online.


If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

It happens on step 4 when I try to publish the topology. the first 3 steps worked fine.

Edit
Even if i haven't made any changes, when i try to publish the topology i get the error. I've tried running:

 Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn <SQL serverFQDN> -sqlinstancename <s4b instance> -clean -Verbose

and it still brings the error

0 Votes 0 ·

@christmascactus,

Does this error happen in this step as the image shows? If so, please open a Microsoft support ticket to get help removing the remaining stale objects. This article provides ways to contact support for business products.

90721-image.png


0 Votes 0 ·
image.png (21.2 KiB)

It happens any time it try to publish the topology, even if I open the topology and try to publish it without making any changes I get that error. We don't have a support contract with Microsoft for SfB unfortunately.

0 Votes 0 ·
Show more comments