Hi, NALINI

A similar error has occured, see the suggested resolution below:

The WFE servers were load-balanced. Adding a host file entry on WFE pointing to its own IP address on each of WFE seems do have done the trick

try adding the hosts entries on the WFEs so that web service calls originating on a WFE server will not need to go back out to the load balancer and lose its user context.

Attached please find K2 for SharePoint Environment Setup documentation.

Kind Regards

Julia

Hi NALINI,

This error can be caused by the Identity set on the SharePoint Web Services Root Application pool being set to Local Network. Does the Local Network have rights to access SharePoint data? The User Profile Service uses the SharePoint Web Services Root Application pool to complete the tasks. Does the current Idenitity of the Sharepoint Web Services  Root Application Pool have the correct rights? Also does the User have full control over the User Profile Service?

HTH

Regards,

Yannick

Hi, NALINI

To follow up on this post did the above suggestion help you fix the error you had while submitting a form?

Can you please update us with regards to this post.

Regards

Julia

Hi Nalini

Is this error generated when submitting InforPath form?

If this is a yes to this question then please give the following option to try.

Option 1

You turn on SharePoint logging to understand the exact error from the Application.
Please refer to the following link to enable SharePoint Logging :
http://www.k2underground.com/blogs/infrastructure_spotlight/archive/2009/01/12/troubleshooting-infopath-forms-services-errors.aspx

Option 2

Be sure that the user has been given Start rights on the process.

Option 3Updating the K2 Service Account’s SPN with the FQDN
- Created the SPNs for MS SQL Server.
PS: The ’Do not require Kerberos pre-authentication’ flag on the user’s account had to be enabled to receive accurate Kerberos errors in Event Log.