This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
[Note] This thread was originally posted on MSDN. As the MSDN Exchange Dev forum mainly focuses on developing issues and the TechNet Exchange forums for general questions have been locked down, we manually migrated this one to Microsoft Q&A platform to continue the troubleshooting.
Hi everyone.
We encountered a very strange bug with exchange search.
Context:
Outlook working in on-line mode (running on terminal servers, so we can`t chnage it to cached mode due high IO)
When user get message with any attached file AND forward it, the message disappears from the search results. Outlook search showing forwarded message from "SENT" folder, but do not showing original message in "INBOX"
There is an example on sreenshot
as you can see, search showing only 3 results, while we have 4 messages (2 in inbox, 2 in sent).
OWA have same issue.
Users do not use Conversation View, as some correspondence may contain dozens of messages that are difficult to view in this form.
This problem appear after upgrading to Exchange 2019 (CU3) from 2016. Now we installed CU8, but this bug still here...
Has anyone encountered a similar bug?
Hi @Antoл K and @MarcoMandricardo-1414 ,
I want to confirm with you that when using MFCMAPI to view the original email with the problem, is the parameter "BigFunnelCorrelationID" empty?
Looking for your feedback.
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Helo, Lucas! I don`t find this attribute in original message (in Inbox). Message in Sent folder has this attribute, in Inbox - no.
hi @Lucas Liu-MSFT
i confirm that on an item just recived, i have the parameters, but after forwarded them, it's gone. here the screenshot about my test:
email just arrived:
email after forwarding
after you confirm the bug, there is a hotfix for repair search on all email recived and forwarded that has lose this parameters?
Hi @Antoл K and @MarcoMandricardo-1414 ,
Thank you very much for the information.
Combined with the current information, we still cannot determine that the issue must be a BUG. I am doing more testing in the specific CU version of Exchange 2019 you provided to determine the root cause.
If there is any progress, I will update it in this post immediately.
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
thank you @Lucas Liu-MSFT ,
what other kind of thing could be causing this problem then?
we are testing and evaluating the solution with outlook cache enabled in the meantime
Hi @MarcoMandricardo-1414 ,
Taking into account the particularity of this problem, we are currently unable to confirm what caused this parameter to be changed. We are doing more tests in different versions of Exchange 2019 experimental environment. thank you for your patience.
As a wrokaround, if possible, you can temporarily enable oulook cache mode to avoid this problem.
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Sign in to comment
11 answers
Sort by: Most helpful
Hi ,
Do you have this issue with forwarding emails without attachments?
After forwarding, can you see the original mail in your mailbox?
Only one user have this issue or all have?
2.Confirm that the database where the user is located has search index enabled, and the value of IndexEnabled should be true by running: Get-mailbox <user name> | fl name,database
Get-MailboxDatabase <db name> | fl Name,IndexEnabled
3.Check the status of the database and content index by running below command. If ContentIndexState shows FailedAndSuspended or Failed status, try to rebuild the database content index directory.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Antoл K ,
Do suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Thanks for your understanding.
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
No. Please, see my comment below.
Hi @Antoл K ,
Does the check have any results?
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi @Antoл K and @MarcoMandricardo-1414 ,
Regarding this issue, we are conducting internal discussions and testing in more environments to reproduce the problem. If we have any update, I will update it in this post immediately.
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Sign in to comment
Without attachments search working fine, you can see it on screenshot.
After forwarding - yes, the original message exist in inbox, but search don`t showing it.
Only one user - no, all users, also i have tested this bug on 3 installations of Exchange Server 2019 in different Active Directory forests.
P.S. Mailbox migration from one MDB to another fix issue with exsiting messages. But after migration new emails having same problem.
Hi @Antoл K ,
Do you have the same problem if you search through other information? E.g. sender
What problems did you encounter when restarting these two services?
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Search by sender returns same result. Message with attachment don`t showing in inbox, only in sent items.
What problems did you encounter when restarting these two services? - Did not quite understand the question. We have restarted the services in the hopes that this will fix the search problem. It did not help.
Hi @Antoл K ,
According to my research, this issue probably caused by BigFunnel.
1.Please run the following command to check whether the bifFunnel is enabled and whether any items are not indexed.
2.You can check the attributes of the email by using MFCMAPI. The attribute value of "0x365A0003" of normal email is "0".
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Lucas. Sorry for the long silence.
Powershell output about test account:
BigFunnelIsEnabled : True
BigFunnelNotIndexedSize : 558.9 KB (572,325 bytes)
BigFunnelNotIndexedCount : 10
I checked the attribute "0x365A0003"
When message arrived it showing 0. But after forwarding original message got "3" value.
Screenshots attached.
P.S.: Message in "Sent items" folder have normal value "0"
any update or solution?
Hi @ANTON KARAPUTIN ,
According to the output of the command line, we could know that this issue is caused by BigFunnel.
According to my test in Exchange 2019 lab environment, the attribute “0X365A0003” of the original message before and after forwarding both showing 0. And according to some of my recent searches and research, I found there is a bug in Exchange 2019 beta version. The attribute “0x365A003” will changed and the message couldn’t be searched after forwarding the original message. But it’s has been resolved.
Considering the particularity of search methods in Exchange 2019, have you tried to create a new database? If not, please try to create a new database and migrate one user mailbox to it, then check after migration new message whether have the same issue.
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Hello, Lucas!
I created new MDB and new user in this db. Unofrtunately, it does not helped. Absolutely identical situation.
hi @ANTON KARAPUTIN and @Lucas Liu-MSFT
i have the same issue,
now i check the value of item and post my result
it's possible the bug it's come back @Lucas Liu-MSFT ?
Sign in to comment
hi,
we have a problem like this, but with all mail,
if the first action is forward, the next search always don't display it in inbox folder search.
we have this scenario:
Exchange 2019 CU7 Version 15.2 (Build 721.2)
with outlook in online mode because of RDP server
Microsoft Outlook 2016 (16.0.5110.1000) MSO (16.0.5110.1001) 32bit
i have check bifunnell search index and i have 0 element not index. but the problem is still here.
someone has microsoft support for ask a solution?
please not tell me to use cached mode. i have an RDP farm.
Hi @MarcoMandricardo-1414 ,
Did you try the methods provided above? Such as migrate the user mailbox to another database.
What is the result？
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
hi @Lucas Liu-MSFT ,
migrate mailbox to another db resolve element not indexed, but not resolve this issue about search from outlook in online mode, just after forwarded, it disappear from research result.. it's a real time bug, one moment before research show it in the result, i forwarded it to a contact, internal or external doesn't matter, search again and there is no more the original message in the result.
it seems that forward a message change it's property and hide it from reasearch.
it's a big problem beacouse we have an RDP farm, and all user use outlook in online mode, we can't enable cache in RDP.
ps sorry for my english
Hi @MarcoMandricardo-1414 ,
Please use MFCMAPI to check whether the value of parameter "0x365A0003" will be changed after forwarding your email in the way I provided above.
In addition, after trying to migrate the problem user to a new database, does the problem persist?
----------
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
hi @Lucas Liu-MSFT and @ANTON KARAPUTIN
we have the same issue, here the test:
item just recived with correct parameters, and research ok:
after forward email from outlook in online mode parameters change to val 3:
so we check the bug is come back, could you please confirm that and tell us how to resolve?
after that i enable cache mode on the same outlook.. i sent another mail, and forwarded and the issue doesen't show:
We have a fix: use cache don't cause the problem... but for the earlier mail ? we have a lot of email with parameters 3 that we can't find in online and cache mode
Sign in to comment
Hi @Lucas Liu-MSFT , сan you please tell me if there is any information about the bug over the past month? Is the issue reported as a bug? There will be a new CU coming soon, it would be great to get a bug fix in it.
Sign in to comment
Hi @MarcoMandricardo-1414 , @Antoл K
In the past month, I have installed several Exchange 2019 CU versions that you mentioned as having issue. And many experiments have been carried out in the environment, but unfortunately we have not been able to successfully reproduce your problem. In addition, I also searched and researched cases of search problems caused by BigFunnel, but no specific solutions were found in the cases.
Considering that the problem has already affected your actual use, in order to further investigate the root cause of the problem, it is recommended that you open a case with Microsoft for further investigation.
If you successfully solve the problem, you can also share your solution here. This will be beneficial to other community members as well.
I will continue to test and research to find more relevant information.
Sign in to comment
Activity