k2.net 2003 and MOSS site collection

  • 5 January 2008
  • 1 reply
  • 2 views

Badge +2

We have two different types of sites setup on our MOSS server that i am testing against.  One site seems to work fine (i can browse to it through the K2 Studio InfoPath process wizard, i can upload process instance xml docs to it from InfoPath activities etc) but the other site causes problems.  The site that works has a url like this http://employee.mysite.net/workflow.  'workflow' is a subsite for the employee publishing site.  The other site looks like this http://employee.mysite.net/sites/workflow.  'sites/workflow' is a virtual directory within SharePoint (only SharePoint recognizes it, not IIS).  From K2 Studio if i try to browse to the sites/workflow area it will not come up.  I can only see doc libraries if i put the full path in the Virtual server url box and nothing in the site box.  No matter what i seem to put in my ProcessDataFields for these values can i get an InfoPath activity to work.  When the spslist.UploadDocument method is called i get the following error: 


System.Exception: There is no Web named "/sites/workflow".
   at K2Code216126.SendDocURL(ClientEventContext K2)
   at K2Code216126.Main(ClientEventContext K2)


 For clarification we are running K2.net 2003 SP4 and MOSS with the additonal components and hotfix installed.  Any ideas?  For now we are just going to use the subsite but i'd like to understand what the difference is and how to work around this if possible in case we want to setup sites in that manner in the future with MOSS.  Thanks in advance.


1 reply

Badge +7

To clarify:

On the site that doesn't work, you can hardcode the Virtual Server URL to http://employee.mysite.net/sites/workflow and leave the Site field empty, and the process works as expected?

Does this mean that you wish to make the URL dynamic, and therefore you are trying to do something like:

Virtual Server URL: http://employee.mysite.net

Site: K2.ProcessInstance.DataField["Somedatafield"].Value (where the value = sites/workflow)

Site as template: sites/workflow

That would have worked fine on SharePoint 2003 however it seems to be slightly different on MOSS.

My recommendation would be to run through the wizard using the options you want, with the Virtual Server URL hardcoded and the site field empty. Then generate code on the event and replace the hardcoded server virtual server URL with your process instance datafield containing the correct address.

Hope that helps, Richard 

Reply