I'm occassionallyreceiving errors like this in the Application log on both of my Exchange 2007 servers. Does anyone have any information on this error? Event Type:ErrorEvent Source:MSExchange Search IndexerEvent Category:General Event ID:115Date:12/11/2007Time:8:51:44 AMUser:N/AComputer:XXXXXXXDescription:Mapi protocol handler encountered an unknown exception obtaining message content from : MDB a4ea2ce3-2121-4e7c-99ad-bdcc2d12189a, Mailbox d2b11b30-4cf4-44af-b4ba-e3b9819f8c7f, DocumentID 109588, EntryID System.Byte[]. The exception is: Microsoft.Mapi.MapiExceptionNotFound: MapiExceptionNotFound: Unable to open property 0x37010102 (Interface 0000000c-0000-0000-c000-000000000046, Options 0) with flags ReadOnly. (hr=0x8004010f, ec=-2147221233)Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=82] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=194][latency=0] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropOpenAttach [34] Lid: 27962 ROP: ropOpenStream [43] Lid: 17082 ROP Error: 0x8004010F Lid: 24673 Lid: 21921 StoreEc: 0x8004010F Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropOpenStream [43] Lid: 24633 Lid: 5076 StoreEc: 0x8004010F PropTag: 0x37010102 Lid: 28737 Lid: 7540 StoreEc: 0x8004010F PropTag: 0x37010102 Lid: 21569 Lid: 24641 StoreEc: 0x8004010F Lid: 23617 Lid: 5326 StoreEc: 0x8004010F Lid: 25025 Lid: 18881 StoreEc: 0x8004010F Lid: 1750 ---- Remote Context End ---- Lid: 31418 --- ROP Parse Done --- Lid: 25793 Lid: 23873 StoreEc: 0x8004010F Lid: 23097 Lid: 19001 StoreEc: 0x8004010F at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo) at Microsoft.Mapi.MapiProp.OpenProperty(PropTag propTag, Guid interfaceId, Int32 interfaceOptions, OpenPropertyFlags flags) at Microsoft.Mapi.MapiProp.OpenStream(PropTag propTag, OpenPropertyFlags flags) at Microsoft.Exchange.Search.MapiIterator.<GetContents>d__0.MoveNext() at Microsoft.Exchange.Search.MapiChunkSource.GetNextChunk(IntPtr chunk). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

We're getting the exact same thing on our Mailbox server. Have you recently upgraded to 2k7 SP1? I didn't see this until recently, after we had upgraded. It wasn't instant though, a week or two have gone by before I saw it.What's really crazy is that other than the two GUIDs (MDB guid and Mailbox guid) our message reads EXACTLY the same as yours, with the same error codes on the "Lid:" lines, etc.

Hi! We have the same error after installing SP1 for Exchange Server 2007. Did you find any solution for this issue? Best Regards Cicek

I am having this issue, but be aware that my GUIDs are different. What seems to have remedied the issue for the time being (since I made this change anyway) is the following: A. Stop the MSExchange indexer service and Microsoft Search (Exchange) service. B. In the data folder of each store in windows explorer look for a catalog folder which has this GUID: 32acdb23-29c0-41da-aac8-1c1e8f3c4d99 appended to it (that was my GUID, obviously look for the folder with the GUID reported in your error message). C. Delete that catalog folder. Now start the Microsoft Search (Exchange) service again, leaving the MSExchange indexer service stopped. I went so far as to actually disable it altogether.

This looks promising. I'm guessing that you're effectively blowing away the catalog and recreating it.However, there's a Technet page that explains what the services do, and leaving what you called the MSExchange indexer ("MicrosoftExchange Search Indexer") stopped probably isn't the best thing, because you're effectively breaking full-text search of Exchange.Services Installed By Microsoft Exchange Setup (2007) [From Technet]MSExchangeSearch -- Provides content to the Microsoft Search (ExchangeServer) service for indexing. This service is dependent upon the MicrosoftExchangeActiveDirectory Topology service and the Microsoft Search (ExchangeServer) service.MSFTESQL-Exchange [The Microsoft Search (Exchange) service] -- Provides full-text indexing of mailbox data content. This is a MicrosoftExchange-customized version of Microsoft Search. This service is dependent upon the Remote Procedure Call (RPC) service.So, if you disable MSExchangeSearch, the MSFTESQL-Exchange service won't actually get any data to index, and your search will be broken.Since the errors are COMING from the MSExchangeSearch service, and judging from the content of the messages, what's happening is that the service is barfing on something in the store itself, some piece of data that it can't index for some reason. This seems like either an unexpected bug (the service should skip gracefully instead of dumping error codes) or expected behavior (it dumps errors so you know it is skipping something). We'll need an Exchange team member to tell us more though... One would hope that if it is EXPECTED behavior, there's a way to shut off the event log entry for it because it gets pretty spammy.

