In an Exchange2013 CU2 environment with 4 mailbox servers (2 each in a different site) and separate front end servers (also 2 each in a different site) I find the application evenlogs on mailbox servers littered (500 events per 24 hours) with Event ID: 1309, Event Source: ASP.NET. With common underlying exeptions "MapiExceptionMailboxInTransit" and "MapiExceptionIllegalCrossServerConnection"
The errors seem to be caused by attempts to login to https://localhost:444/owa/proxylogon.owa using the userID of a Health monitoring mailbox that is actively mounted on a different mailboxserver.

I theorize that this to be a bug in the Exchange Health manager (not keeping track of where mailboxes are actively mounted) but can't say that for sure.

Any suggestion on how to "turn off" this check in the health manager configuration so I don't get all these false positive messages ?

Examples of message below --------------------------

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          8/5/2013 9:55:45 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      den-s-mbx4.mydomain.com
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 8/5/2013 9:55:45 AM
Event time (UTC): 8/5/2013 3:55:45 PM
Event ID: ec427c24c3d74b3d80c99d8e8612c8f1
Event sequence: 79334
Event occurrence: 11067
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/2/ROOT/owa-1-130188945774437279
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: DEN-S-MBX4
 
Process information:
    Process ID: 18388
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
 
Exception information:
    Exception type: MapiExceptionMailboxInTransit
    Exception message: MapiExceptionMailboxInTransit: DatabaseLocationProvider detected site violation (hr=0x0, ec=1292)

 
 
Request information:
    Request URL: https://localhost:444/owa/proxylogon.owa
    Request path: /owa/proxylogon.owa
    User host address: 127.0.0.1
    User: MYDOMAIN\SM_4275121dabc948258
    Is authenticated: True
    Authentication Type: Kerberos
    Thread account name: NT AUTHORITY\SYSTEM
 
Thread information:
    Thread ID: 49
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:
 
 
Custom event details:

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ASP.NET 4.0.30319.0" />
    <EventID Qualifiers="32768">1309</EventID>
    <Level>3</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-05T15:55:45.000000000Z" />
    <EventRecordID>6270698</EventRecordID>
    <Channel>Application</Channel>
    <Computer>den-s-mbx4.mydomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>3005</Data>
    <Data>An unhandled exception has occurred.</Data>
    <Data>8/5/2013 9:55:45 AM</Data>
    <Data>8/5/2013 3:55:45 PM</Data>
    <Data>ec427c24c3d74b3d80c99d8e8612c8f1</Data>
    <Data>79334</Data>
    <Data>11067</Data>
    <Data>0</Data>
    <Data>/LM/W3SVC/2/ROOT/owa-1-130188945774437279</Data>
    <Data>Full</Data>
    <Data>/owa</Data>
    <Data>C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\</Data>
    <Data>DEN-S-MBX4</Data>
    <Data>
    </Data>
    <Data>18388</Data>
    <Data>w3wp.exe</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>MapiExceptionMailboxInTransit</Data>
    <Data>MapiExceptionMailboxInTransit: DatabaseLocationProvider detected site violation (hr=0x0, ec=1292)

</Data>
    <Data>https://localhost:444/owa/proxylogon.owa</Data>
    <Data>/owa/proxylogon.owa</Data>
    <Data>127.0.0.1</Data>
    <Data>MYDOMAIN\SM_4275121dabc948258</Data>
    <Data>True</Data>
    <Data>Kerberos</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>49</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>False</Data>
    <Data>
    </Data>
  </EventData>
</Event>

----------------------------------

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          8/5/2013 12:08:32 PM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      wal-vm-mbx1.mydomain.com
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 8/5/2013 12:08:32 PM
Event time (UTC): 8/5/2013 4:08:32 PM
Event ID: 77d613a2c42344348fd215f4ad092708
Event sequence: 325843
Event occurrence: 7098
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/3/ROOT/owa-1-130191699398831006
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
    Machine name: WAL-VM-MBX1
 
Process information:
    Process ID: 31516
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
 
