Can't connect my Microsoft account to my domain account

When I log in to my domain account on Windows 8.1 Pro 64-bit and on multiple machines, I get the message:

We're sorry, but something went wrong.  Your Microsoft account wasn't connected to this domain account.

Code: 0x8004804e

I have connected my Microsoft account to my domain in the past without problems, but can't get it to work now on two different computers with multiple users.

Thanks

Greg

January 11th, 2015 5:31am

Do this work in any workstation?

Probably, the group policy settings don't allow you to connect a Microsoft account.

http://windows.microsoft.com/en-us/windows-8/connect-microsoft-domain-account

Free Windows Admin Tool Kit Click here and download it now
January 11th, 2015 11:39am

Hi Greg,

From your description, you make the domain account connect to Microsoft account. However, you will get the following massage,

We're sorry, but something went wrong.  Your Microsoft account wasn't connected to this domain account.

Code: 0x8004804e

There is workaround, you can connect the Microsoft account again.

As for the solution, I researched our case database just now and find that the case which has the same error 0x8004804e is very rare. Could you give me more time for further investigation? I will update you on the case troubleshooting tomorrow.  Thanks for your understanding and cooperation.

January 14th, 2015 12:39pm

Hi Greg,

Hare are things going? Based on my further investigation, it may cause by network. It is the best method to analysis this issue that collect network trace during the issue reproduce. For Microsoft, there is network monitor tool. Here are steps,

1. Download Microsoft Network Monitor Tool from the following link and install it on the problematic machines

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f

 

2. Start Network Monitor at "Start" ->"Program"-> "Microsoft Network Monitor 3.4" -> "Microsoft Network Monitor 3.4"

3. On the left-panel, check the "LAN connection" and uncheck the other unnecessary connections

 

4. Click "Tools", click "Options", switch to the "Capture" tap, and set the "Temporary capture file size (MB)" to 200

 

5. please run the command line below in the cmd.exe with admin permission to clear the DNS cache and NetBIOS cache

 

ipconfig /flushdns

nbtstat RR

 

6. Click "New Capture", click "Start" on the Capture menu

 

7. Try to reproduce this issu

 

8. When get the error, click "Stop" on the Capture menu, and click "File"->"Save as" to save the captured files.

 

Please upload the one drive if you want to we help you analysis.

Thank you.

Free Windows Admin Tool Kit Click here and download it now
January 16th, 2015 12:48pm

Thank you.  I'll give this a try over the weekend and send you the results.
January 17th, 2015 1:14am

It does, but only on workstations that were setup a couple of months ago.  I'll look into the group policy setting.  I don't think that policy is defined, but I'll double check the "Block Microsoft accounts" policy setting.
Free Windows Admin Tool Kit Click here and download it now
January 17th, 2015 1:20am

@Bryan, thank you for your help.  Here is a public link to the capture of network traffic.

https://onedrive.live.com/redir?resid=806570FBB48D3918%21762

Thank you

Greg

January 17th, 2015 10:11pm

Hi Greg,

Thank you so much your cooperation.

Unfortunately, we cannot get any available information from the network tracing. To do further investigation, I learnt the issue may be cause by the file or registry that store the information about Microsoft account is corrupt. So we can reconnect the Microsoft account again to bypass this issue.

As for the root cause, I have done a lot of research recently, however the resource is limited. I will continue to perform bottom layer analysis of this mechanism. It will cost time but I will follow it as soon as I find any useful clue.

Thank you for your time.

Free Windows Admin Tool Kit Click here and download it now
January 21st, 2015 11:09am

I now have this problem as well. Is there an answer yet?
February 16th, 2015 12:57am

Unfortunately, I was never able to find a solution.  Good luck guys...
March 4th, 2015 3:18pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics