Outlook Didn’t Initialize: Fix OwaInvalidConfigurationException in Exchange

Full Error

When trying to log in to Outlook Web App (OWA), users may see the following error:

Outlook didn't initialize.
The Active Directory configuration settings couldn't be accessed for virtual directory "owa" under Web site "Exchange Back End".


Request
Url: https://mailserver.domain.com.ua:444/owa/auth/error.aspx
User host address: 10.x.x.x
OWA version: 15.1.2242.12

Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: The Active Directory configuration settings couldn't be accessed for virtual directory "owa" under Web site "Exchange Back End".

Call stack
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()
Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoaderBase.Load()
Microsoft.Exchange.Clients.Owa.Core.OwaSettingsLoader.Load()
Microsoft.Exchange.Clients.Owa.Core.OwaApplicationBase.ExecuteApplicationStart(Object sender, EventArgs e)

Inner Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: The Active Directory configuration settings couldn't be accessed for virtual directory "owa" under Web site "Exchange Back End".

Call stack
Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(IConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId vDirADObjectId, Boolean isPhoneticSupportEnabled)
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration()
Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager()

What This Error Can Mean

This error is not always caused by a single issue.

In general, it may be related to:

• OWA virtual directory misconfiguration
• IIS issues
• Exchange services not running properly
• Problems accessing Active Directory

So first, always verify basic Exchange health:

• Exchange services are healthy
• OWA works for other users
• IIS is running

When This Article Applies

If everything above looks fine, and:

• OWA works for most users
• The issue affects only specific users
• Or only newly created mailboxes

Then you are most likely dealing with a mailbox configuration issue

Typical Scenarios

1. New Mailbox (Most Common)

• User created via ECP
• User has never logged into OWA before
• Login fails immediately

2. User Enabled OWA Light Mode

• User manually enables “Light version of Outlook Web App”
• OWA stops working even if it worked before

Root Cause

The issue is usually caused by invalid or incomplete mailbox regional settings.

When a mailbox is created via ECP, Exchange does NOT always properly initialize:

• Language
• Time zone
• Default folders (Inbox, Sent Items, etc.)

Full OWA may still work.

OWA Light is stricter and fails with OwaInvalidConfigurationException.

Fix

Run the following command in Exchange Management Shell:

Get-Mailbox -Identity username | Set-MailboxRegionalConfiguration -Language en-US -TimeZone "FLE Standard Time" -LocalizeDefaultFolderName

Important

• Replace en-US with your environment language
  (e.g. de-DE, fr-FR, uk-UA)
• Set the correct time zone for your region and replace username with the actual user account

What This Fix Does

• Initializes mailbox language
• Sets a valid time zone
• Recreates and localizes default folders

After this, OWA works normally (including Light mode)

Workaround (Disable Light Mode)

In some cases, this issue may occur even when mailbox regional settings are correct, especially if the user has enabled OWA Light mode.

OWA Light is less tolerant to configuration inconsistencies and can trigger this error even on otherwise working mailboxes.

Option 1: Disable via OWA settings

If the user can access settings:

1. Go to Settings → General → Light version
2. Uncheck:
   – Use the light version of Outlook
3. Log out and log back in

Option 2: Open Mailbox via Another User

If the user cannot log in at all:

1. Temporarily grant yourself access to the user’s mailbox
2. Log in to OWA with your admin account
3. Click Open another mailbox
4. Enter the affected user’s mailbox

The mailbox will open normally (without the error).

• Go to settings and disable Light mode
• Remove your access permissions

After that, the user should be able to log in normally

Disable OWA Light Mode via PowerShell (Optional)

To prevent users from enabling Light mode:

Set-CASMailbox username -OWALightEnabled $false

Check status:

Get-CASMailbox username | fl OWALightEnabled

Disable for all users:

Get-Mailbox -ResultSize Unlimited | Set-CASMailbox -OWALightEnabled $false

Why This Happens

• Exchange does not fully initialize mailbox regional settings via ECP
• Some mailboxes end up with inconsistent configuration
• OWA Light strictly depends on these settings and fails if they are invalid

Permanent Solution (Automation)

Option 1: Scheduled Task

$users = Get-Mailbox -ResultSize Unlimited | Where-Object {
    $_.WhenCreated -gt (Get-Date).AddMinutes(-10)
}

foreach ($user in $users) {
    $config = Get-MailboxRegionalConfiguration $user.Alias

    if (-not $config.Language) {
        Set-MailboxRegionalConfiguration -Identity $user.Alias `
            -Language en-US `
            -TimeZone "FLE Standard Time" `
            -LocalizeDefaultFolderName
    }
}

Option 2: Provisioning via PowerShell

Instead of using ECP, you can create and initialize the mailbox in one step via PowerShell:

New-Mailbox `
  -Name "John Doe" `
  -UserPrincipalName john.doe@domain.com `
  -Alias john.doe `
  -FirstName John `
  -LastName Doe `
  -Password (ConvertTo-SecureString "P@ssw0rd!" -AsPlainText -Force)

Set-MailboxRegionalConfiguration -Identity john.doe `
  -Language en-US `
  -TimeZone "FLE Standard Time" `
  -LocalizeDefaultFolderName

This way the mailbox is created and immediately gets correct regional settings, no need to fix anything later.