Any news/solutions about this error ?

Anybody have any luck yet with this error? Rebuilding the search indexes does NOT fix the problem for me (and for others judging by similar postings on experts-exchange, etc.)

Without sounding like I am bandwagoning, I too am also having this error. It began approximately two weeks after I installed SP1 to my Exchange 2007 server. This error pops up about once a week and other than being annoying, does not yet appear to affect anything I know of or can find. I am using one Exchange server with the three roles assigned: hub transport, client access and mailbox.

This error started immediately after I finally got SP1 applied (after 4 hours of torture) and is popping up 20+ time per minute. We have been up about 9 hours. The trouble started 1/2 way through the upgrade when the server suddenly rebooted. I watched in horror and spent the next 4 hours reading blog articles, hacking the registry, and running setup.com /mode:upgrade, and waiting on hold for Microsoft support. I finally resorted to v8.0 registry key I exported before starting the upgrade. That, plus yet another reboot, and the GUI setup ran to completion.I'm afraid to touch a thing at this point.We have just the one Exchange server;small shop. As soon as I can get through to Microsoft support, I'm letting them deal with this because my brain is not working very well at this juncture. Event Type:ErrorEvent Source:MSExchange Search IndexerEvent Category:General Event ID:115Date:3/21/2008Time:7:45:02 AMUser:N/AComputer:IBM3650-EMAILDescription:Mapi protocol handler encountered an unknown exception obtaining message content from : MDB 030e75ce-03dd-4fb7-8691-796f8b2f34c7, Mailbox a6057147-0b78-4a68-9d3a-f8d39de7c963, DocumentID 90271, EntryID System.Byte[]. The exception is: Microsoft.Mapi.MapiExceptionUnknownUser: MapiExceptionUnknownUser: Unable to make connection to the server. (hr=0x80004005, ec=1003)Diagnostic context: Lid: 23065 EcDoConnectEx called [length=189] Lid: 17913 EcDoConnectEx returned [ec=0x3EB][length=56][latency=0] Lid: 19778 Lid: 27970 StoreEc: 0x3EB Lid: 17730 Lid: 25922 StoreEc: 0x3EB at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Int32 ec, DiagnosticContext diagCtx) at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName, Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize) at Microsoft.Mapi.ConnectionCache.OpenMapiStore(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, ClientIdentityInfo clientIdentity, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId) at Microsoft.Mapi.ConnectionCache.OpenMailbox(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, ClientIdentityInfo clientIdentity, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId) at Microsoft.Exchange.Search.MailboxCache.GetMailbox(ServerMdbAndMailboxGuids guids) at Microsoft.Exchange.Search.MapiChunkSource.GetMapiStoreFromCache() at Microsoft.Exchange.Search.MapiChunkSource.GetMessageFromDocumentId() at Microsoft.Exchange.Search.MapiChunkSource.GetNextChunk(IntPtr chunk).

I've had a ticket open with Microsoft about this for some time now. This is where it currently sits: "I apologize for the delayed response. There has been other customers that have experienced this same event id. The good news is that we are now able to repro the event id. So far, it has been determined that some process is deleting a message property which causes the Search Index process to error when try to read the delete message property. It is unclear what process can be deleting this property. We are able to delete this property only by using internal tools. Since our test Exchange servers does not have any 3rd party applications, we can only suspect some 3rd party process is accessing message properties on random users. A bug has been filed to have Development to further investigate the event id."

Try this,maybe can fix the problem... OpenSettings --> Control Panel --> Add / Remove Programs. Search the Microsoft Full Text Indexing for Exchange. Click on "click here for support information." and click on Repair button. After that a reboot is notrecommended,but I did it anywhere. have a good day Ettore

