Getting 2400 error in outlook application

Anonymous
2023-04-11T09:25:43+00:00

Hi,

Something went wrong [2400] error in outlook application. Web outlook is working fine.

Tried outlook repair, reinstallation, new profile creation and cleared password from device credential manager still issue persist. Seems like Microsoft issue. Screenshot attached

Please share any troubleshooting steps for permanent fix

Thanks

Anand

Outlook | Windows | Classic Outlook for Windows | For home

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

91 answers

Sort by: Newest
  1. Anonymous
    2023-05-15T06:36:04+00:00

    I have the same problem again since 12 Mai. it was fixed with an update, but now is back again.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-05-12T21:15:01+00:00

    It's baaa-aaack. No emails sent or received through my Outlook account on my PC again after another update. How do they manage to do this to themselves? And is the only "fix" to wait for another update?!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-05-12T06:45:53+00:00

    Buenos días:

    En mi caso aparecio el error al configurar una nueva cuenta de correo en el outlook, esta cuenta necesitaba una comprobación para autenticación, eliminé la cuenta, realicé la comprobación a través de la web y al configurarla de nuevo ya no aparecía el error.

    Saludos.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-05-03T07:23:55+00:00

    I am getting the same error all the time, only in Outlook, when sending ad receiving mails

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-05-03T00:19:14+00:00

    The only reason MS fixed it so quickly was because I did what I NEVER do - a RE&RE.... 🤣🤣🤣🤣

    Now - had I ignored it , the fix would have taken ages -- always the way..... :-)

    Was this answer helpful?

    0 comments No comments