ex50_index_queue 6 stuck messages

what version/build you running?

I had the same issue. patch from tech support resolved it.

I may not have the description right, but when a message enters this queue and it has a problem with assigning ownership, it will get stuck in the queue.

I had over 100 messages before I called in.

Hello,

Here is my understaning of the issue:

When EmailXtract Arcihve and shortcut jobs run they can bring ownership updates to EmailXtender server. These updates usually comes to EX because a email is found in someones mailbox who is not owner of the message so far, one scenario I could think of is moving messages form someone's PST file to your mailbox because you do the same job and needs the same emails. Because emails where not sent to you but they are in your mailbox you need to be added as owner of the messages so that you can search for these mails.

Due to any reason in past if a message fails to be archived properly and volume information in SQL do not get assigned to the message ID, when updates will go to index queue they need to have volume information available to do the job. In past what was happening was that after 60 tries EX will dispose off updates which do not happen with last three releases of EX.

Here updates will stay in the index queue till they gets processed or till someone takes then out manually. Here are usually the three ways to do it:

1. Speak to support and ask them about a SDR open with engineering for this issue. Once the resolution will be provided then these updates will be processed.

2. Install a hotfix available that will try 60 times and take out updates if those could not be applied to the messages.

3. Work with support to take data out of MSMQ index queue till the resolution for the SDR (as per 1. i mentioned above) is found and then process exported data back once the resolution is in place.

Usually having this data in index queue do not cause any problem for new messages coming in the index queue because those will be getting processed without problem, the only worry is that as many times you will run emailXtract jobs data will accumulate in index queue because same messages without volumes could be found in other mailboxes. If the number of messages in index queue will be a very large number (about 50K) then I would suggest approach 3 I mentioned above.

Still I would suggest working with support on it and see what they has to has after they check your environment and data in the index queue.

Hope this clarifies few things.

Regards,
Rajan Katwal