none
ERROR with BizTalk Monitor Job (Biz2010) - A cursor with the name 'MsgboxDB_Cursor' already exists RRS feed

  • General discussion

  • Error - A cursor with the name 'MsgboxDB_Cursor' already exists

    I got following error multiple times with BizTalk Monitor job in past. Last week I again faced it post BizTalk 2010 CU8 installation.

    Root Cause - The SP code is not deallocating the cursor and in the next SP being called, a cursor with the same name is being created.

    Solution - To fix this issue, we will need to modify the SP and add the deallocate statement.

    This appears to be a safe change (as it does not affect the logic of the SP).


    Pankaj Negi

    Monday, May 30, 2016 11:35 AM

All replies

  • Hi Pankaj,

    Nice to see you on the forum. Thanks for sharing your observation, Appreciate it.

    Cheers!


    Rachit Sikroria (Microsoft Azure MVP)

    Monday, May 30, 2016 3:33 PM
    Moderator