A Microsoft support rep provided a few methods you can try to resolve that error. Not sure what the actual issue is and a lot of users apparently reported that none of those methods worked, but that is the official response from Microsoft as far as I know.