"Something went wrong. Service request timed out"

Table of contents

The error message "Something went wrong. Service request timed out after 90000ms." in Microsoft Outlook typically indicates a connectivity issue preventing the application from fully loading or communicating with the server within the expected time frame.
Potential Causes & Solutions:
Network Connectivity Issues:
Check your internet connection: Ensure you have a stable and reliable internet connection.
Restart your router/modem: This can refresh your network connection.
Check proxy settings: Ensure they are correctly configured and not blocking Outlook's access.
Temporarily disable VPN/Antivirus: If using, test if these interfere with Outlook's connection.
Outlook Application Issues:
Refresh the application: As suggested by the error message, try clicking "Refresh the application".
Clear Outlook's cache: Corrupted cached data can cause issues. Close Outlook, navigate to
%localappdata%\Microsoft\Outlook
in File Explorer, and delete theCache
orRoamCache
folder (skip database files if prompted).Repair Office Installation: Go to Control Panel > Programs > Microsoft Office > Change and choose Quick Repair or Online Repair.
Open Outlook in Safe Mode: To identify if add-ins are causing the problem, run Outlook in safe mode (
outlook.exe /safe
). If it works, disable add-ins one by one until the culprit is found (File > Options > Add-Ins).Create a new Outlook Profile: This helps rule out a corrupted profile. Close Outlook, go to Control Panel > Mail > Show Profiles, and add a new profile, then set it as default.
Account or Server Related Issues:
Verify Account Settings: Ensure your email account settings (server addresses, port numbers, security settings) are correct in Outlook (File > Account Settings > Account Settings > Change).
Check for Server Issues: Visit the Office 365 Service Health Dashboard (if applicable) to see if there are any reported service outages affecting Outlook or your email provider.
Contact your email service provider or IT administrator: If the issue persists after trying the above steps, especially if it's a work/school account, contact your provider or administrator for further assistance, as it might be a server-side problem.
Subscribe to my newsletter
Read articles from Namdev Pratap directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by

Namdev Pratap
Namdev Pratap
Come along with me on a public learning journey into AWS Cloud and DevOps, designed specifically for those without a technical background. I'll be documenting each step in straightforward, easy-to-understand language to help others make a smooth transition into DevOps. Together, we'll delve into continuous integration, deployment, and automation, breaking down complex concepts into manageable, actionable insights.