Hi all, 2 weeks (roughly) since anyone has responded to this thread. Have been watching it with interest as we are also suffering from the same problem. Have installed SP1 and Update Rollup1 for good measure. Any joy with this? thanks.

I ran a complete, offline defrag of my mailbox database along with isinteg and still the problem persists. I also tried the steps proposed by Ettore Roversi to no avail. Reporting this back to Microsoft, I received the following response: The bug that was opened for this problem is still active and being investigate by Exchange development. I'll provide an update as soon as we get a response from Dev. Sorry for the delay.

I have noticed this same exact (except for the GUIDs of course) error. This only happens on one mailbox, and only when that user sends an e-mail to one particular external recipient, the error is generated when the read reciept comes back in. I believe that recipient is using a web access type mail client on their ISP (a neighborhood cable company). Just thought that I would add this in case it helps anyone solve this issue.

Has anyone come up with a solution? My Exchange 2007 server has this error. I installed SP1 two months ago and haven't noticed any ill effects (until now). Doesn't seem to be effecting anything (yet). This error started happening over the weekend and no changes were made to teh server.

Status of the case Event SearchIndexer:115 is new to Exchange 2007 SP1. It may be indicating issues that were in your environment all along, but were not exposed in the form of event. This event was introduced to help us catch unexpected crashes of indexing process. As understand you were not exposed to the unexpected crash issue. Unfortunately this event does not distinguish between critical issues and exception that we may recover from. Looking through the data that you provided I see that all of events 115 reported in your environment are of a later kind. Events that report: MapiExceptionNotFound: Unable to open property 0x37010102 are not critical and are not indicative of any problem that we should be worrying about. Cause and Resolution In collaboration with engineers from the Exchange product group I learned that these events are due to a recently discovered issue. The issue is that information store allows messages to have empty attachments. Causing MAPI_E_NOTFOUND error code to bubble up to Search Indexer in cases when attachments body is empty. This may be a result of AV software stripping message attachments. This issue is currently being worked on. Unfortunately, the fix may require somewhat destabilizing code change, so product group is not likely to attempt the fix before next service pack. In the mean time, I have filed another hotfix request. The nature of my request is to prevent Search Indexer from treating problems associated with this known issue as critical errors. This is much simpler fix. It should prevent false-positive error events from being logged. If everything goes smooth we should have the fix in SP1 RU3. Plan 1. Wait for Rollup Update 3 for Exchange 2007 Sp1. OR 2. Request an Interim Update that may be used to implement a temporary relief while waiting for RU3.

