Outlook.com Error 500 – TooManyObjectsOpenedException After Account Compromise – Mailbox Inaccessible

Question

Outlook.com Error 500 – TooManyObjectsOpenedException After Account Compromise – Mailbox Inaccessible

Zen 0

Hello Microsoft Support and Community,

I urgently need assistance with my personal Outlook.com mailbox.

On October 18, 2026, my Microsoft account experienced an unauthorized successful sign-in originating from an IP address geolocated to Brazil.

After discovering this, I immediately secured the account by:

Resetting my Microsoft account password.

Enabling two-step verification with Microsoft Authenticator.

Signing out of all devices and sessions.

Removing existing app passwords.

Reviewing mailbox rules, blocked senders, and forwarding settings.

I was initially able to access Outlook, but later the mailbox stopped loading completely.

Current errors:

Outlook Web: HTTP 500

Exception: Microsoft.Exchange.Data.Storage.TooManyObjectsOpenedException

BootResult: throttle

Error source: StartupData

Outlook on mobile: HTTP 503

Additional information:

I can successfully sign in to my Microsoft account and access its security settings.

My other Outlook accounts work normally.

The problem affects only the compromised mailbox.

My original mailbox contents were missing when I first regained access.

Clearing browser sessions and accessing Outlook from different devices have not resolved the problem.

I cannot use Outlook's built-in support because the mailbox crashes before the interface loads.

What I need assistance with:

Is this exception caused by a mailbox-side Exchange resource limit or another server-side condition?

Can Microsoft investigate or reset the affected mailbox's server-side resources?

How can I contact the Outlook.com technical support team when the affected mailbox cannot load?

Can Microsoft assist with recovering the missing emails once mailbox access is restored?

I have screenshots containing the error diagnostics, timestamps, and Microsoft account activity records.

I would appreciate assistance from a Microsoft moderator or an appropriate Outlook.com support team.

Thank you.Hello Microsoft Support and Community,

I urgently need assistance with my personal Outlook.com mailbox.

On October 18, 2026, my Microsoft account experienced an unauthorized successful sign-in originating from an IP address geolocated to Brazil.

After discovering this, I immediately secured the account by:

Resetting my Microsoft account password.

Enabling two-step verification with Microsoft Authenticator.

Signing out of all devices and sessions.

Removing existing app passwords.

Reviewing mailbox rules, blocked senders, and forwarding settings.

I was initially able to access Outlook, but later the mailbox stopped loading completely.

Current errors:

Outlook Web: HTTP 500

Exception: Microsoft.Exchange.Data.Storage.TooManyObjectsOpenedException

BootResult: throttle

Error source: StartupData

Outlook on mobile: HTTP 503

Additional information:

I can successfully sign in to my Microsoft account and access its security settings.

My other Outlook accounts work normally.

The problem affects only the compromised mailbox.

My original mailbox contents were missing when I first regained access.

Clearing browser sessions and accessing Outlook from different devices have not resolved the problem.

I cannot use Outlook's built-in support because the mailbox crashes before the interface loads.

What I need assistance with:

Is this exception caused by a mailbox-side Exchange resource limit or another server-side condition?

Can Microsoft investigate or reset the affected mailbox's server-side resources?

How can I contact the Outlook.com technical support team when the affected mailbox cannot load?

Can Microsoft assist with recovering the missing emails once mailbox access is restored?

I have screenshots containing the error diagnostics, timestamps, and Microsoft account activity records.

I would appreciate assistance from a Microsoft moderator or an appropriate Outlook.com support team.

Thank you.

0 comments

1 answer

Your answer

Answer 1

This cross-client TooManyObjectsOpenedException at StartupData requires Microsoft to investigate the Outlook.com mailbox service, so open a support request outside the affected mailbox and ask for mailbox-side diagnostics rather than repeating browser or device troubleshooting.

What the error indicates

The combination of:

Outlook.com HTTP 500
Outlook Mobile HTTP 503
TooManyObjectsOpenedException
BootResult: throttle
esrc: StartupData
Successful access to the Microsoft account and security pages
Failure isolated to one mailbox across devices

is consistent with a mailbox-service or startup/throttling condition, not a local browser session problem. The exact TooManyObjectsOpenedException and BootResult: throttle combination has also been reported for Outlook.com in October 2026 ^1^.

However, the public information does not establish:

the precise backend resource that exceeded its limit;
that the unauthorized sign-in caused the mailbox failure; or
that users can reset the condition themselves.

Outlook.com users have no Exchange administrative access or supported mailbox-reset command. Microsoft Support must determine whether the mailbox needs server-side repair, reprovisioning, or release from throttling.

Open a support case without loading Outlook.com

Since the mailbox UI cannot open, use one of these external routes.

Option 1: Windows Get Help app

Open Start, search for Get Help, and launch it.
Enter:
Personal Outlook.com mailbox inaccessible — HTTP 500 TooManyObjectsOpenedException at StartupData
Select Contact Support when offered.
Choose the Outlook.com/Microsoft account product and the closest email-access category.
Select an available contact method, such as browser chat or callback.

Microsoft documents that Get Help can connect personal-account users to support, although available methods depend on the issue, subscription, region, and operating hours ^2^.

Option 2: Microsoft’s public support page

Open Microsoft customer support and select the Personal account path, then describe this as an Outlook.com technical problem. The site may offer self-help or connect you to an appropriate contact option ^3^.

Option 3: Outlook Mobile in-app support

If the mobile app’s menus remain accessible despite the mailbox HTTP 503:

Tap Inbox or the account-menu button.
Tap ? at the bottom.
Select Contact Outlook Mobile Support.

That is Microsoft’s documented route for Outlook for iOS and Android support ^4^.

Also check Microsoft’s public service-health page for a current Outlook.com incident before opening the case ^5^. A similar exact error was publicly reported in mid-October 2026, but the available public information does not confirm a matching incident specifically for October 18.

Information to put in the case

Request mailbox-side investigation of Outlook.com startup throttling/provisioning, and include:

UTC date and time of the latest failure;
exact exception, BootResult, esrc, HTTP status, and any request/correlation ID;
that web and mobile both fail;
that multiple devices and browser-session clearing made no difference;
that other Outlook.com mailboxes work;
that Microsoft account and security pages remain accessible;
when the unauthorized sign-in occurred and when the mailbox last worked;
screenshots attached privately to the support case.

Do not publish session IDs, correlation data, IP addresses, or account identifiers in a public Q&A thread.

Recover the missing messages after access returns

Use a PC or Mac as soon as the mailbox opens:

Check Deleted Items, Junk Email, Archive, and the Other tab.
In Deleted Items, select Recover items deleted from this folder.
Select the missing messages and choose Restore.

Messages removed from Deleted Items remain recoverable for 30 days; Junk Email is also retained for 30 days. Recovery from the recoverable-items area requires a computer rather than the mobile app or mobile browser ^6^.

If messages are absent from both Deleted Items and the recoverable-items list, add that fact to the existing support case immediately. The documented self-service recovery window is limited, and recovery is not guaranteed after items have been permanently removed.

References