Exception information:
    Exception type: MapiExceptionIllegalCrossServerConnection
    Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA;Action=ViaProxy] is not allowed to make cross-server calls to [wal-s-mbx2.mydomain.com]
   at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)

 
 
Request information:
    Request URL: https://localhost:444/owa/proxylogon.owa
    Request path: /owa/proxylogon.owa
    User host address: ::1
    User: MYDOMAIN\SM_9d047d8145014f31b
    Is authenticated: True
    Authentication Type: Kerberos
    Thread account name: NT AUTHORITY\SYSTEM
 
Thread information:
    Thread ID: 41
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:    at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)
 
 
Custom event details:

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ASP.NET 4.0.30319.0" />
    <EventID Qualifiers="32768">1309</EventID>
    <Level>3</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-05T16:08:32.000000000Z" />
    <EventRecordID>1841325</EventRecordID>
    <Channel>Application</Channel>
    <Computer>wal-vm-mbx1.mydomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>3005</Data>
    <Data>An unhandled exception has occurred.</Data>
    <Data>8/5/2013 12:08:32 PM</Data>
    <Data>8/5/2013 4:08:32 PM</Data>
    <Data>77d613a2c42344348fd215f4ad092708</Data>
    <Data>325843</Data>
    <Data>7098</Data>
    <Data>0</Data>
    <Data>/LM/W3SVC/3/ROOT/owa-1-130191699398831006</Data>
    <Data>Full</Data>
    <Data>/owa</Data>
    <Data>C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\</Data>
    <Data>WAL-VM-MBX1</Data>
    <Data>
    </Data>
    <Data>31516</Data>
    <Data>w3wp.exe</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>MapiExceptionIllegalCrossServerConnection</Data>
    <Data>MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA;Action=ViaProxy] is not allowed to make cross-server calls to [wal-s-mbx2.mydomain.com]
   at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String&amp; correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)

</Data>
    <Data>https://localhost:444/owa/proxylogon.owa</Data>
    <Data>/owa/proxylogon.owa</Data>
    <Data>::1</Data>
    <Data>MYDOMAIN\SM_9d047d8145014f31b</Data>
    <Data>True</Data>
    <Data>Kerberos</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>41</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>False</Data>
    <Data>   at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String&amp; correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)
</Data>
  </EventData>
</Event>

Hi,

To troubleshoot this issue, we can try resetting the OWA virtual directory.

http://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

Hi,

 I am facing similar issue in my Exchange 2013 DAG setup..

When I launch OWA and try to load the Enterprise Vault Office mail APP through OWA...the request goes through CAS however on mailbox I get 500 http error for the following event id:

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          8/7/2013 2:28:27 PM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EX15-MBX1.samba.local
Description:
Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 8/7/2013 2:28:26 PM 
Event time (UTC): 8/7/2013 8:58:26 AM 
Event ID: b620b73033e14eecbadd02e3c0628ec6 
Event sequence: 2 
Event occurrence: 1 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/2/ROOT/owa-1-130203394254023750 
    Trust level: Full 
    Application Virtual Path: /owa 
    Application Path: E:\Exchange2013\ClientAccess\owa\ 
    Machine name: EX15-MBX1 
 
Process information: 
    Process ID: 9784 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\SYSTEM 
 
Exception information: 
    Exception type: MapiExceptionIllegalCrossServerConnection 
    Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA;Action=ViaProxy] is not allowed to make cross-server calls to [EX15-MBX2.samba.local]
   at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)

 
 
Request information: 
    Request URL: https://localhost:444/owa/proxylogon.owa 
    Request path: /owa/proxylogon.owa 
    User host address: ::1 
    User: SAMBA\SM_9437c4e62aac4f239 
    Is authenticated: True 
    Authentication Type: Kerberos 
    Thread account name: NT AUTHORITY\SYSTEM 
 
Thread information: 
    Thread ID: 9 
    Thread account name: NT AUTHORITY\SYSTEM 
    Is impersonating: False 
    Stack trace:    at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)
 
 
