Our subscription status has been stuck in "SettingUp" for 4 hrs, Please advise.
Thanks,
Eric
Our subscription status has been stuck in "SettingUp" for 4 hrs, Please advise.
Thanks,
Eric
I heard back from the SPP Team on this issue.
"The SPP service is not able to access the partner subscription (Sage 100 Testing DSD) and receiving an error.
ok - I ran through all of that again, we'll see if the third time is a charm.
We believe we've found the cause of this issue. The subscription ID entered into the SPP portal was incorrect. When you receive email from Insights, there will be two GUIDs. One is the Partner ID and…
I am having this same problem as well. Reran power shell scripts and am trying again.
It is still saying fault after rerunning the script
We believe we've found the cause of this issue. The subscription ID entered into the SPP portal was incorrect. When you receive email from Insights, there will be two GUIDs. One is the Partner ID and the other is the Subscription ID. It's easy to mistake the two because all GUIDs look the same . Verify your Subscription ID in the Azure portal and make sure that matches the Subscription ID you enter into the Sage SPP portal. If you have the wrong GUID, you will need to create a new Subscription with the correct ID (delete the old one later). Remove any Service Provider Delegations in the Azure portal and then re-run the Powershell Scripts. Note that you'll need to re-upload them as the GUIDs will have changed. Upload both files before launching the script. Once the scripts finish, you should now be able to kick off the Subscription Setup.
We believe we've found the cause of this issue. The subscription ID entered into the SPP portal was incorrect. When you receive email from Insights, there will be two GUIDs. One is the Partner ID and the other is the Subscription ID. It's easy to mistake the two because all GUIDs look the same . Verify your Subscription ID in the Azure portal and make sure that matches the Subscription ID you enter into the Sage SPP portal. If you have the wrong GUID, you will need to create a new Subscription with the correct ID (delete the old one later). Remove any Service Provider Delegations in the Azure portal and then re-run the Powershell Scripts. Note that you'll need to re-upload them as the GUIDs will have changed. Upload both files before launching the script. Once the scripts finish, you should now be able to kick off the Subscription Setup.
*Community Hub is the new name for Sage City