Sign-in didn't work. This happens on one user only.
-
Monday, May 07, 2012 6:40 PM
Hello,
I am in the middle of testing Lync Server 2010 with a few users. I was able to add and enable three IT admin users for testing. Out of the three users, User A can't log into the client. User A gets an error saying "Sign-in didn't work. You didn't get signed in. It might be your sign-in address or logon credentials, so try again. If that doesn't work, contact your support team." Using the same computer, User B and User C were able to sign-in with no problems. User A tried a different computer but got the same error. I made sure User A's windows credentials are correct. User A is able to log into our Windows domain but the Lync Server doesn't recognize User A's credentials. I removed User A from the Lync Control Panel and added User A back but that didn't help.
I am running Lync Server 2010 on VMware ESX 4.1, Windows Server 2008 R2 Enterprise SP1.
Clients are using Windows 7 Pro 64bit.I am stumped. Any advice is grateful. Thanks.
Rogie
- Moved by Noya LauModerator Wednesday, May 09, 2012 7:11 AM (From:Presence and IM)
All Replies
-
Monday, May 07, 2012 7:04 PM
did you check in the Lync Control Panel to make sure visually that they are enabled in Lync?
aslo, What happens if you add user D and enabled them, does it work?
sounds like userA isn't enabled.
+Say thanks and observe basic forum courtesy:
+If this post answered your question, Mark As Answer
+If this post was helpful, Vote as Helpful
windowspbx blog: my thots/howtos
see/submit Lync suggestions here: simple and public -
Monday, May 07, 2012 7:24 PM
Matt,
Yes, User A is showing Enabled in the Control Panel. I did add User D and User D was able to log in successfully.
Rogie Olaes
-
Monday, May 07, 2012 7:44 PM
By the way, I used the Lync shell to enable my users. Now when I tried to disable User A in the Lync Control Panel, I get the following error:
Active Directory operation failed on "SERVER.DOMAIN.COM". You cannot retry this opearation: "Insufficient access to perform the operation 0000....etc.
But if i use the Lync shell to disable User A, it works.
I can use Lync Control Panel to disable User B.
Rogie O
-
Monday, May 07, 2012 7:46 PMthats fine, some users (depending on groups) need to be enabled via shell
+Say thanks and observe basic forum courtesy:
+If this post answered your question, Mark As Answer
+If this post was helpful, Vote as Helpful
windowspbx blog: my thots/howtos
see/submit Lync suggestions here: simple and public -
Tuesday, May 08, 2012 8:35 AM
Hi
Agree with Matt on the groups, Admin users can only be enabled through the PS.
The sip adress of the user that can't login, is it the same as his SMTP or have you used the first.lastname option?
I've seen strange charachters like this one ´ in the sip adress that causes strange behaviours.
in the controlpanel verify adresse and make sure that there are no strange charachters or that the user login is correct so that you haven't mixed up names if they have basicly the same name.
Sam Smith and Sam Smith, first one has a login Samsm and the second has Samsmi, seen this done this misstake myself, specially in a pilot fas in a bigger company.
/Tim
-
Tuesday, May 08, 2012 2:15 PM
Tim,
The SIP address is first inital, last name @ domain.company.com. For example, JDoe@domain.company.com. It does match his SMTP. There are no special or strange characters, just all alpha characters. His name is not common so there is no error on mixing up the names.
Thanks.
Rogie O
-
Tuesday, May 08, 2012 3:05 PMOk guys, here is the kicker. User A told me he was able to log into Lync last year when Lync Server was initially deployed. (This is before I came aboard). User A and User X tested it and the chat worked. That same year the DC server crashed and Active Directory had to be rebuilt. Since then the Lync Server had not been working.
When I came aboard the Lync Control Panal, cert, and Active Directory were not configured correctly and Lync Server gave me a bunch of errors. There were no users listed in the Lync Control Panel. I ran the wizards and was able to resolve all the issues until this one.
Today I have all my users added and enabled. I tested about 5 users and only User A so far is having the issue.Rogie O
-
Tuesday, May 08, 2012 8:36 PM
Hey
Can you try the following pls:
- Open Active directory users and computers
- Make sure "advanced Features" is selected in the view menu
- search for user A, go to his properties ==> security ==> advanced
Is the selection box ticked? (inheritable permissions)
If not, pls tick it and try it again.
Reinhart
-
Tuesday, May 08, 2012 10:33 PM
Also while your in AD check and make sure the account is not set to require a password change on next login. I realize in your case this may not be it but I saw the same behavior a few months back with a new user setup in our system.
bear jelly
-
Wednesday, May 09, 2012 7:08 AMModerator
In addition, you can try to use this troubleshooting tool to diagnose the Lync client sign-in issues. Hope helps.
Noya Lau
TechNet Community Support
-
Wednesday, May 09, 2012 4:02 PM
Hey guys,
@Noya I used the tool but I didn't see how I can input User A SIP to test his login. I know the computer can log into Lync with User B credentials but not User A. I ran the tool and didn't see any issues.
@bear jelly the account is not set to require a password change on next login.
@Reinhart i would do what you suggested but i'm afraid of messing his account. User A is my boss, lol.
I did find a fix/workaround.
I went to my Exchange server and added User A a new SIP address. Then using the Lync shell i assigned the new SIP address to User A. Presto! User A can now log in using the new SIP address.
Thanks for your input. I prob wouldn't figure this one out without joining this forum.
Rogie O
- Marked As Answer by Rogie O Wednesday, May 09, 2012 7:27 PM
.png)
