none
Cumulative Update 3 for Workflow Manager 1.0 (KB3104066) RRS feed

  • Question

  • Hello guys,

    Did somebody try to install the CU3 for the Workflow Manager ?

    one of my clients ask me to do it but i have a strange error :

    Start-WFHostUpgrade : Could not successfully delete the management Service Bus

    topic with multiple retries within a timespan of 00:05:05.8580391.. The

    exception of the last retry is: The remote server returned an error: (401)

    Unauthorized. Authorization failed for specified action: Manage..TrackingId:e10

    a193b-10dd-40c9-8392-1bf26d9c3a32_GCNSPWF1VQ,TimeStamp:6/6/2016 2:52:22 PM.

    At C:\ProgramData\Microsoft\E-Business Servers

    Updates\Updates\Uninstall3104066\UnifiedWFHotfixUpgrade.PS1:499 char:5

    +           Start-WFHostUpgrade -TargetWFVersion $TargetWFVersion

    +           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

        + CategoryInfo          : WriteError: (:) [Start-WFHostUpgrade], TimeoutEx

       ception

        + FullyQualifiedErrorId : WFServiceUpgradeFailed,Microsoft.Workflow.Deploy

       ment.Commands.StartWFHostUpgrade »

    I'm in WF Client/Manager version 2.0.40131.0.

    Service Bus 1.1 and the WF service is working well without any problem.

    does it a know bug ?

    thanks for your support,

    Friday, June 10, 2016 2:39 PM

All replies

  • 401 error telling me that there is permission issue.

    Please make sure the account under which you are log in should have access to workflow database and services.


    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://krossfarm.com

    • Proposed as answer by Veera Kota Tuesday, June 20, 2017 7:03 PM
    Friday, June 10, 2016 7:07 PM
  • Hi,

    I have the same problem and I solved the package installation with the same account that have installed Workflow Manager 1.0

    I think that there are the permission issue in the database schema.

    Bye!

    Raffa!

    Wednesday, May 10, 2017 10:26 AM