Custom event details: 

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ASP.NET 4.0.30319.0" />
    <EventID Qualifiers="32768">1309</EventID>
    <Level>3</Level>
    <Task>3</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-08-07T08:58:27.000000000Z" />
    <EventRecordID>484819</EventRecordID>
    <Channel>Application</Channel>
    <Computer>EX15-MBX1.samba.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>3005</Data>
    <Data>An unhandled exception has occurred.</Data>
    <Data>8/7/2013 2:28:26 PM</Data>
    <Data>8/7/2013 8:58:26 AM</Data>
    <Data>b620b73033e14eecbadd02e3c0628ec6</Data>
    <Data>2</Data>
    <Data>1</Data>
    <Data>0</Data>
    <Data>/LM/W3SVC/2/ROOT/owa-1-130203394254023750</Data>
    <Data>Full</Data>
    <Data>/owa</Data>
    <Data>E:\Exchange2013\ClientAccess\owa\</Data>
    <Data>EX15-MBX1</Data>
    <Data>
    </Data>
    <Data>9784</Data>
    <Data>w3wp.exe</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>MapiExceptionIllegalCrossServerConnection</Data>
    <Data>MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA;Action=ViaProxy] is not allowed to make cross-server calls to [EX15-MBX2.samba.local]
   at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String&amp; correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)

</Data>
    <Data>https://localhost:444/owa/proxylogon.owa</Data>
    <Data>/owa/proxylogon.owa</Data>
    <Data>::1</Data>
    <Data>SAMBA\SM_9437c4e62aac4f239</Data>
    <Data>True</Data>
    <Data>Kerberos</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>9</Data>
    <Data>NT AUTHORITY\SYSTEM</Data>
    <Data>False</Data>
    <Data>   at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String&amp; correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)
</Data>
  </EventData>
</Event>

Simon, These errors occur on the mailbox servers ... they have no client access role installed, the command get-owavirtualdirectory -server servername returns nothing. so I can not remove and create the owa backend directory with the information in the link you provided.

Also the accounts in the error message are consistenly the user accounts for various health monitoring mailboxes.

User accounts appear unaffected, further letting me believe that the backend owa is OK.

The following clues in the stacktrace "MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA;Action=ViaProxy] is not allowed to make cross-server calls to [wal-s-mbx2.mydomain.com]" and "at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)" appear to suggest that the code is attempting to rightfully block the request because the mailbox server is not hosting the active copy of the health monitoring mailbox that is trying to login, but somehow this runs into an exception in the ASP.NET code.

Is there a way to configure or manipulate these health checks ? - False positives are not really helpfull.

Or should I just wait for CU3 and hope that this bug will be fixed then ?

Nupur, you are indeed seeing the same events, however I doubt there is a relationship between the event and your OWA logon session as a user because the account referenced in the event = SAMBA\SM_9437c4e62aac4f239 which is a health monitoring account, and i doubt you used that account to logon to OWA when you attempted to load Enterprise Vault Office mail App.

get-mailbox -id SAMBA\SM_9437c4e62aac4f239 -monitoring

Nupur, you are indeed seeing the same events, however I doubt there is a relationship between the event and your OWA logon session as a user because the account referenced in the event = SAMBA\SM_9437c4e62aac4f239 which is a health monitoring account, and i doubt you used that account to logon to OWA when you attempted to load Enterprise Vault Office mail App.

get-mailbox -id SAMBA\SM_9437c4e62aac4f239 -monitoring

• Edited by adenhaan Wednesday, August 07, 2013 9:45 PM ambiguity

Nupur, you are indeed seeing the same events, however I doubt there is a relationship between the event and your OWA logon session as a user because the account referenced in the event = SAMBA\SM_9437c4e62aac4f239 which is a health monitoring account, and i doubt you used that account to logon to OWA when you attempted to load Enterprise Vault Office mail App.

get-mailbox -id SAMBA\SM_9437c4e62aac4f239 -monitoring

• Edited by adenhaan Wednesday, August 07, 2013 9:45 PM ambiguity