Hi Folks, We're having the same issue, here's our environment: Exch 2007 recently upgraded to SP1 (2 weeks ago) 2 x CAS 2 x HT 3 x MB consisting of2 x CCR Node and 1 SCR node 1 DB currently at 175GB Backup Exec 12D backing up the passive CCR node Recent work carried out: Transaction logs moved to new LUN CCR node DB re-seeded (update-storagegroupcopy) SCR node installed and seeded Yesterday whilst seeding the SCR node users started reporting slow response times in Outlook 2007, same events present in the event logs, today the same thing has happened - sluggish performance varying in length of time, during which the information store seems to be unavailable. Here's the events: Event Type:ErrorEvent Source:MSExchange Search IndexerEvent Category:General Event ID:115Date:10/06/2008Time:11:22:22User:N/AComputer:myCompNameDescription:Mapi protocol handler encountered an unknown exception obtaining message content from : MDB 938dfb45-f621-406a-ac2b-1fdd061adb9c, Mailbox d9b6c7d0-0cef-425b-99b9-609fd3c9b814, DocumentID 2665366, EntryID System.Byte[]. The exception is: Microsoft.Mapi.MapiExceptionNotFound: MapiExceptionNotFound: Unable to open property 0x37010102 (Interface 0000000c-0000-0000-c000-000000000046, Options 0) with flags ReadOnly. (hr=0x8004010f, ec=-2147221233)Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=103] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=206][latency=0] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropOpenAttach [34] Lid: 27962 ROP: ropOpenStream [43] Lid: 17082 ROP Error: 0x8004010F Lid: 24673 Lid: 21921 StoreEc: 0x8004010F Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropOpenStream [43] Lid: 24633 Lid: 5076 StoreEc: 0x8004010F PropTag: 0x37010102 Lid: 28737 Lid: 7540 StoreEc: 0x8004010F PropTag: 0x37010102 Lid: 21569 Lid: 24641 StoreEc: 0x8004010F Lid: 23617 Lid: 5326 StoreEc: 0x8004010F Lid: 25025 Lid: 18881 StoreEc: 0x8004010F Lid: 1750 ---- Remote Context End ---- Lid: 31418 --- ROP Parse Done --- Lid: 25793 Lid: 23873 StoreEc: 0x8004010F Lid: 23097 Lid: 19001 StoreEc: 0x8004010F at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Object objLastErrorInfo) at Microsoft.Mapi.MapiProp.OpenProperty(PropTag propTag, Guid interfaceId, Int32 interfaceOptions, OpenPropertyFlags flags) at Microsoft.Mapi.MapiProp.OpenStream(PropTag propTag, OpenPropertyFlags flags) at Microsoft.Exchange.Search.MapiIterator.<GetContents>d__0.MoveNext() at Microsoft.Exchange.Search.MapiChunkSource.GetNextChunk(IntPtr chunk). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. And: Event Type:WarningEvent Source:MSExchangeIS Mailbox StoreEvent Category:Views Event ID:1173Date:10/06/2008Time:11:29:51User:N/AComputer:myCompNameDescription:Error 0x6bb deleting unused restricted view from folder 1-1AD0D9BC80 on database "First Storage Group\ExchangeDatabase". Microsoft Exchange Information Store will try to delete the view again at the next maintenance interval. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. One thing we noticed was that the beremote service (backup exec remote agent) was leaking memory and was sat at 4.9GB, Exchange was using 5GB when store.exe is usually more along the lines of 10GB, could be a red herring. We also saw a couple of SCSI bus resets. Is anyone else using backup exec? Keep us posted guys, Gareth.

I'm experiencing the exactly same issue here.Basicly waiting for Update Rollup 3 for SP1. So far only few errors reported for two user mailboxes. However, the said users mentioned they haven't removed any attachments. In addition we _are_ using Backup Exec 12 with GRT enabled. The error concerning deleting unused restricted views can safely be ignored as per Microsoft's KB article. http://support.microsoft.com/kb/913126

We installed Update Rollup 3 for SP1 and are still seeing this error.

We were using Exchange 2007 SP1 for several months, but this error began when we installed Update Rollup 3 for Exchange 2007 SP1. A solution would be appreciated.

For what it's worth, we run both Blackberry Enterprise and Good Mobile Messaging against our Exchange store, so possibly one of those two apps is what is deleting this "special" message property...?

Hi Everyone. We too are experiencing this Event ID occurring on a frequent basis. An earlier post mentioned the removal of a particular MAPI property relating to or at least referencing the removal/attachment blank scenario. I wondered if anyone is running an archiving solution on their plant? If so and the archiving solution is set to remove attachments from the mail and leave a stub message for retrieval of the message does anybody know if this is a potential cause for the MAPI property to be found missing/blank?

Hello - just came across this posting as I'm having same issue. Above, someone mentioned that some process is deleting properties, they are not sure which process, etc. and they do not have 3rd party apps that would be doing this. I have no idea if this is related, but we've noticed an ocassional event (info) indicating that"A named property has been created for the database ...". From other articles I've read on this, seems this info event is caused by virus scan or spam blocking on Exchange Server. BTW ... we have E2K7 SP1 + Rollup 3 installed. Is there any chance that this "new named property" is causing issues with the Search Indexer?

I've been dealing with this issue since 2K7 RTM. VERY ANNOYING! Common MS, please provide fix this is been going on way too long.....Furthermore, "ignore it sinceits not effecting anyone" is not a solution. It effects Admins who browse event logs looking for errors or problems.

Event ID 115 may be logged intermittently on a computer that is running Exchange Server 2007 with Service Pack 1 http://support.microsoft.com/kb/950976 Install Update Rollup 4 for Exchange Server 2007 Service Pack 1

