K2 can't submit to the SharePoint Library if the DNS name is stated in its UDC's

CassimY — Tue, 31 Jan 2012 11:48:38 GMT

Hi,

We have SharePoint 2010 installed 3 tier - web, app and DB
We have K2 installed 2 tier - app and DB
We have InfoPath Forms Services installed
We're using InfoPath 2010
We're using DNS names

I created a browser enabled form and published it to a SharePoint site. I then created a K2 process on the form and deployed the process to the SharePoint site. When the user tries to submit the form, K2 complains that there was an error accessing a data source.

We had K2 come in to try and trouble shoot the issue. We thought our installation, setup, configuration, etc. was incorrect but they checked everything and confirmed that all was correct. They spent 2 days with us and could not find the problem.

A colleague then discovered the problem by mistake:

When one creates a K2 process on a browser enabled form, K2 publishes specific UDC's to the site.
When the user submits the form, those UDC's are accessed.
The site url is stated in the UDC.
Because we're using DNS names, K2 stated the DNS name in the UDC, and that's perfectly understandable and correct.
But when we manually edit the UDC and change the DNS name to the direct path (i.e. server name, port number, etc.), the form submits successfully.

So we've isolated the problem - when the form is submitted, K2 cannot access the site using the DNS, but it can using the direct path. And this baffles us because when we create and deploy the K2 process, we use the DNS name, and the deployment succeeds.

Our AD guys investigated and can't find anything incorrect in the DNS name and mapping to the direct path. Our SharePoint team are at a loss. And K2 have no answers. Has anyone out there experieneced the same problem? Or have any propositions?

Thanx

Yusuf

General

K2 can't submit to the SharePoint Library if the DNS name is stated in its UDC's