Skip to main content


 

Symptoms


No emails to Authorisers
 

Diagnoses


When you attempt to migrate a form over from 4.6.11 server to another server (4.7) with a process and smartobjects + data.

When you choose to run the form and submit data you get the following error:

Message: Object reference not set to an instance of an object. ServiceName: ADService2 ServiceGuid: 83ac8762-cd63-4e86-8ac8-964e8729b735 InnerExceptionMessage:

The event viewer says:

28083 DestinationRule: Message: Object reference not set to an instance of an object. ServiceName: ADService2 ServiceGuid: 83ac8763-ab63-4f86-8bc8-9bde8729b735 InnerExceptionMessage:

InnerException: Exception has been thrown by the target of an invocation.
InnerException: An unexpected error has occured while trying to resolve a value for Resolver ID 106C5886-18B1-4c09-BEB3-6F7342669D18.
InnerException: An unexpected error has occured while trying to resolve a value for Resolver ID 106C5886-18B1-4c09-BEB3-6F7342669D18.
InnerException: An unexpected error has occured while trying to resolve a value for Resolver ID 106C5886-18B1-4c09-BEB3-6F7342669D18.
InnerException: An unexpected error has occured while trying to resolve a value for Resolver ID 59F5D9BC-3B14-45ca-9C94-6FCB3C4D862F.
InnerException: Message: Object reference not set to an instance of an object. ServiceName: ADService2 ServiceGuid: 83ac8763-ab63-4f86-8bc8-9bde8729b735 InnerExceptionMessage:

The form is tied to a workflow that is supposed to send a request to be authorised, but this does not seem to work. The workflow destination is being pulled back from the AD User smart object with the method of "ADUser.GetUsersByGroup.Name filters are based on the department groups to select users within a particular department.

With this in mind this fails, is their a reason why this is happening ?


 

Resolution

This is a bug and there is a coldfix that will need to be requested via K2 support which will need to be applied for the following workarounds for the issues below:

The workaround is the following:

Issue 1

The mapping should not be only the token, but the actual value to be used. For example repro step:
"...you should select a group name, such as Finance.Name to be the value, then click ok."

Issue 2

Type the Filter name in instead of using the property.
This is a bug and we have logged a bug for this - to be fixed in the product in a later version.
 




 
Be the first to reply!

Reply