for weeks i've been troubled by a mailbox database that has been in crawling state. summary of it is in this thread:

index state crawling

so last week i created a new mailbox database, moved about 50 or so mailboxes to it. that many mailboxes (it have a max limit of 5GB per mailbox user) took almost 6 days to complete.

today when i checked my mailbox databases, all of them are in healthy index state! including the mailbox database that have been crawling for several weeks!!

what just happened?

Hi Reno,

Thank you for your question.

Did you use DAG in your organization?

What is Exchange version and CU?

We could active database manually on the specific Exchange mailbox server.  Then, if the issue persist, restart Microsoft Exchange Information Store service.

In addition, we could check if there are any errors in application log on this Exchange mailbox server and post them for our troubleshooting.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

hi,

in my excitement i forgot to include: Exchange 2013 CU4 and yep using DAG with two mailbox servers.

the only errors i could see that is even remotely related are events 1309 and 1006.

my question is, why the index crawling state got fixed? i merely moved 50 mailboxes to a new database. could this be somewhat the same like when a PST file (nope we're not using) almost gets full and it throws tantrums? but when some emails are removed from that PST file it goes back to normal.

btw, the mailbox database is working fine.

• Edited by Reno Mardo 2 hours 38 minutes ago

Hi Reno,

I  suspect the issue might be because of anyone of the following..

Deadlock: Exchange Search deadlocks waiting on threads from MSSearch
Corruption: One or more search indices are corrupted
Stall: Similar to deadlock in that the indices are not getting updated
Backlog: The Search catalog is backlogged resulting in missing index searches


Thanks & Regards
Vickram M
 

hi,

in my excitement i forgot to include: Exchange 2013 CU4 and yep using DAG with two mailbox servers.

the only errors i could see that is even remotely related are events 1309 and 1006.

my question is, why the index crawling state got fixed? i merely moved 50 mailboxes to a new database. could this be somewhat the same like when a PST file (nope we're not using) almost gets full and it throws tantrums? but when some emails are removed from that PST file it goes back to normal.

btw, the mailbox database is working fine.

• Edited by Reno Mardo Monday, July 27, 2015 4:50 AM

hi,

in my excitement i forgot to include: Exchange 2013 CU4 and yep using DAG with two mailbox servers.

the only errors i could see that is even remotely related are events 1309 and 1006.

my question is, why the index crawling state got fixed? i merely moved 50 mailboxes to a new database. could this be somewhat the same like when a PST file (nope we're not using) almost gets full and it throws tantrums? but when some emails are removed from that PST file it goes back to normal.

btw, the mailbox database is working fine.

• Edited by Reno Mardo Monday, July 27, 2015 4:50 AM

Hi Reno,

We suggest you post Event id 1309 for our troubleshooting.

Then we could restart the following services to check if the issue persist:

1.        Microsoft Exchange Search
2.        Microsoft Exchange Search Host Controller

If not, we could refer to the following link to repair database to check if issue was solved:

https://technet.microsoft.com/en-us/library/ff625226%28v=exchg.150%29.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

hi,

event 1309:

Log Name:      Application
Source:        ASP.NET 4.0.30319.0
Date:          7/29/2015 11:14:22 AM
Event ID:      1309
Task Category: Web Event
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      MB01.ACME.com
Description:
Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 7/29/2015 11:14:22 AM 
Event time (UTC): 7/29/2015 8:14:22 AM 
Event ID: 6d2408a6d98944cdab25dc7f0a9fdc22 
Event sequence: 93154 
Event occurrence: 30143 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/2/ROOT/owa-1-130813289213649725 
    Trust level: Full 
    Application Virtual Path: /owa 
    Application Path: D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\ 
    Machine name: MB01 
 
Process information: 
    Process ID: 5824 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\SYSTEM 
 
Exception information: 
    Exception type: MapiExceptionIllegalCrossServerConnection 
    Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [MB01.ACME.COM] to [mb02.ACME.COM]
   at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
   at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.ExRpcConnectionFactory.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, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, TimeSpan callTimeout, Byte[] tenantHint)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)

 
 
Request information: 
    Request URL: https://localhost:444/owa/proxylogon.owa 
    Request path: /owa/proxylogon.owa 
    User host address: 127.0.0.1 
    User: ACME\SM_5460b374dea541929 
    Is authenticated: True 
    Authentication Type: Kerberos 
    Thread account name: NT AUTHORITY\SYSTEM 
 
Thread information: 
    Thread ID: 111 
    Thread account name: NT AUTHORITY\SYSTEM 
    Is impersonating: False 
    Stack trace:    at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)
   at Microsoft.Mapi.CrossServerConnectionPolicy.CheckAndBlockMonitoringMailboxes(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.CrossServerConnectionPolicy.Apply(ExRpcConnectionInfo connectionInfo)
   at Microsoft.Mapi.ExRpcConnectionFactory.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, Boolean unifiedLogon, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout, TimeSpan callTimeout, Byte[] tenantHint)
   at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo, ClientIdentityInfo clientIdentity, String applicationId, Byte[] tenantPartitionHint, Boolean unifiedLogon)
   at Microsoft.Exchange.Data.Storage.MailboxSession.ForceOpen(MapiStore linkedStore, Boolean unifiedSession)

Hi Reno,

This event log means that LAM OWA deeptest probes target both active and passive databases. We do this because the state of DB is dynamic and only targetting actives will make us coverage on servers that don't have any actives. When a logon is attempted via passive DB store throws MapiExceptionIllegalCrossServerConnection which we handle in the probe code and consider as success. Anything other than this exception is considered as a failure, queries done by design.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

hi,

thanks but i'm not particularly worried about that event id.

i'm just looking as to what really happened why my mailbox database got fixed after many weeks in the crawling index state. rebuilding the index didn't helped. only when I moved 50 mailboxes to another database.