I need your help getting an issue to reproduce consistently, and the first person to give me verifiable repro steps will win *$500.00 (USD)!

While this problem has reared its ugly head sporadically, I can't get a consistent repro, and therefore, have little to go on in terms of debugging.  However, more and more customers are reporting this issue, and I'm quite sure we have a bug somewhere.  But this son of a beesting is quite the elusive one, and I'm turning to the OCS community at large for help!

 

Issue/Symptoms:

When attempting to shut down Windows (XP SP2, XP SP3, Vista, or Vista SP1), Microsoft Office Communicator 2007 will occasionally hang on shutdown, and the user will be prompted with the following dialog box:

 

End Program - communicator.exe

This program is not responding. To return to windows and check the status of the program click cancel. If you choose to end the program immediately, you will lose any unsaved data. To end the program click END NOW or the other option is to CANCEL.

 

 

Environment:

·         Office 2003 SP3 (or Office 2007 SP1)

·         Outlook running in Cached Mode against Exchange Server 2007

·         Office Communicator 2007 (builds 2.0.6362.0 - 2.0.6362.64)

·         Outlook is set as the Personal Information Manager in Communicator 2007

·         "Save my instant message conversations" checkbox can be either enabled or disabled

 

Notes:

This problem typically manifests itself after Outlook has been closed, yet Communicator is running (then the user shuts down Windows)

 

Contest Details:

If you can reproduce this error 100% of the time, and can furnish detailed steps (with an accompanying video demonstrating the repro) that will enable me to build out a lab topology causing this issue to reproduce consistently in-house here at Microsoft, I will personally pay the person who provided the repro steps $500 USD out of my own pocket.  The key here is so long as I'm able to reproduce it 100% of the time based of the steps you provided me, I will declare you the winner, and will gladly pay you your winnings.

*Please note that this is not a Microsoft-sponsored contest nor sanctioned event.  However, the self-inflicted price tag is worth it, as I've already burned way too many hours (both my own, and my customers) trying to get this issue to manifest itself consistently.  Oh, and Microsoft employees (that is, full-time employees, contingent staff, and their respective families) are considered ineligible for this contest.

 

UPDATE:  We finally fixed this!  I'll create a new post shortly with full details ...