Nupur, you are indeed seeing the same events, however I doubt there is a relationship between the event and your OWA logon session as a user because the account referenced in the event = SAMBA\SM_9437c4e62aac4f239 which is a health monitoring account, and i doubt you used that account to logon to OWA when you attempted to load Enterprise Vault Office mail App.

get-mailbox -id SAMBA\SM_9437c4e62aac4f239 -monitoring

• Edited by adenhaan Wednesday, August 07, 2013 9:45 PM ambiguity

Nupur, you are indeed seeing the same events, however I doubt there is a relationship between the event and your OWA logon session as a user because the account referenced in the event = SAMBA\SM_9437c4e62aac4f239 which is a health monitoring account, and i doubt you used that account to logon to OWA when you attempted to load Enterprise Vault Office mail App.

get-mailbox -id SAMBA\SM_9437c4e62aac4f239 -monitoring

• Edited by adenhaan Wednesday, August 07, 2013 9:45 PM ambiguity

Hello

I had the same problem.

It was due to Health Monitoring mailboxes with database property defined to $null value (databases removed).

[PS] Get-Mailbox -Monitoring

...
WARNING: The object domain/Microsoft Exchange System Objects/Monitoring
Mailboxes/HealthMailboxd740500b93e24ed4992d2dda1a43eda4 has been corrupted, and it's in an inconsistent state. The following validation errors happened:
WARNING: Database is mandatory on UserMailbox.
WARNING: Database is mandatory on UserMailbox.

I removed all monitoring mailboxes AD accounts (domain/Microsoft Exchange System Objects/Monitoring Mailboxes)
Then i restarted "Microsoft Exchange Health Manager" service on each Exchange 2013 server.
Mandatory monitoring mailboxes are re-created automatically.

Regards

Thanks. I removed all montoring mailboxes from AD as you suggested and they got automatically re-created.

I checked and the database property is set for all of them.

The servername property is about equally split between 2 mailbox server names (even though all mailboxes are active on a single mailbox server right now).

Unfortunately this did not solve the issue as I am still receiving these messages on all 3 mailbox servers that have passive copies of the databases.

Hello

events disappeared during a while but you're right, they are back :(

Still investigating ...

After a 9 hour support call on Friday, we had to recreate all Health/Monitoring mbx and the MonitoringMailboxes OU after rerunning Setup /PrepareAD.  I still have the same errors referenced:

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          9/3/2013 8:19:29 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      ICTEXCH01.domain.local
Description:
Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 9/3/2013 8:19:29 AM 
Event time (UTC): 9/3/2013 2:19:29 PM 
Event ID: 

be685b0e8bb64fb28d0034f27b1a9922 
Event sequence: 21213 
Event occurrence: 10832 
Event detail code: 0 
 
Application information: 
    Application domain: 

/LM/W3SVC/2/ROOT/owa-1-130221879503207027 
    Trust level: Full 
    Application Virtual Path: /owa 
    Application Path: D:\Microsoft\Exchange 

Server\V15\ClientAccess\owa\ 
    Machine name: ICTEXCH01 
 
Process information: 
    Process ID: 12176 
    Process name: w3wp.exe 
    Account name: NT 

AUTHORITY\SYSTEM 
 
Exception information: 
    Exception type: MapiExceptionIllegalCrossServerConnection 
    Exception message: 

MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA;Action=ViaProxy] is not allowed to make cross-server 

calls to [ICTEXCH02.domain.local]
   at Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, 

String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean 

wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] 

clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)
 
Request information: 
    Request URL: 

https://localhost:444/owa/proxylogon.owa 
    Request path: /owa/proxylogon.owa 
    User host address: 127.0.0.1 
    User: ICTGRP\SM_1c532dc9f31a41989 
 

   Is authenticated: True 
    Authentication Type: Kerberos 
    Thread account name: NT AUTHORITY\SYSTEM 
 
Thread information: 
    Thread ID: 54 
    
Thread account name: NT AUTHORITY\SYSTEM 
    Is impersonating: False 
    Stack trace:    at 

Microsoft.Mapi.MonitoringBlockingExRpcConnectionFactory.Create(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, 

String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, Boolean 

wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] 

