How to resolve item stuck in the Destination Queue and do not log into the Worklist.

Last post 09-17-2007, 5:03 AM by Ockert. 4 replies.
Sort Posts: Previous Next
  •  09-13-2007, 10:29 AM 18610

    How to resolve item stuck in the Destination Queue and do not log into the Worklist.

    Hi,

    I am having this problem that whenever I run an item in K2 it always stuck up in the "Destination Queue" and not logging in the Worklist. As a workaround to this I always redirect the item in the K2 Service Manager to the specific queue.

    I'm using K2.net 2003 SP4.

    Also as a starter with SP4, is it safe to uninstall the SP3 package since I've already upgraded.

    Thanks,

    -ginoskie Big Smile

  •  09-14-2007, 3:53 AM 18628 in reply to 18610

    Re: How to resolve item stuck in the Destination Queue and do not log into the Worklist.

    Sorry, please elaborate, I'm not sure what you mean by 'stuck up in the Destination Queue and not logging in the Worklist'.

    Are you saying that you've now got both SP3 and SP4 on the same machine?  Should not be able to happen.  SP4 should have upgraded SP3.

    Regards,

    Ockert


    The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.
  •  09-14-2007, 10:40 AM 18649 in reply to 18628

    Re: How to resolve item stuck in the Destination Queue and do not log into the Worklist.

    Realze there is a bug in K2 SP4 in K2 Service Manager where the "Help" > "About" reports the incorrect Service Pack version (still displays SP3, not SP4 after the upgrade). You can go to the K2 "\bin\" folder and look for the K2 dll versions to confirm the SP your're running, or load K2 oin console mode and note the SP in the first couple of entries logged.

    Also, another SP4 'gotcha': please make sure the K2 Studio clients and K2 Server are running the same .Net Framework version (keep at 1.1 until you've coordinated a switch to 2.0). SP4 upgrade loves to automatically flip to 2.0 after an upgrade (SP4 was the first K2 Service Pack to support 2.0, and it finds it quite effectively during the upgrade ;-) and assumes you want the new version since its available on the machie.

     

     


    Dave
  •  09-14-2007, 12:42 PM 18652 in reply to 18628

    Re: How to resolve item stuck in the Destination Queue and do not log into the Worklist.

    Once again thanks for replying Ockert,

    What I meant with my statement 'stuck up in the Destination Queue and not logging in the Worklist' was for example there was an item logged in my process but when I looked at the Workspace Worklist the item was not there so trying to find where is it I look in the K2 Service Manager and found it in the Worklist with the Destination column value of Destination Queue which I think is working as design in K2 but once I redirected the Item to the specific Destination Queue the item will then be available in the Workspace Worklist. So everytime this happens I always redirect the item to its specific destination queue.

    Is there anything I'm missing here?

     Are you saying that you've now got both SP3 and SP4 on the same machine?  Should not be able to happen.  SP4 should have upgraded SP3.

    - What I'm trying to say here is I have just upgraded to SP4 in a SP3 server then now I would like to install K2.net in a server that K2 doesn't exist, do I still need to install all K2 SPs before the SP4 or is it safe to just install the SP4 even without the SP3,SP2.......etc.

    Thanks a lot Ockert,

    - ginoskie Smile

  •  09-17-2007, 5:03 AM 18698 in reply to 18652

    Re: How to resolve item stuck in the Destination Queue and do not log into the Worklist.

    Hi ginoskie,

    Let's start with the easy one first. SP4 is a full install which you can run on a clean system - no previous service packs required.

    Ok, so in a Client Event, you assign a worklist item to a queue called 'Approvers' for example.  When a process instance is created and the appropriate worklist item is created, you can find the item in K2.net Service Manager but not in the Workspace Worklist.  If you redirect the item to the same queue 'Approvers', the item is available in the Workspace Worklist.  Is this correct?

    If so, I would guess the problem lies in the Client Event creating the worklist item.  Look for code similar to 'K2.AddWorklistItem(...)'.  Make sure there are no leading or lagging spaces in the Queue Name passed to this method.

    HTH,

    Ockert


    The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.
View as RSS news feed in XML