We are not yet on Rollup 3. We receive many 115 and 1173 messages amongst others, but 1173 seems to occur as much as any (also many 9646, but I don't believe those are actually critical to other issues we are experiencing at this time). We also run EMC Email Xtender (for archiving) and Blackberry Enterprise.In addition to those logged entries, this past weekend our monitoring system was frequently alerting us about the CPUs being over 90% utilized on the Exchange mail server (CCR Cluster). While there are other log entries, nothing stands out as to an obvious reason why the CPU alerts were sent.I have read online (with respect to 1173) that there were suggestions that offline defrags may assist, but perhaps that was with respect to Exch 2003. But I see someone tried that to no avail. The likely culprit is BES. Some BES forums/blogs suggested to change registry settings on the Exchange server... MaxObjsPerMapiSessionHKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\MaxObjsPerMapiSessionDefault is 500...we have increased, but will require a restart on the system.

After Updating to rollup 4 we are still getting the following: Mapi protocol handler encountered an unknown exception obtaining message content from : MDB f9d9b3a9-be22-4220-9218-f5c145eb6a84, Mailbox e2a20f28-de06-4866-8382-627470a7bdbe, DocumentID 983389, EntryID System.Byte[]. The exception is: Microsoft.Mapi.MapiExceptionNotFound: MapiExceptionNotFound: Unable to open property 0x37010102 (Interface 0000000c-0000-0000-c000-000000000046, Options 0) with flags ReadOnly. (hr=0x8004010f, ec=-2147221233) Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=82] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=194][latency=0] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropOpenAttach [34] Lid: 27962 ROP: ropOpenStream [43] Lid: 17082 ROP Error: 0x8004010F Lid: 24673 Lid: 21921 StoreEc: 0x8004010F Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropOpenStream [43] Lid: 24633 Lid: 5076 StoreEc: 0x8004010F PropTag: 0x37010102 Lid: 28737 Lid: 7540 StoreEc: 0x8004010F PropTag: 0x37010102 Lid: 21569 Lid Which is eventid 115 , any other solutions known? Regards DC

Same problems here. Has anyone opened a ticket with MS?Eric

Eric, No I havent opened a case with MS , I believe the only solution I seem to find in forums is to install the update roll up packs but that hasnt work, now recently I have installed rollup update 5 and atleast uptill now I haven't recieved the error.. but I'll wait a week to see if the error appears again. If you find another solution please let me know. Regards, Dale

All,I've been dealing with PSS since 08/2009 about the event 115 issie and here is the final (so far) result:Event 115 is triggered by a bug in the index service. (NOTE after RU4 for Exchange 2007 SP1 the events 115 are not more logged, but problem still occurs. The Eventlog level for the Indexer has to be raised from Powershell to get the error again).What triggers the issue:A mail has a mail attached. The attached mail has a document attached and the subject is the name of doc (e.g.: my document.doc). The attached doc is pretty much anything but a PDFIf all these conditions are true, then the indexer has trouble to index, the event 115 will be logged (or not..depending of the log level), and the mail is NOT indexed, and will not be found using the quick search.People using Outlook and Exchange Xache mode will still find the mail as cache mode triggers the client indexing (but they won't find the mail from OWA).The Exchange Product team has denied the development of the fix . So bug willstay unless enough people are logging a call... How nice is that,Chris

Hi all. I have just had this error on one of our Exchange 2007 clients. The problem was the way the cluster was created and thus how the services were started. The service: "Microsoft Search (Exchange)" was started as 'local machine' and the service: "Microsoft Exchange Search Indexer" was started with the virtual cluster name. This created the conflict. As soon as we started Microsoft Search (Exchange) with the Virtual Cluster Name, all started OK

To resolve this problem, download Update Rollup 4 for Exchange Server 2007 Service Pack 1. For more information about Update Rollup 4 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=152556) /* Windows Infrastructure Support Engineer */

But if you're going to do that, you might as well load Update Rollup 9. Or install Service Pack 2, and then Update Rollup 3. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Albert Widjaja" wrote in message news:48858e19-6213-4e0e-8994-fe0e4f035f2c... To resolve this problem, download Update Rollup 4 for Exchange Server 2007 Service Pack 1. For more information about Update Rollup 4 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=152556) /* Windows Infrastructure Support Engineer */Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."