Skip to main content

We couldn’t sign you in. Please check your sign-in info and try again.


Issue: Unable to log-in to the LRS Admin portal.

Error: We couldn’t sign you in. Please check your sign-in info and try again.
 
Problem Statement:

Configured Lync Room System Admin portal using TechNet article however unable to login using SIP enabled object. Getting error message ‘We couldn’t sign you in. Please check your sign-in info and try again.’

Resolution:

Troubleshooting step:

1.    Configured and installed LRS room web portal on Front End server.




2.    Using Active Directory object with SIP enabled and proper credential.

3.    Tried to accessing the admin portal using FQDN of the FE server and also using the localhost however still getting the below error.

                                                    i.     We couldn't sign you in. Please check your sign-in info and try again.

4.    Checked the IIS logs and we were getting below errors.

a. 2015-04-09 02:44:26 fe80::81af:590f:4038:d7f4%12 GET /lrs/ login&reason=401&target=https%3A%2F%2F%2Flrs%2F 443 - fe80::81af:590f:4038:d7f4%12 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https:///lrs/ 304 0 0 58

5.    Checked and verified the IIS setting for the LRS virtual directory all were in place, however the SSL was not checked. Later enabled the SSL (checked the SSL required on the LRS v-directory).

6.    Still getting same error. We couldn't sign you in. Please check your sign-in info and try again.

7. Later checked the IIS logs and now getting the below 401 unauthorized errors.

a. 2015-04-09 17:20:57 ::1 GET /lrs/handler - 443 - ::1 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+rv:11.0)+like+Gecko https:///lrs/?login&reason=401&target=https%3A%2F%2F%2Flrs%2F 401 0 0 1

8.    Seeing the requests are hitting the via the IPV6 hence we have disabled the IPV6 using the network setting and also via registry followed below article.


9.    Added the pool name in the config file as per the below article step no 6. (This is not required because have LRS and portal on single pool, however want to do all possible things).


Still getting same errorL.

10.Using the host file entry pointed to the POOL FQDN and tried however still getting same error and also same errors in the IIS logs. L

11.Later tried pointing to the web services FQDN using the host file entry like below.

10.0.0.7     Lync-Int-web.mydomain.com


 

This time it worked. J

12.Later have verified all possible combinations to access the portal, but only using the internal web services FQDN able to access Lync room admin portal.

IMG.

I have not found any article or information from MICROSOFT that Lync Room System Admin portal will work only using internal web service name.

 

Thank you.

Comments

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…