The server you are trying to access is using an authentication protocol not supported by this version of Office.

Anonymous
2016-01-03T04:23:13+00:00

since windows update 1511, or since i installed the new office 2016 apps in my office 365 for small business environment, i got this message more and more frequently when my laptop starts, or tries to access the onedrive for business server using the groove.exe program. it was getting annoying. it lasts for weeks now. i tried several entries in the communities and found nothing helpful. i removed and reinstalled the office 2016 apps three times and nothing changed.

now i managed to identify where groove.exe resides (c:\program files\microsoft office\root\office16) and delete it to cap this nonsense. i know this solution does not help those poor people relying on microsoft and using good old groove under it's onedrive label to store and exchange sensitive data. i used it to share photos with my business colleagues; this no longer works but is not vital. the data once uploaded using groove are still safe on my sharepoint site and remain accessible using the browser. 

i strongly urge microsoft to re-install the authentication protocol used by office 2016 because this issue turns its loyal users away from all its other cloud offerings. moreover, i expect a statement from microsoft why quality controls was not able to prevent this issue. it is a serious violation of the office 365 contracts with microsoft.

[reposted from http://answers.microsoft.com/en-us/office/forum/office_2016-office_storage/the-server-you-are-trying-to-access-is-using-an/613fba96-c432-479a-96e0-6df51a9da4fa]

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

41 answers

Sort by: Newest
  1. Anonymous
    2016-01-12T02:22:32+00:00

    Hi everyone,

    Glad to see the activities in this thread where everyone trying to help Thomas. I have a suggestion here.

    Thomas has been linked to one of our assisted support engineer. I would advise Thomas to maintain an active conversation with the assigned engineer. The engineer is working closely with our engineering team to resolve Thomas's issue. Once we have achieve the resolution either Thomas or me will share the information here for the benefit of the community. Between now and the time when the issue is resolved, i would hold back on attempting any troubleshooting being offered on this thread especially for other community members who come across this thread.

    In case any community members who come across this thread and having the exact symptom. Please read the thread below. This is a generic error with various symptom, let us help you to identify and point you to the right direction.

    https://community.office365.com/en-us/f/154/t/426299

    Thanks,

    Chee Loon

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-01-11T17:21:40+00:00

    Hi All,

    If a password changed recently, change it back and reboot your PC until Microsoft debugs the problem it is having with authentication. (if your network admin will let you.)

    Wait it out for the fix. Same thing happened today to one of my end users. It was working, end user was at the end of his 90 day password and changed it. Waited 2 minutes for it to sync with Office online. Rebooted computer, and one drive for business was gone and gave him the unsupported server. Thinking my end user messed something up went through the accounts and checked all the products were syncing and signed in. Backed up the one drive on his local computer to another file JUST IN CASE and we needed it because when it did finally start working again, it overwrote the updated documents from the online one drive (guessing wiped and recreated to folder.)

    Found this thread and read through everything and Nate's post gave me a clue. I had my end user change is password back the one from earlier today(in active directory on the Domain controller directly) and MAGIC, everything synced back up.

    Microsoft will have to fix this in time. I have also noticed problems with the online version maintaining its sync between web based access recently.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-01-11T10:24:33+00:00

    I did so, right in the beginning - it didn't help

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-01-11T09:28:16+00:00

    one more thing that help with sync issues is deleting the following folders, closing the one drive for business tray taskbar icon and sync again.

    • onedrive business
    • onedrive for business – unsynced changes folder.

    ![](http://fud.community.services.support.microsoft.com/Fud/FileDownloadHandler.ashx?fid=7d54acab-4ba8-4cbe-9974-c093bb3eb834)

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-01-11T08:58:56+00:00

    Alex, thanks for asking

    1. Microsoft Office 365 Small Business Premium
    2. I download Office and use it locally
    3. Always OS and Office 64 Bit, x64-based
    4. Windows 10 Pro, Version 1511, OS Build 10586.36,

        a) on i7-4712HQ CPU @ 2.30GHz, installed RAM 16GB ("Laptop")

        b) on i3-4020Y CPU @ 1.50GHz, installed RAM 4GB ("Tablet")

    Both Windows and Office updates are automatically downloaded and installed, current office version is 16.0.6366.2036.

    I'm not aware of any other problem connected to Office. I installed four language packs (DEFI), US English is primary. he language mix on Windows originates from the fact that is very difficult to get hardware without pre-installed German or French OS in Switzerland and you cannot completely get rid of the original install. But this is not an issue.

    My guess is, the problem is server-based, as Groove is a very old product and probably can no longer cope with users having both work and office accounts linked to the same e-Mail address. Your fix points into that direction. Do your users have different e-Mails in the Microsoft and the Work account?

    Was this answer helpful?

    0 comments No comments