Onedrive.com Error Code 103

Anonymous
2022-01-19T14:57:31+00:00

I recently updated the password on my account, but now I am unable to access my files on OneDrive. When I sign in on the web, I get the error message "Something went wrong. Error code: 103" and the page just reloads endlessly.

Similarly, I am unable to access any files in the OneDrive app for iPhone. When trying to open a file, it never downloads and eventually the error message is displayed "The file can't be displayed. Sorry, there was a problem opening the viewer."

Microsoft 365 and Office | OneDrive | For home | Other

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

51 answers

Sort by: Most helpful
  1. Anonymous
    2022-10-11T01:57:10+00:00

    How do I get to download files my onedrive when every thing I click on in there creates a 103 error loop?

    I was getting messages that it was getting full (1TB) but now it wont let me download files or delete files

    I dont know code or any "fancy" stuff...just an old woman who needs help

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-10-10T20:37:04+00:00

    What was the question?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-10-10T20:16:26+00:00

    yes, Microsoft Edge is the only browser that worked!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-09-04T08:01:28+00:00

    I emptied the cache storage then all was fine.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-09-04T02:34:33+00:00

    Thank you - this worked for me. When I logged in via Edge it first tried to sign me in using a couple of my other MS accounts (residual cookies I guess) and I had to manually type the correct email address to log in with. Once successfully logged in, I emptied my recycle bin and went back to FF and refreshed. The error was gone.

    I think this must be the result of some weird cookie conflict in the browser.

    Was this answer helpful?

    0 comments No comments