Registration Wizard stuck at SharePoint Service Broker step

  • 15 February 2022
  • 0 replies
  • 42 views

Userlevel 5
Badge +20
 

Registration Wizard stuck at SharePoint Service Broker step

kbt154541

PRODUCT
K2 Five
K2 blackpearl
TAGS
SharePoint
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.

Issue

The Registration Wizard seems to be stuck at the SharePoint Service Broker step.

Image

 

Symptoms

While this is typical of a web application with a lot of sites, this may also indicate errors from SharePoint.

Troubleshooting Steps

Please use one of the options below to resolve this issue:
 
  1. Resolve SharePoint-related Errors

    Review the host server logs for any errors related to SharePoint while the Registration Wizard is running. Below is a common example of an error you may encounter:  

    eg.
    "SharePointRoleProvider.GetContainers: System.Reflection.TargetInvocationException: An unexpected failure was encountered when contacting SharePoint to get information from the group provider [Group Provider]: The SharePoint server has indicated that the web service could not be found. Consider updating the group provider configuration. ---> System.Net.WebException: The remote server returned an error: (404) Not Found."

    As a workaround for this error, you may temporarily remove the [Group Provider] from the K2 Management Site. If you are on a version earlier than K2 blackpearl 4.7,  you may refer to the following article for instructions on how to delete a SharePoint Group Provider.
     
  2. Increase the executionTimeout value in the Smartforms Runtime web.config

    The default value is 320 seconds. You may increase this value to complete the Registration Wizard.
     
    <httpRuntime maxRequestLength="16384" requestValidationMode="2.0" enableVersionHeader="false" sendCacheControlHeader="false" executionTimeout="320" />

0 replies

Be the first to reply!

Reply