clientSessionInfo, TimeSpan connectionTimeout, Byte[] tenantHint)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore)

Hi.

I have the same problem in my enviroment with two CAS/HUB servers in a DAG enviroment. I removed all montoring mailboxes from AD and they got automatically re-created. I still have the same failure.

Any idea? I`m stuck. Owa etc works just fine.

Regards

+1 to the list.  We have 6 monitoring accounts and only 1 corrupt.  tried the suggestions above and it fixed it for a while but its back.  We're also running CU2.

Jason.

Same Error - Exchange 2013 Cu2 . Nothing could fix it

Same error for us in CU3.

I also have seen this issue since CU1 and am now on CU3.  I have a DAG and I wonder if that is part of the issue.  Does anyone else here that is seeing the problem *not* have a DAG or is running a single server?

Same issue on CU3...cleaned up all of the health mailboxes. Anyone find a fix?

Same error after installing CU3 with DAG....

Has anyone from Microsoft chimed in yet?  Between this and everything else flooding my damned event logs, it can get difficult finding real issues whilst filtering out the noise that's in there right now!

Also have this issue on Ex2013 CU3, but only on one server from DAG.

I made OWA integration of two mailbox servers with Lync 2013. On one of them appears Event 112, which mean that integration was successful, on second server instead of Event 112 appears Event 1309 ASP.NET error. After that a half of users see in OWA Lync presence, other - don't see.

2013 CU3 Same error for me.. no fix yet?

Same issue here with CU3... I didn't try yet with SP1 because BES and netbackup doesn't support it yet.

I can confirm that this is still happening in 2013 SP1.

I experienced the same problem with SP1. It looks like exchange has a preference for 2012 DC's even if they are off site... We have 2012 DC's in all sites except the main site. The main site was planned to be upgraded but we were not there yet. After we brought up a 2012 DC server in the site where exchange was installed al these errors were gone... 2003 DC's are official supported but I think there is an undocumented feature that even tier 3 and 4 of MS support isn't aware of...

Also check for informational event 2080 in your application log and wonder what exchange thinks of what is on site and what is off site... This can change every time it does this check...

Related events:

1006 warning site violation
1039 warning asp.net
2080 info over what exchange thinks of on and off site

Problem description:
Connection problems with: Outlook clients
Owa http 500 something went wrong
Active sync http 500 (cannot connect to server on device)
ECP http 500

If someone can replicate this then let me know in this thread! I have still a case open with MS and have the ability to discuss things with them...

• Proposed as answer by Wouter Tepper Tuesday, April 01, 2014 11:33 AM
• Unproposed as answer by Wouter Tepper Tuesday, April 01, 2014 11:35 AM
• Edited by Wouter Tepper Tuesday, April 01, 2014 11:45 AM

We have a single site with 2012r2 domain controllers and get this same error using Exchange 2013 SP1 running on Windows 2012r2.    So I don't think this error is at all related to non 2012 DC in the site.

Same problem here, Exchange 2013SP1+W2012R2.

Same problem here, Exchange 2013SP1+W2012R2.

same here

Same Issue  i opened a case to know what's going one with this event :

http://unifiedit.wordpress.com/2014/04/30/exchange-2013-asp-net-4-0-30319-0-mapiexceptionillegalcrossserverconnection/

Hi, have you had an answer from Microsoft support regarding this problem?

I've got the same.

Thanks

Antonio

DavidR1, I'm having the same issue with no DAG involved. Just a CAS and a MBX/UM/HUB server (two servers, that is).

I've tracked this issue on a greenfield deployment on 4 Exchange servers in a DAG.  The error pops up on all the servers.  I've managed to resolve the problem.

The error appears to be where a health mailbox isnt located on a database mounted on this server.  So for example MBX1 hosts DB01 and is reporting the error.  MBX2 hosts DB02 and that has the mailbox located on it.

Workaround: Move the mailbox reported in the event log to a database located on the server logging the error.  In the above example the move would be to DB01.  It is not clear if this fix has any other consequences, but it does stop the errors from being logged!

Hi, in my case the problem related to this error is little different.

I've got a DAG of two multirole servers (CAS+MBX) (Exchange 2013 SP1 on W2K12  R2) and if I stop the OWA application pool on the server that host the active mailbox DB, the balancer in the correct manner redirect the session to the CAS server where the OWA application pool is working, but this CAS is not able to connect the the server with the active mailbox DB (from the error message is clear that he know who is hosting the active mailbox DB). In the event viewer I have the ASP.NET error above with the message "is not allowed to make cross-server calls to".

The problem is the same with DAG in "old" style and DAG semplified without IP.

The strange is that when the OWA application pool is started on the CAS+MBX server that is hosting the active DB, and the balancer select a CAS+MBX server that don't have the active mailbox DB, this is able to connect to the server that is hosting the active DB.

In the error logs nothing that can help to troubleshooting these problems.

Thanks

• Edited by AO1201 Monday, May 26, 2014 3:27 PM

I had the same problem.

Ideleted all monitoring databases from Active Directory and resatrted services. Now it's working.

More information

http://theucguy.net/recreate-exchange-2013-health-mailboxes

Hi, I've deleted all the health-mailboxes users and recreated these, but doesn't solve the problem that is still the same....when I stop the OWA application pool of the member of the DAG where the mailbox database is active, the other members are not able to connect to the mailbox and the error is still the same asp.net event id 1309.

No problems when the OWA application pool is up, and also the other members are able to reach the active mailbox database on the node where it is.

• Edited by AOit Monday, June 09, 2014 3:26 PM

Hi, we are experiencing  the same issue on 2 of our Exchange 2013 systems, both systems having at least two DAG multirole server nodes. Tried to recreate the health mailboxes and recreated the OWA virtual directories.

The error messages are only logged for health mailboxes, no user logins are affected.

Any new information about this error? A fix from Microsoft?

Regards,

Sebastian

+1

Same errors here, Exchange 2013 SP1, 4 multi-role servers in a DAG.

Has anyone tried CU5 or CU6, and can confirm deny whether this is addressed? Id don't see it anywhere in the release notes.

Thanks,

Karl

Hi,

This same happens also with CU5. I have two multirole servers with DAG configured.

Br.

Vesa

I experienced the same problem with SP1. It looks like exchange has a preference for 2012 DC's even if they are off site... We have 2012 DC's in all sites except the main site. The main site was planned to be upgraded but we were not there yet. After we brought up a 2012 DC server in the site where exchange was installed al these errors were gone... 2003 DC's are official supported but I think there is an undocumented feature that even tier 3 and 4 of MS support isn't aware of...

Also check for informational event 2080 in your application log and wonder what exchange thinks of what is on site and what is off site... This can change every time it does this check...

Related events:

1006 warning site violation
1039 warning asp.net
2080 info over what exchange thinks of on and off site

Problem description:
Connection problems with: Outlook clients
Owa http 500 something went wrong
Active sync http 500 (cannot connect to server on device)
ECP http 500

If someone can replicate this then let me know in this thread! I have still a case open with MS and have the ability to discuss things with them...

I've a set up with only 2 2012 DC and I've the same issue. Exchange 2013 CU4

Hi all again, I finally resolved this, just went to Active directory, under Microsoft Exchange System Objects OU and I deleted all Health Mailboxes.

Then reset Health Manager service in all servers, and voil! ASP event is gone since more than 24 hours.

Regards,

Hi,

Can you tell me if this resolved your issue permanently please?

We are running Exchange 2013 SP1 in Co-existence with 2010 SP3 and are encountering these same warnings.

Thanks

Guys I had the same issue and recreated the Health Mailboxes + restarting Exch Health service didn't work.

Then I realised I didn't restarted the service in all the servers.

Once I restarted the Health service in all the 4 servers the event dissappeared (or at least for the last 24 hours).

I guess y'all saw this but I'm putting anyway http://www.expta.com/2014/05/fix-for-aspnet-40303190-3005-event.html 

Cheers,

Frank