Home > Microsoft, Microsoft Lync > Microsoft Lync 2010 – Cannot sign in because the server version is incompatible

Microsoft Lync 2010 – Cannot sign in because the server version is incompatible

Today I decided to change my current OCS client to the new Microsoft Lync 2010 client. Knowing that we currently use Office Communicator Server (OCS), I knew I would run into compatibility issues. Note: Before I carry on, I will have to give credit to a fellow colleague of mine, Ryan Crawcour for pointing me in the right direction for this fix.

Well sure enough, I was presented with the following error:

Lync2010Error1

Entered my Sign-in address and clicked Sign In

Lync2010Error

 

Cannot sign in because the server version is incompatible with Microsoft Lync 2010. Contact your support team with this information.

To Fix:

You will need to add a Registry Key to tell the Microsoft Lync 2010 client to ignore the server compatibility check. To do this, follow the steps below.

  1. Run Regedit (Open command prompt, type Regedit)
  2. Navigate to HKEY_CURRENT_USER > Software > Policies > Microsoft > Communicator
  3. Right-Click, Select New > DWORD (32-bit) Value
  4. Enter Name as DisableServerCheck
  5. Right-Click on the new Registry key you just created and select Modify
  6. Enter Value data of 1 (Base = Hexadecimal)
  7. Click OK

Now when you attempt to sign in again you should be greeted with success!

Lync2010Success

 

Enjoy!

Greg Olsen
Yellow Duck Guy

