Problem with Workflow task: The parameter 'CreateTaskRequest.ExtensibleElements.Language' is arequired field. It cannot be null or empty.

[Former Member]

I am using the verification Workflow Task to check the end-to-end configuration of Workflow with DE FP1 as descriped in the operation guide.

The workflow task is getting send from backend to NW Gateway and then to Sharepoint. But we get an error response back saying:

The parameter 'CreateTaskRequest.ExtensibleElements.Language' is arequired field. It cannot be null or empty.

These are the Logical Port settings for Workflow

.

And this is the error message

I have set the language parameter in the Logical Port from User Context to English but without any difference. The verification workflow is not showing in Sharepoint.

Anybody got some thoughts on this one?

[binson · Accepted solution]

Dear Nizaar,

SAP note: 1385461 should solve this issue. please Implement this note in your backend system and trigger a new workitem.

Regards,

Binson

[Former Member · Accepted solution]

Thanks Bison. Implemented the note and all the corresponding notes.

Now I am getting a different error message, so I say progress ?

    Message details:

    Error when calling SOAP Runtime functions: <SOAP_FAULT

    xmlns:soap="http://w

    ww.w3.org/2003/05/soap-envelope"><soap:Code><soap:Value>s

    </soap :Value></soap:Code><soap:Reason><soap:Text xml:lan

    unexpected erro r has occured on the server. Error detail

    reference not set to an instance of an

    object.</soap:Text></soap:Reason><soap:Node>http://sharep

    t.erpplus.local/_vti_bin/OBAWorkflowService.asmx</soap:No

    ><E

    rror

    xmlns="http://schemas/oba/2010/TaskflowWebService"><Error

    reference not set to an instance of an

    object.</ErrorMessage><ErrorSource

    >Microsoft.SharePoint</ErrorSource><ErrorCode></ErrorCode

    <InnerException>n

    ull</InnerException></Error></soap:Detail></SOAP_FAULT>

[binson · Accepted solution]

Dear Nizaar,

first of all, my name is Binson not Bison 

Did you check SharePoint ULS logs? You should find some error logs there..

Please attach error logs here, which would help me to check it better.

Regards,

Binson

[Former Member · Accepted solution]

Hahaha sorry Binson, was thinking of somebody else. I will get back to you with the Sharepoint logs.

The ULS Logs are zero Kb ?! I have asked my SP Dev to look into it.

In the meantime I was wondering if this root site url is correct. I saw it in the functional trace:

http://sharepoint.erpplus.local/Tasks

It correspondence with the entry in Table /IWTNG/D_USR_SUB, but shouldn't it be something else??

[binson · Accepted solution]

Dear Nizaar,

The error message you mentioned above means that the Gateway reqeust has reached SharePoint server but its failing there because of some issues. To findout the root cause we need to check SharePoint log files.

Regards,

Binson

[Former Member · Accepted solution]

Binson,

This is what the logs shows:

11/09/2012 10:20:34.64  w3wp.exe (0x06E0)                        0x0F5C Duet Enterprise                Generic                        gx7j Unexpected Couldn't add role claims to the SAML token. Exception An error was encountered while retrieving the user profile. is thrown. 

11/09/2012 10:20:34.71  w3wp.exe (0x06E0)                        0x0AC0 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (ExecuteWcfOperation:http://Microsoft.Office.Server.UserProfiles/GetProfileProperties). Execution Time=105.912622973031

As an FYI the starter services are working. Where to go from here ?

[Former Member]

Problem solved. Binson fist answer help me solved my original issue.

The second issue I had was related to the end-to-end Workflow test tool which can be found on the Duet DVD. For more info see page 14 of the Duet Enterprise

SAP Operations Guide.

Although the properties of the Workflow Page were all in order, like the GPW, possible outcomes the verification workflow didn't reach it, hence the error statement.

I mannuallly created a workflow site with the same settings and that worked.

Thanks Binson for your help.