cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Nintex web service connector: Index was out of range..

Hi Guys,

I am trying to make a simple SOAP service call using the drag and drop web service connector on a simple workflow.

The SOAP service I'm trying to call is a legitimate one that comes with a major fortune 500 product and it has an exposed WSDL file.

Nintex can successfully see the WSDL file and when I click "Test Connection" I get the result "OK".

I can also see Nintex successfully populate the input parameter fields and also it knows the structure of the result that I'm expected to receive in return.

But when I click "Execute" to do a live test, the "Results" text box simply populates with "Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index"

It doesn't seem to make any difference which values I use inside the two parameters.

I can also remove the parameters completely from the SOAP request and I still get the same result.

Any ideas on this error? Is it being thrown by the Nintex SOAP parser itself? It looks like a generic .NET error coming from Nintex/SharePoint, rather than from the web service I'm calling itself.

Many thanks!

Labels: (1)
Tags (1)
0 Kudos
Reply
2 Replies
Not applicable

Re: Nintex web service connector: Index was out of range..

Also just to confirm, I can successfully call this web service outside of Nintex just using .NET WebService Studio or SoapUI etc no problems at all. It seems to be Nintex/SharePoint related.

0 Kudos
Accept as Solution Reply
Not applicable

Re: Nintex web service connector: Index was out of range..

Some more info guys, we are getting this in the SharePoint logs thrown by Nintex:

Unexpected

Action Workload exception:
System.ArgumentOutOfRangeException: Index was out of range. Must be
non-negative and less than the size of the collection.

Parameter name:
index     at
System.Collections.CollectionBase.System.Collections.IList.get_Item(Int32
index)     at
System.Xml.Serialization.XmlSchemas.get_Item(Int32
index)     at
Nintex.Workflow.Common.WSDLInspectorV1.GetParameters(ServiceDescription
serviceDescription, String messagePartName)     at
Nintex.Workflow.Common.WSDLInspectorV1..ctor(Uri webServiceUri,
NetworkCredential credential) at
Nintex.Workflow.Common.WSDLInspector.GetWSDLInspector(Uri webServiceUri,
NetworkCredential credential, WSDLInspectorVersion versionToUse)   
at phM=.uxM=.vBM=(whM= vRM=)     at
Nintex.Workflow.Activities.Adapters.NWCallWebServiceAdapter.Execu...         
d6f4fdb5-a93d-4964-8282-2a4a0989c6ed

Also:

- We can successfully call this same web service directly outside of Nintex.

- We can call another web service with Nintex and Nintex doesn't crash.

0 Kudos
Accept as Solution Reply