Azure Service Fabric
An Azure service that is used to develop microservices and orchestrate containers on Windows and Linux.
252 questions
Host is not joining to Workflow Manager farm
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 4%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAT%3C/text%3E%3C/svg%3E)
Ava Tomlinson
96
Reputation points
We have a SharePoint Workflow Manager Farm (SharePoint 2016 on-premise environment) running on a single server. We were trying to upgrade Azure Service Fabric version 5.1.163.9590 with version 9.1.1121.9590 on Workflow Manager server Which requires to leave the Workflow Farm and rejoin it. While rejoining the Worklfow Manager farm, we got an error message that farm is partially joined. Steps followed to install Microsoft Azure Service Fabric Version 9.1.1121.9590:
- Take a snapshot of the server for precautionary measures.
- Open Workflow Manager Configuration and leave the farm.
- Now uninstall Microsoft Azure Service Fabric 5.1.163.9590 from the control panel.
- Restart the server.
- Run the command below to install Service Fabric using Workflow PowerShell opened as an administrator and move to the same folder where the exe file is located with the cd command. .\MicrosoftServiceFabric.9.1.1583.9590.exe /accepteula
- Restart the server.
- Verify the Microsoft Azure Service Fabric version from the control panel.
- Ensure the Windows firewall service is running.
- At this point, rejoin the server using Workflow Configuration Manager with the following credentials and generation keys. ERROR-
[Error] [1/13/2024 7:22:25 AM]: System.Management.Automation.CmdletInvocationException: The remote server returned an error: (404) Not Found. The incoming request is not recoginzed as a namespace policy put request: Unrecognized policy type: SubscriptionDescription, http://schemas.microsoft.com/netservices/2010/10/servicebus/connect.TrackingId:5b0aff8a-7d17-4f0c-af50-89769d59ae2d_Gde,TimeStamp:1/13/2024 7:22:25 AM ---> Microsoft.ServiceBus.Messaging.MessagingEntityNotFoundException: The remote server returned an error: (404) Not Found. The incoming request is not recoginzed as a namespace policy put request: Unrecognized policy type: SubscriptionDescription, http://schemas.microsoft.com/netservices/2010/10/servicebus/connect.TrackingId:5b0aff8a-7d17-4f0c-af50-89769d59ae2d_Gdei,TimeStamp:1/13/2024 7:22:25 AM ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.ServiceBus.Messaging.ServiceBusResourceOperations.CreateOrUpdateAsyncResult`1.EndGetResponse(CreateOrUpdateAsyncResult`1 thisPtr, IAsyncResult ar)
at Microsoft.ServiceBus.Messaging.IteratorAsyncResult`1.StepCallback(IAsyncResult result)
--- End of inner exception stack trace ---
Server stack trace:
Exception rethrown at [0]:
at Microsoft.ServiceBus.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.ServiceBus.NamespaceManager.CreateOrUpdateSubscriptionAsyncResult.OnCreateSubscription(IAsyncResult result)
at Microsoft.ServiceBus.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
Exception rethrown at [1]:
at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Workflow.Administration.ServiceUpdateManager.CreateManagementEntities(IList`1 namespaceManagerUris, ServiceBusClientCredentialType clientCredentialType, IDictionary`2 arguments, TimeSpan retryTimeout)
at Microsoft.Workflow.Deployment.Commands.WorkflowServiceConfigHelper.SetWFRuntimeSettings(String resourceDBConnectionString, String config)
at Microsoft.Workflow.Deployment.Commands.AddWFHost.CallWFRuntimeSettings(Service wfserviceInfo, String unencryptedResourceConnectionString)
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Workflow.Deployment.ConfigWizard.CommandletHelper.InvokePowershell(Command command, Action`3 updateProgress)
at Microsoft.Workflow.Deployment.ConfigWizard.ProgressPageViewModel.AddWFNode(FarmCreationModel model, Boolean isFirstCommand)
.ProgressPageViewModel.AddWFNode(FarmCreationModel model, Boolean isFirstCommand)
While rejoining the Worklfow Manager farm, we got error message that farm is partially joined. We were able to join SB Farm, but not the WF Farm getting below mentioned error. The Workflow Manager was working fine before leaving the farm (prior to upgrading Microsoft Azure Service Fabric to 9.1.1121.9590).
Looking for Solution of this issue.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(160, 17%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYJ%3C/text%3E%3C/svg%3E)
Yanli Jiang - MSFT 21,611 Reputation points Microsoft Vendor2024-01-24T03:08:35.63+00:00 Hi @Ava Tomlinson ,
I understand your feelings very well. However, there are many reasons for this problem. There may be a problem with the Microsoft Azure Service Fabric upgrade process, but this is beyond my ability. I have added relevant tags and hope that the product engineers will give professional judgment. Because SharePoint itself has not been modified, problems may also occur during the connection process.
It is recommended that you do the following checks:
- Verify that the Service Bus is running and accessible. You can check the Service Bus logs to see if there are any errors or warnings that might indicate an issue.
- Check the credentials used to join the Workflow Manager farm. Make sure that the account has the necessary permissions to join the farm and that the credentials are correct.
- Check the firewall settings on the Workflow Manager server and the SharePoint servers. Make sure that the necessary ports are open and that the servers can communicate with each other.
Hope this helps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.
-
Ava Tomlinson 96 Reputation points
2024-01-24T07:29:37.9966667+00:00 - We took a server snapshot before the upgrade and restored it to the initial state due to the issue. We also took a copy of the logs before the snapshot restore. Server log confidential info has been removed.txt
- The credentials of the service account are correct.
- If we stop the Windows Firewall service, we get the error "Port number 9002, specific for internal communication, is blocked within the port range." Therefore, we joined the existing farm with the Windows Firewall service running.
-
Ava Tomlinson 96 Reputation points
2024-01-24T07:33:54.5133333+00:00 From the log, we can observe that the Service Bus is attempting to connect to http://schemas.microsoft.com/netservices/2010/10/servicebus/connect, which is identified as inaccessible. Could you please confirm whether whitelisting this URL can resolve the issue? We also require the following details:
- Destination IP address:
- Destination port(s):
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 4%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
kobulloc-MSFT 23,491 Reputation points Microsoft Employee2024-01-26T00:34:35.5266667+00:00 Hello, @Ava Tomlinson ! We have received your feedback and want to make sure that your question is answered. To determine why you are running into a namespace policy error, we will need to take a closer look at your resources. Please email the following to AzCommunity@microsoft.com and we'll get back to you promptly:
- Subject: "Attn: kobulloc - Service fabric migration error"
- Email body: Your Subscription ID
- Email body: A link to this thread so we can validate and expedite the request
If you don't receive a response within 24 hours, please reply to the thread so we can investigate.
Sign in to comment