Sunday, January 16, 2011

OCS 2007 R2 users having problems viewing Microsoft Lync Server 2010 users’ presence? Check for Event ID: 11 warnings in your communicator logs.

For those who have come across my previous blog posts about Lync Server 2010 users haven’t problems viewing OCS 2007 R2 users’ presence: http://terenceluk.blogspot.com/2011/01/presence-issues-between-microsoft-lync.html, the problem in this post is the exact reverse where:

OCS 2007 User –> viewing –> Lync Server 2010 User = Presence Unknown

Lync Server 2010 User –> viewing –> OCS 2007 User = Presence is working

Just as I have noted in my other post, note that presence issues can be caused by a vast amount of reasons and this blog post only points of the many reasons so if it doesn’t apply to your situation, move on and continue searching because you’ll find many more reasons as you plow through your Google/BING results.

Problem

After successfully installing Lync Server 2010 in your environment and merging your legacy R2 topology, you notice that your OCS 2007 R2 users are not able to see presence information for your Lync Server 2010 users.  You also notice that you can have your Lync Server 2010 user initiate a IM chat with an OCS 2007 R2 user but can’t do it the other way around.

image

After turning on logging for your Office Communicator client as shown here:

image

… you notice that there are event ID: 11 warnings being logged in the application logs for your desktop/laptop:

A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f8). More information is contained in the following technical data:
RequestUri:   sip:lync@domain.com
From:         sip:tluk@domain.com;tag=42f6ddba6a
To:           sip:lync@domain.com;tag=50FB3633A1D1164E9F2082AB912D2410
Call-ID:      ed0ec3bf6e2f424a85eeae2c1693bf7c
Content-type: application/sdp;call-type=im

v=0
o=- 0 0 IN IP4 172.16.1.120
s=session
c=IN IP4 172.16.1.120
t=0 0
m=message 5060 sip null
a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/ms-imdn+xml text/x-msmsgsinvite

Response Data:

504  Server time-out
ms-diagnostics:  1014;reason="Unable to resolve DNS A record";source="ocs02.domain.com";LookupFQDN="ocspool3"

Resolution:
If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

image

Solution

What tipped me off was the event ID: 11 warning that was logged by the Office Communicator Client because while carefully reading through the information, I noticed the following highlighted in RED:

A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f8). More information is contained in the following technical data:
RequestUri:   sip:lync@domain.com
From:         sip:tluk@domain.com;tag=42f6ddba6a
To:           sip:lync@domain.com;tag=50FB3633A1D1164E9F2082AB912D2410
Call-ID:      ed0ec3bf6e2f424a85eeae2c1693bf7c
Content-type: application/sdp;call-type=im

v=0
o=- 0 0 IN IP4 172.16.1.120
s=session
c=IN IP4 172.16.1.120
t=0 0
m=message 5060 sip null
a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/ms-imdn+xml text/x-msmsgsinvite

Response Data:

504  Server time-out
ms-diagnostics:  1014;reason="Unable to resolve DNS A record";source="ocs02.domain.com";LookupFQDN="ocspool3"

While ocspool3 was indeed the name of the enterprise pool for the new Lync Server 2010 environment that was built, the domain suffix was missing.  Logically thinking about the problem, it would make sense that if the OCS 2007 R2 front-end server wasn’t able to correctly resolve the the FQDN of the Lync Server 2010 pool, messages initiated by the OCS 2007 R2 pool wouldn’t be able to get delivered properly.  Unfortunately, changing the FQDN of the Lync Server 2010 pool wasn’t allowed as shown in the following screenshot:

image

So what did I have to do?  I ended up searching far and wide for documentation on how to properly uninstall the Lync Server 2010 pool but was unable to find clear documentation on how to do so.  After trading messages with our Microsoft Partner Forums engineer, I finally got enough to perform an uninstall without manually editing Active Directory with adsiedit.  I’ll write another post about that at a later time but in the meantime, the way to resolve it is to completely remove this pool and redeploy it with the full FQDN entered in. 

image

Once was completed, this presence issue was resolved.

No comments: