Workflows failing to be delivered after change in SharePoint site URL.

[avishek_gorai2]

Hi,

Recently we did a reinstallation of our SharePoint server and reconfiguration (mostly from the SharePoint side) for the Duet Enterprise platform.

Post the reinstallation we are facing issues with the Workflows because the Workflow site collection has been changed

The old site collection was http://ourhost:ourport/sites/DuetEnterpriseSolutions/

The new site collection is http://ourhost:ourport/sites/DuetPlatform/

(the host and port remains to same, hence there was no change made to the logical port of the WorkFlow proxy)

I checked the Web Service logs in SOAMANAGER and found the following error (type: Server Internal error 500):

SOAP Faut Exception caught : An unexpected error, has occured on the server: Error details: The site

http://ourhost:ourport/sites/DuetEnterpriseSolutions could not found in the Web appcatiocn SPwebApplication

Name.SharePoint-xxxxxx

From the error it is evident that somewhere the old site collection is being referred to. Also the request payload (captured from SOAManager) for this service call has the URL in one node, which makes me believe that the URL is coming from SCL. We checked all the configuration guides but could not find where this URL is configured and are now lost.

Can you please help us understand the source of this error, and how to resolve it.

Regards,

Avishek.

[binson · Accepted solution]

Hi Avishek,

Could you please update the workflow user subscription once again from new site collection and check it? You can do it by going to u201CTask Centeru201D -> u201CSite Settingsu201D -> u201CGrant user access to SAP workflow tasksu201D. If the user is already present then please remove it and add it again.

While adding the user subscription, SCL system will add the Routing Site URL in one of its internal table. SO in this case the table might be having entry pointing to old Routing Site URL.

Thanks,

Binson

[avishek_gorai2 · Accepted solution]

Thanks Binson,

It turns out that while doing the trusted user mapping the SharePoint system sends the information to SCL (using a Web Service call) which stores the URL and the trusted user list internally. Which is used by SCL and the backend system also for sending and routing the Work Item.