We are getting the exact same problem - except that the person who built the InfoPath forms and did the initial integration is the only one who can open, edit the forms / processes, and deploy the processes.

All forms and processes are stored on a mapped mnnetwork drive, and the mappings are the same for all of us (m:).

We have tried re-running the K2 Visual Studio configuration manager as was suggested by Mike Talley, and have re-run the InfoPath Integration wizard as well - neither of these have resolved the issue.

My biggest problem with this is that the InfoPath developer is rolling off onto other projects, and we need to distribute out the ability to update and deploy these processes and forms to other resources.

Any assistance would be greatly appreciated!

Paul

Paul,

Again, have not seen this problem before.  You mentioned you have a problem getting to the files because they are on a share somewhere with no access.  Hopefully your network admin can help you with that.

On another note, you can still get access to all the code if it import.  To get the InfoPath form, if the form is published to SharePoint simply go to the form library and download the .xsn.  To get the process code, go the K2 workspace, go console manager, go to the processes, open the versions node and download all the process code.  To get SmartObject, in visual studio go to the K2 Object Browser, right click a SmartObject and select save local.  This is because all K2 code is declarative and not compiled.

Now if you have any .Net custom libraries being used by your processes I cannot help you there.

Jason

Thanks japergis, it did it for me.