Skip to main content

There's a problem with your Instant Messaging configuration and you can't be signed in. For assistance, please contact your helpdesk.


Issue:  Lync – OWA integration broken.
Error:  There's a problem with your Instant Messaging configuration and you can't be signed in. For assistance, please contact your helpdesk. 
 
Problem Statement 
Whenever you login Outlook Web Access you will see the error message ‘There's a problem with your instant Messaging configuration and you can't be signed in’. No buddy list will show there.
It because of either you instant messaging server name (Lync pool server) wrongly or added multiple pool server name in OWA virtual directory.
Resolution:
There are many things which you need to check and verify.
1.     CAS Server certificate, it must trusted with your Lync Server.

Command let to check certificate:

a.     Get-ExchangeCertificate | fl

It will be look like below- image02 

2.     Verify thumbprint of certificate.

You always verify the thumbprint using below command let-

a.     Get-ExchangeCertificate | fl services, thumbprint

It will look like below image03 

3.     Check and verify the trusted application pool.

Check the Owa pool and see Lync pool server name. If you see more than one Lync then you must have to check following things:-
a.      Are they have same Lync version or different?
b.     Do you have more than one Lync pool next to ‘InstantMessagingServerName’?, see the below Image shows two Lync pool server FQDN next to InstantMessagingServerName’.
c.      Are both Lync pool are trusted by certificate?
d.     If you have more than one CAS server than you must see that, Is all CAS server have same Lync pool name?
e.     Is all CAS server has same thumbprint? Etc.

In my case there are two Lync pool server showing on next to Instant Messaging Server name and both Lync Pool server are different version and like one is Lync Server 2010 pool and second are Lync Server 2013 pool.

Here you can see image where two Lync pool showing.
Command Let: Get-OwaVirtualDirectory | fl instant*, Servername
Here is the Image04.
 
4.     I have removed second Lync pool Server FQDN and verified again, now it is showing only one Lync Server pool FQDN.

Command Let: Get-OwaVirtualDirectory | fl instantmessagingservername, instantmessagingcertificatethumbprint

Here is the image05. 

5.     You must restart the IIS Services;
a.     Open the Command Prompt window and using the iisreset/noforce command to reflect the changes.
See the below screenshot Image06 

6.     I have checked after 5 minutes and now Lync integration with OWA is working fine without issue.
Able to access Lync same buddy list. See the below screenshot Image07.

 
Thank you.

Comments

  1. hi,

    How do I configure multiple IM servers ?

    ReplyDelete
  2. Hello Adithya,
    You want to configure multiple Lync SIP domain or what.
    Sorry, i did understand your question.
    Can you elaborate your query?

    Regards
    Balu Ilag [MVP]

    ReplyDelete

Post a Comment

Popular posts from this blog

Outlook Add-in for Skype meeting getting disable after restarting Outlook.

Issue: Outlook Add-in for Lync meeting getting disable after restarting Outlook.
Problem Statement: Outlook Add-ins gets install automatically when Office 2013 installs (Lync and Skype for Business clients are part of Office package). Add-ins name is Lync Meeting Scheduling Outlook Addin or Skype meeting Add-in for Microsoft Office 2013. Sometime if other add-ins conflict with Outlook add-ins then outlook add-in keep getting disabled. And user has to enable it manually after Outlook restarts. 
Resolution: By default Lync Meeting Scheduling Outlook Addin or Skype Meeting Add-in for Microsoft Office 2013 installs wit load behavior "Load at Startup". However due to some conflict users Lync or Skype add-ins load behavior get changed to loaded instead of "Load at Startup" had to re-enable Lync Meeting Add-In in each time Outlook 2013 was started as it was not set to "Load at Startup". Look at the below screenshot. Now question is how we can change load behavior …

Unable to share desktop in Skype for Business?

Unable to share desktop in Skype for Business?
You can show your entire desktop or just a program to everyone in a Skype for Business Meeting, call, or instant messaging (IM) conversation. However sometime this feature does not work and give different errors.  Error message: ·Cannot start Desktop/Application Sharing due to network issues. ·An error occurred during the screen presentation. Resolution: There are multiple thing which may affect application/desktop sharing. 1.Make sure application / desktop sharing enabled on Skype for Business / Lync Server. SfB /Lync Control Panel > Conferencing > Conferencing policy > select Global or create new policy and set enable ‘Enable application and desktop sharing’. Refer below image. 2.Make sure your Skype for Business (Lync) client is updated with latest cumulative updates. Download latest update Skype (Lync) client. 3.Update your Video and Display drivers. a.Go to Start > Control panel. b.Search for Device Manager, and then open it. c.Find V…

Unable to login to Skype for Business client?

Unable to login to Skype for Business client? In order to sign-in on Skype (Lync) you must have login credential provided to you from your organization. ·Sign-in address: bilag@orgname.com ·User name: orgname\bilag ·Password: ************
Note: Orgname.com is my SIP domain name. Here are the most common mistake people make while sign-in on Skype for Business (Lync).
1.If you have login credential however still unable to sign-in then make sure you are putting proper login credential. Below error shows when you are wrong entering your sign-in address:
2.If you are writing correct Sign-in address however getting DNS error then contact administrator/ Support team there may be a DNS resolution or configuration issue. Administrator need to verify the SfB (Lync) AutoDiscover DNS records. 3.Sometime users password may expired/ lockout: Make sure that you password is not expire and lockout. If yes then call to helpdesk and reset your password / unlock. 4.Make user to have updated Skype for Business cli…