Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

fireflox is not able to load microsoft live mail

  • 1 risposta
  • 6 hanno questo problema
  • 1 visualizzazione
  • Ultima risposta di vmbc

more options

The link is through a university website. Up until a few days ago, the licrosoft live webmail was working well. then, all the icons for my mail page were all down the left side and frozen. I shut down the browser and restarted the computer. After entering my username and password, the login page came up blank. I have since removed cookies and caches - the login page has opened, but when I tried to login, the following message appeared on top of a blank page: LiveId authentication code has returned error 0x80049234, indicating that there is a temporary problem with the remote server. Please check the Application Event Log for detailed information and retry the operation later, it will likely succeed. Where do I find the 'Application Event Log'?

The link is through a university website. Up until a few days ago, the licrosoft live webmail was working well. then, all the icons for my mail page were all down the left side and frozen. I shut down the browser and restarted the computer. After entering my username and password, the login page came up blank. I have since removed cookies and caches - the login page has opened, but when I tried to login, the following message appeared on top of a blank page: LiveId authentication code has returned error 0x80049234, indicating that there is a temporary problem with the remote server. Please check the Application Event Log for detailed information and retry the operation later, it will likely succeed. Where do I find the 'Application Event Log'?

Tutte le risposte (1)

more options

ok... follow-up: seems the problem has resolved itself!