Is this code contained in your custom dll or in a user front end aspx page?
The reason I ask is this...
If it is in your custom dll, you can not connect to a process instance to itself i.e. you can not connect to and update process instance xxxx from within process instance xxxx. The reason for this is that K2.net Server locks the record for this process instance id while it is busy actioning the item. K2.net Server locks this record until the Server Event is completed and then you are trying to access the same process instance through another thread.
I would suggest moving the update code back into K2.net Studio (without the K2ROM stuff) OR making use of a synchronous server event. If you make use of a synchronous server event, you'll have to save the serial number of the event to some place you can pick it up from and action the item. Please refer to the Help file for and explanation of the Synchronous Server Event.
HTH,
Ockert
Updating Process Instance with K2ROM.dll hangs
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
