none
Service Message broker services in Starting - SharePoint 2013 RRS feed

  • Question

  • Hi,

    One of our SharePoint 2013 Production server is updated & its Framework updated to 4.6.1

    Now Service Message Broker service is starting which not allows us to start, stop &  Restart, cause SharePoint 2013 workflows not working on Prod server.

    

    As per research I found that windows is update we need to update Service bus 1.0 to 1.1 as well. I download update of Service bus from this link. When I run the setup it gives me error: An unexpected internal error has occurred 

    Kindly advice

    Thanks


    طحہ زبیر احمد Taha Zubair Ahmed http://www.tahazubair.blogspot.com

    Thursday, November 24, 2016 8:36 AM

All replies

  • Hi Taha, the link you referring to is for Service Bus 1.0, so if you upgraded to Service Bus 1.1 you do not need that upgrade. 

    However, if you did upgrade to Service Bus 1.1, you will need to install the Service Bus KB3086798 update.

    Be careful, when you implement an upgrade to Service Bus 1.1 from a previous WFM Farm with Service Bus 1.0, the process is not straightforward, you need to implement the below steps:

    To upgrade a Service Bus farm

    1. Stop the Service Bus for Windows Server farm: from a PowerShell console window, call the Stop-SBFarm cmdlet

    2. On each of the farm nodes, leave the farm. From a PowerShell console window, call the Remove-SBHost cmdlet.

    3. On each of the farm nodes, uninstall Service Bus for Windows Server 1.0. From Add/Remove Programs in Control Panel, uninstall Service Bus for Windows Server 1.0 (or Service Bus for Windows Server 1.0 CU1). Note that there is no need to uninstall Windows Fabric.

    4. On each of the farm nodes, install Service Bus for Windows Server 1.1 using the Web Platform Installer.

    5. From one of the farm nodes, upgrade the farm’s databases. Call the Invoke-SBFarmUpgrade cmdlet and provide a connection string to your management database as well as the certificate auto generation key.

    6. On each of the farm nodes, join the farm by using either the configuration wizard, or the Add-SBHost cmdlet.

    7. To join a Windows Azure Pack management portal, use the Set-SBFarm cmdlet to add the resource provider credentials for admin and tenant. Note that you must deploy the Windows Azure Pack first.

    8. In the Windows Azure Pack management portal, you may want to associate existing namespaces with WAP subscriptions. Call the Set-SBNamespace cmdlet and add a subscriptionID value to existing namespaces.

    Please follow the below article for that

    https://msdn.microsoft.com/en-us/library/dn441403.aspx

    Hope that helps

    Cheers


    Please mark as helpful if this was helpful.


    Thanks & Regards, Jose

    Tuesday, December 13, 2016 4:53 PM