none
Index issue Exchance 2019 CU6 RRS feed

  • Question

  • I installed Exchange Server 2019 CU6 on 17 June.

    Since then any mailbox search in either Outlook or OWA only returns items on or prior to 17 June. Any mail received after this is not included in the search.

    Is this an issue with CU6.

    Thursday, June 25, 2020 3:39 AM

All replies

  • I installed Exchange Server 2019 CU6 on 17 June.

    Since then any mailbox search in either Outlook or OWA only returns items on or prior to 17 June. Any mail received after this is not included in the search.

    Is this an issue with CU6.

    Hi Tony,

    Does it affect all users in your organization?
    Do you have any other Exchange servers running in the environment?

    Regarding your concern about CU6, I searched a lot but so far haven’t seen reports about a similar issue after upgrading to Exchange 2019 CU6. I also checked the release notes but didn’t see this issue included in the Known issues section. And no comments about search or index issue were seen under this announcement blog either.

    Given current situation, I’d like to recommend try the steps below for troubleshooting:

     1. Are you running Exchange Online mode in Outlook client? If this is the case, please try switching to Exchange cached mode and see if there is any difference.
     2. Check the Application event log for search-related error messages.
     3. Run the cmdlet below to test Exchange Search functionality and check if any errors would be returned:

    Test-ExchangeSearch -Verbose

     4. Try restarting the following two services and see the result:


    Regards,

    Yuki Sun


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, June 26, 2020 6:09 AM
    Moderator
  • Outlook client cached mode allows for searches via "all outlook items" but all other searches via server contain no results subsequent to the CU6 update.

    We have 2 servers running a DAG.

    Test-ExchangeSearch -Verbose gives the following.

    On Mailserver - No returned information.

    On Mailserver 2 I get the response below.

    Database     Server       Mailbox      ResultFound SearchTime Error
                                                       InSeconds
    --------     ------       -------      ----------- ---------- -----
    Vet24Mailser MAILSERVER2  HealthMailbo False       -1         Mapi Error for mailbox database "Vet24Mailserver2": [Micr
    ver2                      x-MAILSERVER                        osoft.Exchange.Data.Storage.IllegalCrossServerConnectionE
                              2-Vet24Mails                        xception]: Cannot open mailbox /o=Balvetmail/ou=Exchange
                              erver2                              Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/c
                                                                  n=Servers/cn=MAILSERVER2/cn=Microsoft System Attendant.
                                                                  Inner error [Microsoft.Mapi.MapiExceptionIllegalCrossServ
                                                                  erConnection]:
                                                                  MapiExceptionIllegalCrossServerConnection: Monitoring
                                                                  mailbox [] with application ID [Client=Management] is
                                                                  not allowed to make cross-server calls from
                                                                  [MAILSERVER.local.contoso.com] to
                                                                  [MAILSERVER2.local.contoso.com]
    Vet24Mailser MAILSERVER2  HealthMailbo False       -1         Mapi Error for mailbox database
    ver2Archive               x-MAILSERVER                        "Vet24Mailserver2Archive": [Microsoft.Exchange.Data.Stora
                              2-Vet24Mails                        ge.IllegalCrossServerConnectionException]: Cannot open
                              erver2Archiv                        mailbox /o=Balvetmail/ou=Exchange Administrative Group (F
                              e                                   YDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MAILSERVER
                                                                  2/cn=Microsoft System Attendant. Inner error [Microsoft.M
                                                                  api.MapiExceptionIllegalCrossServerConnection]:
                                                                  MapiExceptionIllegalCrossServerConnection: Monitoring
                                                                  mailbox [] with application ID [Client=Management] is
                                                                  not allowed to make cross-server calls from
                                                                  [MAILSERVER.local.contoso.com] to
                                                                  [MAILSERVER2.local.contoso.com]


    Friday, July 3, 2020 12:56 AM
  • And yes, the issue is with all users in the organization searching on the server via Outlook client and OWA,
    Friday, July 3, 2020 1:49 AM
  • Issue still not resolved.

    Event Viewer shows following error for Source MSExchangeFastSearch:

    An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.FaultException: Cannot invoke service method GetFlows. No service instances were available.

    This may mean that the admin service is unable to talk to the CTS or IMS services; please ensure that your service is running.

    It may also mean that the service is busy reconfiguring itself. This happens after enabling or disabling debugging or preview (for example).In that case, the service should be restored as soon as it has reconfigured itself.
    Parameter name: services

    Server stack trace: 
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Ceres.ContentEngine.Admin.FlowService.IFlowServiceManagementAgent.GetFlows()
       at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[TManagementAgent,TResult](AgentHandle`1 agentHandle, Func`2 function, String eventLogKey)
       --- End of inner exception stack trace ---

    Tuesday, July 7, 2020 2:12 AM
  •  

    Hi Tony,

    Thanks for getting back with more details. Regarding the errors in Event Viewer, may I know if you have tried restarting the two services as mentioned in our previous discussion? Was there any improvement?

    Besides, please check the database status by running the cmdlet below:

    Get-MailboxDatabaseCopyStatus

    By the way, as this is a public forum, we have covered the domain name in your reply for privacy-related concerns. Please remember to remove any sensitive information involved in your future post to protect the personal information. Thanks for your understanding.

    Regards,

    Yuki Sun


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, July 7, 2020 5:03 AM
    Moderator
  • Thanks Yuki,

    Have restarted services as well as rebooted servers. No change.

    Get-MailboxDatabaseCopyStatus returns Healthy for both database and archive database.

                 Status          CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
                                                                  Length    Length                             State
    ----                                          ------          --------- ----------- --------------------   ------------
                 Healthy         0         0           7/07/2020 1:05:55 PM   NotApplicable
                                                                                                               
                Healthy         0         0           7/07/2020 1:07:24 PM   NotApplicable
                                                                                                               

    Further, if I try to move a mailbox I get a big funnel error

    Error: MigrationMRSPermanentException: Informational: The request has been temporarily postponed because Search is not up to date. The Microsoft Exchange Mailbox Replication service will attempt to continue processing the request.

    Many thanks

    Tony

    Tuesday, July 7, 2020 5:20 AM
  • Hi Tony,

    Please make sure all Exchange related services are running on both servers, then run the command below for an affected user(let’s say user001), check the values highlighted in the following image: 

    Get-MailboxStatistics user001| fl BigFunnel*  


    Moreover, regarding the output of Test-ExchangeSearch, as Mailbox System Attendant has been removed from Exchange 2013 and the forward, while the configuration object is still residing in configuration partition, so per my understanding, the error that “cannot open mailbox Microsoft System Attendant” is normal. Given this, you can try specify an identity parameter for Test-ExchangeSearch and try it again to see if any errors are returned:

    Test-ExchangeSearch -Identity user001 -Verbose

    By the way, prior to the Exchange 2019 CU6 update, were you running an earlier build of Exchange 2019 or do you mean you migrated from an old version of Exchange sever?
    What’s the OS version of your Exchange servers?(Exchange 2019 requires to be installed on Windows Server 2019)

    Regards,

    Yuki Sun


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Wednesday, July 8, 2020 7:17 AM
    Moderator
  • Thanks Yuki,

    All Microsoft Exchange services are running on both servers.

    The upgrade was from Exchange 2019 CU5 to Exchange 2019 CU6. Both servers are running Windows Server 2019 1809. 

    Output for user is.

    BigFunnelIsEnabled                     : True

    BigFunnelMaintainRefiners              : True
    BigFunnelFilterTableTotalSize          : 288 KB (294,912 bytes)
    BigFunnelFilterTableAvailableSize      : 192 KB (196,608 bytes)
    BigFunnelPostingListTableTotalSize     : 895.1 MB (938,541,056 bytes)
    BigFunnelPostingListTableAvailableSize : 1.563 MB (1,638,400 bytes)
    BigFunnelLargePOITableTotalSize        : 448 KB (458,752 bytes)
    BigFunnelLargePOITableAvailableSize    : 256 KB (262,144 bytes)
    BigFunnelTotalPOISize                  : 180.5 MB (189,277,018 bytes)
    BigFunnelMessageCount                  : 61621
    BigFunnelIndexedSize                   : 10.09 GB (10,830,626,387 bytes)
    BigFunnelPartiallyIndexedSize          : 516.9 MB (541,990,572 bytes)
    BigFunnelNotIndexedSize                : 1.245 GB (1,336,479,191 bytes)
    BigFunnelCorruptedSize                 : 4 B (4 bytes)
    BigFunnelStaleSize                     : 55.93 MB (58,651,199 bytes)
    BigFunnelShouldNotBeIndexedSize        : 39.2 MB (41,107,578 bytes)
    BigFunnelIndexedCount                  : 61196
    BigFunnelPartiallyIndexedCount         : 413
    BigFunnelNotIndexedCount               : 7153
    BigFunnelCorruptedCount                : 0
    BigFunnelStaleCount                    : 12
    BigFunnelShouldNotBeIndexedCount       : 3240
    BigFunnelMailboxCreationVersion        : 0

    Also results for Test-ExchangeSearch

    [PS] C:\Windows\system32>Test-ExchangeSearch -Identity tony -Verbose

    Database     Server       Mailbox      ResultFound SearchTime Error
                                                       InSeconds
    --------     ------       -------      ----------- ---------- -----
    Vet24Mailser MAILSERVER2  Tony         False       0          Time out for test thread.
    ver2Archive               

    And

    Database     Server       Mailbox      ResultFound SearchTime Error
                                                       InSeconds
    --------     ------       -------      ----------- ---------- -----
    Vet24Mailser MAILSERVER2  Gemma   False       0          Time out for test thread.
    ver2

    Presumably the BigfunnelCorruptedSize is part of the issue?

    Tony

    Friday, July 10, 2020 2:24 AM
  • Hello Tony,

    4 bytes are quite minor so it seems to me that it's should be fine. 

    As regards to the error "Time out for test thread", I found the following thread which discusses a search issue occurs to Exchange 2019 CU3 and was finally resolved by renaming the folder MachineKeys under C:\Users\All Users\Microsoft\Crypto\RSA. The symptom and event logs are not exactly the same, but I am assuming that it's worth trying if the folder exists in your environment:

    Exchange Server 2019 CU3 - Time out for test thread 

    Besides, not sure if it's related, but may I know if the MigrationMRSPermanentException error can be reproduced whenever you tries to move a mailbox? When it occurs, is there any event logs in Event Viewer? 

    This Exchange Server 2019 Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.

    Regards,

    Yuki Sun


    Exchange Server 2019 will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.

    For more information, please refer to the sticky post.

    Tuesday, July 14, 2020 8:43 AM
    Moderator