Communicator Error ID:5001 “The following message was not delivered”

I have recently encountered this error in an OCS 2007 deployment with a mix of Communicator 2007 and Communicator 2005 clients. The problem was specifically that the Communicator 2005 client did not have the latest hotfix installed: http://support.microsoft.com/kb/949280/ (released December 19, 2008).  The Communicator 2007 client had the latest hotfix, but not the Communicator 2005 client.

 

Another possibility for this error when it involves two internal IM clients and an OCS 2007 server, is an OCS 2007 server issue with the IM filter application not being able to read from WMI. The presence of a specific event in the server event log will confirm that this is the problem. The event-id specifics and resolution is documented in Microsoft Knowledge Base article 943392: http://support.microsoft.com/kb/943392.

 

If an internal user is getting this error while attempting to communicate to an Public IM recipient, it is likely a problem with your Edge server, the Edge PIC configuration, the remote PIC gateway, or the format of the IM address being used to try and reach the recipient. The following links document the most common problems:

·         Changes to Yahoo! IM federation may affect users of Office Communications Server 2007 and Live Communications Server 2005

·         IM fails to send to Corporate AIM

 

Read Full Post »

The OCS 2007 Automatic Sign-In Troubleshooting Tool V1.0

Debugging Office Communicator 2007 automatic sign-in issues can be frustrating because of the different DNS records and their associated formats that are used to locate the home server or pool to attempt the sign-in. To simplify the debugging process, I wrote a small Windows tool that can be downloaded and run on the client.

The OCS Automatic Sign-In Troubleshooter programmatically performs DNS lookup’s for all the DNS records that the Office Communicator 2007 client uses to locate an OCS 2007 server, and displays the results. The tool performs the DNS queries as the client would (e.g. using the client DNS settings and cache), so that the results will reflect what Office Communicator will use. If people find the tool useful, I will add more functionality.

Additional Details & Download: http://www.insideocs.com/tools/MOCLogin.htm

Screenshot:

For more information about the Office Communicator Automatic Sign-in process and how to troubleshoot it, see:

• DNS Records and Office Communicator Automatic Client Sign-In
• Automatic Office Communicator Sign-In (Part 1 – The Correct DNS Service Location (SRV) Record)
• Automatic Office Communicator Sign-In (Part 2 – ensuring the correct Subject Name on the Certificate)
• Automatic Office Communicator Sign-In (Part 3 – ensuring the client trusts the issuing Certificate Authority)

Read Full Post »