Advertisements
Categories: Microsoft, Microsoft Lync
  1. July 18, 2011 at 10:55 pm

    Dude I just tried this with out success. I am running Windows 7 64 bit. It did not have the location: HKEY_CURRENT_USER > Software > Policies > Microsoft > Communicator it had everthing up to HKEY_CURRENT_USER > Software > Policies > Microsoft

    • July 18, 2011 at 11:23 pm

      Did you try creating the Communicator Sub-Key in the Registry? I did create mine on Windows Server 2008 R2 Enterprise OS x64, so not sure if there is a difference. I haven’t tested on Windows 7 x64 yet. Try creating the key as mentioned and let me know how you get on.
      Greg.

    • July 18, 2011 at 11:27 pm

      The installer I used was: en_lync_2010_x64_598497.exe

  2. July 18, 2011 at 11:37 pm

    Yep I created the key in every location that looked simular to the one you specified, still not luck. I am using verion 4.0.7577.280 (LyncSetup.exe)

  3. July 24, 2011 at 12:53 am

    This solution working fine with Windows 7 32 bit os.

  4. dixxie
    July 27, 2011 at 1:29 am

    Hi
    I created the DWORD in HKEY_LOCAL_MACHINE > Software > Policies > Microsoft > Communicator an it works fine. I’m running oldschool WinXP Pro 32 bit and MSOffice 2010.
    Dixxie

  5. darren
    July 28, 2011 at 6:59 am

    i already have that version yet no joy – also tried creating the DWORD (64-bit) value just incase – still no joy ….

  6. darren
    July 28, 2011 at 7:03 am

    ignore last post – I had missed the key policies – creator communicato under this and now working – thanks !

  7. Seyed
    August 5, 2011 at 2:30 am

    Was it required for If we have lync Server configured also?.

    • August 5, 2011 at 8:11 pm

      If you have a Lync Server already – then no. This blog post is only for people with Office Communicator Server as the server and using the Lync Client. These two are not supported together, but this blog post explains how to get them talking together.

      Thanks for reading and the question – happy to answer.
      Greg.

  8. August 9, 2011 at 5:47 am

    sweet one. thanks.

  9. September 15, 2011 at 5:34 am

    Hi
    I created the DWORD in HKEY_LOCAL_MACHINE > Software > Policies > Microsoft > Communicator an it works fine. I am on 64 bit windows 7 and I created 32 bit dword. thanks for the post

  10. sarah
    November 10, 2011 at 4:57 am

    woohoo!

  11. surendra hode
    December 3, 2011 at 12:47 am

    as per you suggetion i changed value 0 to 1 then it’s working fine

    thanks:-surendra hode

  12. mayyor
    December 6, 2011 at 6:19 pm

    followed all the instructions but i still have the same error. also tried under HKEY_LOCAL_MACHINE but still a no go.

  13. Shah
    December 14, 2011 at 6:00 pm

    Hi Friends,

    I got same problem with my client use Windoss 7 and 32 bit. I try Navigate to HKEY_CURRENT_USER > Software > Policies > Microsoft > Communicator but i cannot see the communicator folder..so how can i handle this one? anybody help

  14. Shah
    December 14, 2011 at 6:02 pm

    Hi Friends,

    I got same problem with my client use Windows 7 and 32 bit. I try Navigate to HKEY_CURRENT_USER > Software > Policies > Microsoft > Communicator but i cannot see the communicator folder..so how can i handle this one? anybody help

  15. Billy Andrew Sy
    December 21, 2011 at 3:31 pm

    thank you so much for this tip! 🙂

  16. Jorge
    December 27, 2011 at 1:19 pm

    Hello All,

    It was useful and it worked like a charm. And indeed, in my case I have W7 users and none of them have created the key as described; so after I created it and login… PRESTO!!! they were able to login right away.

    Thanks again and Merry Christmas and Happy New Year!!!:)

  17. Dipan
    December 29, 2011 at 10:10 am

    The registry key is under HKEY_LOCAL_MACHINE, not CURRENT USER for Win7.

  18. Vijay
    January 31, 2012 at 12:50 pm

    My communicator 2007 R2 is not working after performing this registry update. Please help.

    Steps followed:
    1. uninstalled Communicator 2007 R2.
    2. Installed Lync 180 days 32 bit trail version.
    3. Updated the registry to avoid this Lync login issue. After this registry update, Lync worked perfectly.
    4. Unistalled Lync
    5. Installed Communicator 2007 R2.
    6. Tried to login and it’s crashing. Typical Win7 message – (communicator 2007 has stopped working)

    thanks,
    Vijay

  19. Prasad Panthangi
    March 29, 2012 at 3:15 am

    Thank you very much!! It helped me!!

  20. Rachit Rastogi
    April 7, 2012 at 8:55 am

    awesome Bro…it worked in first instance

  21. ARiel
    June 9, 2012 at 12:37 am

    Thanks Bro!!! work correctly.. 🙂

    Best regards

  22. dan
    June 28, 2012 at 12:04 am

    thanks it helped me too
    now how do i do the same for my macbook???

  23. Arulappan
    July 18, 2012 at 10:38 pm

    Thanks you..!! it worked for me on Win 7 64bit..I created the folder “Communicator” under the registry path HKEY_CURRENT_USER > Software > Policies > Microsoft > Communicator.

  24. roca
    August 1, 2012 at 8:20 am

    dude, how I can perform this on a mac. thanks

    • August 5, 2012 at 7:44 pm

      I don’t work with macs these days, therefore I cannot help you in this area – apologies. Maybe have a search around to see if anyone else has done this.
      Greg.

  25. August 3, 2012 at 10:16 pm

    MS Office Lync 2013 preview work fine with OCS2007R2! This dword DisableServerCheck =1 is need to be added to the “HKLM\SOFTWARE\Policies\Microsoft\Office\15.0\lync”. Create this folder, if not found …

    • August 9, 2012 at 11:51 am

      I have tried “hacking” the registry to get Lync 2013 Preview to go as well with OCS server but with no luck so far. I get the error: Cannot sign in because the server is temporarily unavailable. If the problem continues, please contact your support team. Any ideas?? Greg.

      • user
        February 27, 2013 at 9:17 am

        Spot on! Thank you.

    • Harry
      September 3, 2012 at 9:48 pm

      worked like a charm. thanks.

    • Coco
      October 26, 2012 at 8:58 am

      NICE!!! I was looking for that… thank you sir.

  26. rho
    August 23, 2012 at 8:55 am

    The registry hacked worked for me but I don’t see the PRESENCE for another coworker of mine. Is it because my login sip Bob@companylongname.com versus that my default email address is Bob@company.com?

  27. Haresh
    August 27, 2012 at 8:14 pm

    Hey guys this works like a charm. thanks for the help. Just one hint, if you dont have folder Communicator under HKEY_CURRENT_USER > Software > Policies > Microsoft > then just create one and do as Greg has mentioned

  28. Toppy
    September 4, 2012 at 12:24 am

    thanks, this helped, created the folder communicator first before the above mentioned instructions.

  29. monstercupcake
    September 6, 2012 at 5:29 am

    Make sure you’re adding the “DisableServerCheck” to HKEY_CURRENT_USER > Software > Policies >Microsoft > Communicator and NOT HKEY_CURRENT_USER> Software> Microsoft > Communicator.

    “Policies” is the KEY.

    Issue resolved after adjusting this.

    Thanks!

  30. Surendar R S
    September 25, 2012 at 5:39 pm

    Thanks all you guys .i also gave a try and its working fine 🙂

  31. October 12, 2012 at 4:49 am

    I am trying to get Lync2010 client to talk to Lync2013 preview. I added that key and dword value, end tasked communicator.exe and restarted it, but it still gives me that same error.

    I do not want to download the entire office 2013 preview.

    • October 12, 2012 at 4:55 pm

      I tried the same process without luck. If you get it working, lets us know. You may have to move to the Lync 2013 client as well for this to work.

  32. MicaH_Z
    October 17, 2012 at 3:26 am

    If you have installed a 32-bit Lync 2013 preview client on a 64-bit windows OS the proper location for the DisableServerCheck is HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\Office\15.0\lync.

    • Lync User
      November 27, 2012 at 3:23 pm

      Thank you. It worked, Lync 2013, Win7 64 bit. as per the above comment. If you dont find Communicator or office or lync folder, Create Key ‘Office\15.0\lync’ under HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft. & create this flag.

  33. VidhyaSagar
    November 5, 2012 at 3:58 am

    Дмитрий Шмаков :
    MS Office Lync 2013 preview work fine with OCS2007R2! This dword DisableServerCheck =1 is need to be added to the “HKLM\SOFTWARE\Policies\Microsoft\Office\15.0\lync”. Create this folder, if not found …

    Thank You!! this worked fine for me in Lync 2013

  34. koush
    November 9, 2012 at 8:13 am

    Wow!!! it worked !!!! Thanks a lot 🙂

    • November 9, 2012 at 8:51 pm

      @koush – not worries. Happy to help. Thanks for reading the post.

  35. November 26, 2012 at 7:22 pm

    How to log in microsoft lync?

  36. Jaime
    January 16, 2013 at 12:18 pm

    Hello there, i had created a DWORD on W7 64bits an works!!! thx a lot!

  37. February 13, 2013 at 8:22 am

    Thank you en tabarnak!
    It worked like a charm !!!

  38. Alexboom
    February 26, 2013 at 5:11 am

    For those with problems still after the registry hack…check this
    http://support.microsoft.com/kb/2701664
    It worked for me on win7x64, with x64 client

  39. Ponni
    March 1, 2013 at 4:50 pm

    It is perfect.. yeap it worked.. 🙂 thanks

  40. Krister H
    March 7, 2013 at 11:27 pm

    Hi!
    After testing lync 2013 client and OCS server 2007 and get it working with hack I cant go back and use the OCS 2007 client. any tip to reverse?

    regards
    Krister

    • March 8, 2013 at 9:44 am

      You will need to reverse out the changes made to put it back in the original state.

      • Krister H
        March 8, 2013 at 7:30 pm

        Tried that and also tried a other pc with fresh ocs installation on it but it wont start, seems that something has happen on the ocs 2007 server but I cant find out what

  41. Manikandan Sethuraju
    March 9, 2013 at 3:47 am

    Hi,
    Please guide me, I did all the things which are mentioned above.
    I am using Windows7 32 bit system & Lync2010. When i try to connect by using my credential it’s not connecting. No error message will be shown, simply it’s loading like “Contacting server and signing in..”. But when i try to connect by using another login credential means it’s working fine.

    Note : Suppose i try to connect lync by using my credential to another system, it’s working fine.

  42. Driz
    July 27, 2013 at 2:55 am

    Guys – This also worked for Windows 8 and Lync 2010 64bit.

    Same as above, Make sure you’re adding the “DisableServerCheck” to HKEY_CURRENT_USER > Software > Policies >Microsoft > Communicator and NOT HKEY_CURRENT_USER> Software> Microsoft > Communicator.
    “Policies” is the KEY. <—-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Just add a New Folder in Microsoft call "Communicator" if there is not a folder here. Then add the Dword “DisableServerCheck” and modify the 0 to a 1 then….

    Communicate away!!!

  43. August 1, 2013 at 12:57 am

    hi sir,

    we are using OCS, but i have a problem with one of our XP machine. it’s always logging in, we believe that there’s an incompatible application in the machine that’s causing this. appreciate your help.

  44. August 6, 2013 at 2:03 am

    Hello, I’m using 1 Microsoft 2010 windows 7 with 64 bit. I’m encounter same problem with that. Hope you can help me with this.

  45. Michael
    August 30, 2013 at 9:32 am

    Do you have Lyn2010 with 32bit?

  46. Bhabani
    November 19, 2013 at 6:48 am

    Thanks Greg. You saved my day today. I have been scratching my head.

  47. Vinay
    August 23, 2014 at 4:57 am

    The solution worked for me with 32 bit DWORD. Thanks and cheers!!!

  48. Carlos Perez
    March 10, 2015 at 10:56 am

    Only:Lync 2010 Hotfix KB 2953593 (32 bit) do the trick for me!

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: