none
Windows Search Service error

    Question

  • EventID:3083
    Category: Gatherer
    Description:
    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered

    Search continues to work yet there errors keep appearing in the Application Event Log. Any clue on how to get rid of them.

    Running on Windows Standard x64 Server 2003, with terminal services in application mode.
    Sunday, November 19, 2006 8:34 AM

Answers

  • I found the following registry key was missing - imported it from another computer that didn't have the problem and the problem went away.

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}]
    @="Windows Search Service Office Outlook Protocol Handler"

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\InprocServer32]
    @=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,74,00,25,\
      00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,73,00,\
      73,00,70,00,68,00,2e,00,64,00,6c,00,6c,00,00,00
    "ThreadingModel"="Both"

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\ProgID]
    @="Search.MAPI2Handler.1"

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\VersionIndependentProgID]
    @="Search.MAPI2Handler"

     

    Wednesday, November 22, 2006 9:32 AM

All replies

  • "Date: 21/11/2006
    Source: Windows Search Service
    Time: 10:59:27
    Category: Gatherer
    Type: Error
    EventID: 3083

    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered"

    Having the exact same error message, your not alone.  Running Windows XP x64 SP1. Search is fully functional however.
    Tuesday, November 21, 2006 11:37 AM
  • I found the following registry key was missing - imported it from another computer that didn't have the problem and the problem went away.

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}]
    @="Windows Search Service Office Outlook Protocol Handler"

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\InprocServer32]
    @=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,74,00,25,\
      00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,73,00,\
      73,00,70,00,68,00,2e,00,64,00,6c,00,6c,00,00,00
    "ThreadingModel"="Both"

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\ProgID]
    @="Search.MAPI2Handler.1"

    [HKEY_CLASSES_ROOT\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\VersionIndependentProgID]
    @="Search.MAPI2Handler"

     

    Wednesday, November 22, 2006 9:32 AM
  • Same problem here  . . . and noticed perfmon getting a lot of Exception Dispatches/sec which may be related.

    I wonder if you may have used a "registry cleaner" and that may have Removed the class registration?

    I used a "cleaner", but looked over most of what was being cleaned and approved the cleaning decisions.  If you did not use a cleaner, I can rest easier.

    Steven Bland

    Monday, January 01, 2007 11:06 PM
  • I did not use any registry cleaning tools and am still receiving the above mentioned errors.  Not quite ready for the "leap" to Vista just yet, x64 XP still has a lot of life left in it. Roll on x64 SP2 I say :)
    Thursday, January 04, 2007 8:07 AM
  • I have the same error - x64 / office 2007 / WDS 3.

    It is absolutely refusing to index pst files - the event log reads:

    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered

    in parallel outlook is spamming:

    Failed to determine if the store is in the crawl scope (error=0x80040154).

     

    Monday, February 19, 2007 1:36 AM
  • This was also an issue on 64-bit Vista and we made a fix for it, but it looks like the fix did not correctly address 64-bit XP.

    The background on this issue is that there are two process that can index on 64-bit machines. One process is 64-bit and can load 64-bit protocol handlers and the other is a 32-bit process which can load 32-bit protocol handlers. In this case, since mapi (which is used to index outlook email) is 32-bit only, when the 64-bit protocol handler process starts, it tries to load the 64-bit version of the non-existent mapi protocol handler. It should call into the WOW64-32 layer to determine that this handler is correctly registered in the other CLSID hive and not display the error. For some reason this check is not passing, most likely due to some incompatible vista only flag we are using when calling to WOW64.

    The good news is that this error message will not impact email indexing, but will create event messages every time the protocol handler starts up.

    Tuesday, February 20, 2007 1:29 AM
  • X64 SP1 /office 2007    (not sure what WDS 3 is)

    I am getting the same problem, it happened after I installed office 2007, I have been running 64x for 2 years and this is a real pain, the error window pops up every few seconds for 10 or 15 minutes after I reboot the machine.  It seems to stop after 30 or 40 error dialog pops.   If I leave the system on I do not seem to have the problem.

     

    I checked my registry and all the entries are there accourding to one of the above posts

     

    Monday, March 05, 2007 11:16 PM
  •  

    The first issue is benign "The protocol handler Search.Mapi2Handler.1 cannot be loaded", this is because the 64-bit protocol handler can't load MAPI which is 32-bit only. This is OK, because the 32-bit protocol handler will load it correctly. (see my post above).

    As for the dialog box, I forward this thread to the outlook team for investigation.

    Tuesday, March 06, 2007 6:42 PM
  • Could you give us more information about the dialogs you're seeing popping up?  Please provide the title and text of the dialog.

    Thanks,

     - Michael Hilsdale

       Outlook Search Team

    Tuesday, March 06, 2007 9:20 PM
  • I'm getting nasty dialogs (the regular debug dialogs) whenever this error happens. It keeps asking me whether I'd like to debug the exception.

     

    I'm running Windows 2003 Server Enterprise SP2.

    Wondows Desktop search

    Office 2007

     

    Kindly let me know if there's a patch available for this...

     

    Monday, April 16, 2007 5:57 PM
  • You need to provide more info on this issue before anyone can help.
    Monday, April 16, 2007 11:09 PM
  • Great explanation but this is causing a problem with installing a patch to BF2142 1.25.  Everytime I run the installation it bombs and post this error in the event log.  Any suggestions

     

    Thursday, April 26, 2007 1:55 AM
  • Importing the registry entries you suggested stopped the errors from occurring. Thanks!
    (It was getting annoying trying to track down my real errors in the event log with all those windows search service errors.  Even though they don't "hurt" anything, a windows update that includes this would be nice).
    Friday, June 15, 2007 7:17 PM
  •  

    I am running Windows XP X64 and get the following error:

     

    The protocol handler Search.Mapi2Handler.1 cannot be loaded.

     

    I have MS Office 2007, and the outlook install the Windows Desktop Search for Windows XP SP2

     

    I solve this isue, unistalling the previus version of the Windows Desktop Search and installing the correct version of the Windows Desktop Search X64 edition, You can download it from:

     

    http://www.microsoft.com/windows/desktopsearch/downloads/default.mspx#wds1

     

    I hope this work for the rest

    Friday, June 29, 2007 12:15 AM
  • I was receiving the same error as being discussed in this topic:

    Running:
    Microsoft Windows XP x64 SP2

    I tried to uninstall WDS and reinstall the x64 version but that did not correct the error.

    I then imported the registry key that the above user stated from a fresh pc and that solved the error.  Thank you for your help.
    Friday, September 14, 2007 4:18 PM
  • This solution solved my problem.  Thank you!

     

    I started having this trouble when I had to re-install WDS 3.01.  I could NOT use add/remove programs to uninstall as it said it encountered an error.  However, Once reinstalling I had the awful problem.  Adding these Registry Entries to the registry solved the problem.  I use XP Pro x64 with SP2.

     

    hth,

    Kingofbytes

     

    Thursday, October 25, 2007 1:00 PM
  • Hello everybody,

     

    I am getting the same error on XP X64 (english) w/ Outlook 2007 SP1 (german language version), but the problem seems to persist even after additional uninstall/install cycles. The registry key mentioned by another poster is NOT missing.

     

    For you further reference I am getting the following error msgs in the log:

     

    (1) Error

    Event Type: Error
    Event Source: Windows Search Service
    Event Category: Gatherer
    Event ID: 3083
    Date:  14.01.2008
    Time:  11:50:33
    User:  N/A
    Computer: [deleted]
    Description:
    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered

    (2) Warning

    Event Type: Warning
    Event Source: Windows Search Service
    Event Category: Gatherer
    Event ID: 3036
    Date:  14.01.2008
    Time:  11:59:40
    User:  N/A
    Computer:
    Description:
    The content source <mapi://{s-1-5-21-851995528-991508498-840520217-1120}/> cannot be accessed.

    Context: Windows Application, SystemIndex Catalog

    Details:
     A server error occurred. Check that the server is available.   (0x80041206)

     

    (3) Error

    Event Type: Error
    Event Source: Windows Search Service
    Event Category: Gatherer
    Event ID: 3024
    Date:  14.01.2008
    Time:  11:59:40
    User:  N/A
    Computer:
    Description:
    The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

    Context: Windows Application, SystemIndex Catalog

     

     

    Is this problem already filed in the MSFT bug list and will there be a patch soon? Otherwise we would have to uninstall this app from all our x64 pcs.

     

    Thanks

    --fhg'ler

    Monday, January 14, 2008 11:23 AM
  • I am also getting the following error:

     

    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered

    .

     

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    This is on a Windows  Standard x64 Server 2003 Running Exchange 2007 SP1. I started receiving this error once I upgraded my exchange 2007 server to SP1. I am also getting another error message that is related to this issue after my upgrade to SP1.

     

    Event ID: 115

    Source: MSExchange Search Ind

     

    Mapi protocol handler encountered an unknown exception obtaining message content from : MDB 2bb19832-6fd6-48a8-aee0-dfe0de7479c6, Mailbox 03fc0a69-0603-4bd7-9c62-6b3edadfd4d1, DocumentID 144304, 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

     

     

    Has anyone else had this problem after installing Exchange 2007 SP1 and know of a soultion?
    Tuesday, January 29, 2008 11:06 PM
  • I am getting this error:

     

    The protocol handler Search.OneIndexHandler.1 cannot be loaded. Error description: The specified module could not be found. .

    I error out when trying to install office 2007 on Win XP on my laptop.  How do I fix
    Wednesday, January 30, 2008 7:15 PM
  • I am seeing the same error on our CCR clsuter Exchange 2007 server's but till now did not find any solution.

    Any help will be appreciated
    Sunday, February 24, 2008 9:40 AM
  • We just upgraded to Exchange SP1 and receiving the error too. Any suggestions?

     

    Mapi protocol handler encountered an unknown exception obtaining message content from

    Event Type: Error

    Event Source: MSExchange Search Indexer

    Event Category: General

    Event ID: 115

    Date: 2/27/2008

    Time: 11:24:38 AM

    User: N/A

    Computer: MBNODE1

    Description:

    Mapi protocol handler encountered an unknown exception obtaining message content from : MDB 9859c602-c49e-40d2-a97b-f67a80d35961, Mailbox 5b26548c-fd28-4f07-94cd-75f6da16d5d6, DocumentID 382056, 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.

     

    Thursday, February 28, 2008 1:24 AM
  • This may be the fix: went to control panel, add remove programs, found the Microsoft Full Text Indexing Engine for Exchange, and repaired. The errors are now gone.

    • Proposed as answer by SMF1474 Friday, July 02, 2010 5:28 PM
    Friday, March 07, 2008 10:15 PM
  • I hope that was indeed the solution for you,  . . . however I do not have the Indexing Engine for Exchange and am still getting the

    "

    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered

    "

    error in my system log.

     

    Steve

    Tuesday, May 20, 2008 12:27 PM
  • Eric,

     

    Can you point me to the Vista Hotfix?

     

    Thanks,

     

    Jeff L

    Saturday, August 09, 2008 2:23 PM
  • This problem also exists in Windows Search 4.0, Windows XP x64 SP2, Office XP SP3.

    Saturday, August 16, 2008 3:36 PM
  •  TimElvidge wrote:
    EventID:3083
    Category: Gatherer
    Description:
    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered

    Search continues to work yet there errors keep appearing in the Application Event Log. Any clue on how to get rid of them.

    Running on Windows Standard x64 Server 2003, with terminal services in application mode.

     

    How did you resolve this issue

    Tuesday, August 19, 2008 11:21 PM
  • Khalif42: I have since upgraded to Windows 2008 and sorry can't remember whether i fixed it or not.

     

    Tuesday, August 19, 2008 11:25 PM
  • Your running 2008 server with exchange 2007sp1?

     

    Tuesday, August 19, 2008 11:34 PM
  • Did you find a resolution for your first error 3038? Need help having the same error

    running Windows  Standard x64 Server 2003 Running Exchange 2007 SP1

    Tuesday, August 19, 2008 11:40 PM
  •  

    http://technet.microsoft.com/en-us/library/cc754828.aspx

     

    I receive a warning message that the protocol handler Search.Mapi2Handler.1 cannot be loaded.

    This is a known issue on 64-bit Windows XP and Windows 2003 operating systems because there currently is no 64-bit Outlook MAPI provider. The warning message is a notification only and has no impact on indexing or searching

    Thursday, October 02, 2008 9:23 PM
  •     

       Windows XP x64 SP2, Office SB 2007 SP1 - This error (Event: 3083) seemed to be coinciding with stated workstation freezing up.  I uninstalled Windows Search 4.0 (which had been installed via MS Update) and have had no problems (error events) since.
       I did get a download request the first time I opened Outlook after the uninstall stating that in order to use the Instant Search feature I needed to go to Microsoft download, etc.  The search functionality in Outlook still works.  I can neither document nor comment on any search performance differences...

    Tuesday, March 17, 2009 7:47 PM
  • Tim,

    Thanks for the registry keys information which has proved to be helpfull.

    My experience:
    A search through my registry revealed that key exists for 32bit application only. 
    In other words I found {9E175BAF-F52A-11D8-B9A5-505054503030} under [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\
    . . . and not in [HKEY_CLASSES_ROOT\CLSID\

    32 bit applications use [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\
    64 bit applications use [HKEY_CLASSES_ROOT\CLSID\

    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\InprocServer32]
    @="Windows Search Service Office Outlook Protocol Handler"
    
    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\InprocServer32]
    @=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,74,00,25,\
      00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,6d,00,73,00,\
      73,00,70,00,68,00,2e,00,64,00,6c,00,6c,00,00,00
    "ThreadingModel"="Both"
    
    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\ProgID]
    @="Search.MAPI2Handler.1"
    
    [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}\VersionIndependentProgID]
    @="Search.MAPI2Handler"
    
    

    I decided to refrain from deleting [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}]

    Here is the procedure I followed:


     1 > Save a backup copy of the whole registry in case make a mistake.
     2 > Use regedit, search for {9E175BAF-F52A-11D8-B9A5-505054503030} in KEYs
     2 > Verify that you have the right key by looking at the status bar at the bottom of the regedit window
           [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}]
     3 > Use File>Export to save the data to a folder of choice on the hard drive.
     4 > Use Windows Explorer to make a copy of the saved file for editing in the next step.
     5 > Right click the file you wan to edit and select Edit
     6 > Remove delete the characters \Wow6432Node in each line
     7 > Save the file
     8 > Back in regedit click File>Import to import the file you just edited and saved.

    It's just that easy.
    Best wishes,

    Steven Bland
    MemoryMediaProductions.com
    Preserve Your Legacy

    Tuesday, April 07, 2009 1:41 AM
  • Office Outlook only currently ships 32-bit code. This needs to be registered in the Wow6432Node hive so that the search service knows that a 32-bit version of the SearchProtocolHost needs to be started to handle indexing email. Please do not delete or modify registry keys as this will break the product. The error message "The protocol handler Search.Mapi2Handler.1 cannot be loaded." is benign and can be safely ignored on a 64-bit system.
    Microsoft
    Wednesday, April 08, 2009 5:39 PM
  • Hi Eric, it is good to know it is benign, but it does happen quite often. I have windows 2003 R2 x64, and MOSS 2007 with Microsoft Desktop Search 3.01 and the message comes up quite frequently and my clients and I would like to reduce log noise. Are any of these proposed methods likely to be useful to prevent the event from being logged?
    thanks,
    Rick McClinton


    Thursday, April 30, 2009 3:36 AM
  • This has been fixed in Windows Search 4.0. Please try out the current version to see if it address your issue. (The fix was targeted to 64-bit Vista, but it should also address W2k3 x64 platform)
    Microsoft
    Friday, May 01, 2009 1:03 AM
  • Hello; on a 2003R2 standard x64 system I uninstalled windows search 4.0 and reinstalled the x64 version downloaded from Microsoft. I am still getting the error. We are not running exchange on this server. Is this still a problem with Windows Search 4.0? I am ignoring the error for now but I would like to resolve it if I can.
    Thursday, May 07, 2009 10:50 AM
  • I installed Windows Search 4.0 on a fresh Server 2003 x64 machine (Office had already been installed, but Search 3.0 had never been installed), and I'm seeing this error in my event log.
    Tuesday, June 23, 2009 4:43 PM
  • dont' add CLSID's if you don't know for what.
    just register the dll by running "regsvr32 c:\windows\system32\mssph.dll".
    • Proposed as answer by Thibaut PARISI Monday, October 19, 2009 1:22 PM
    Sunday, June 28, 2009 7:09 AM
  • windows search 4.0 on Windows Server 2003 Storage Server and getting this error, any updates?
    Contracted Network/Systems Engineer
    Thursday, July 30, 2009 5:53 AM
  • I installed the MapiCdo Package 1.2.1 Package from Microsoft and this problem went away for about a week.  Anyone else find an answer to this issue? 
    Wednesday, October 14, 2009 7:22 PM
  • Eric,

    I am not running outlook or exchange servers.  I am up to date on all software and am still getting the - protocol handler search.mapi2handler.1 cannot be loaded - errors over and over again until this morning I got a new one - Event ID 1015 (Event ID 2083 for the Windows Search Service has been surpressed 6 times(s) since 8:25:30 PM. This event is used to suppress Windows Search Service events that have occurred frequently within a short period of time.  See Event ID 2083 for further details on this event.)  I'd be happy but I'm still getting the 3083 errors.  I have Windows 2003 server 64 bit os.  Any fixes I'm not getting on updates?  I sure don't want to mess with the registry since everything else seems to be clicking along just fine.  Thanks
    Delma
    Monday, February 15, 2010 2:44 PM
  • How can you tell us not to make a fix for something, that there is not other fix for? 
    Monday, February 15, 2010 7:23 PM
  • Indeed, a fault that is known about for years, still exists and fills my Event log with thousands of error messages that 'are benign and can be ignored'!!!!!
    How the ____ to I find real issues amongst all the red crosses??????????

    A REAL fix, please!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Monday, March 01, 2010 3:26 PM
  • x64 Server 2003 just started that error message after restart from updates.  Server has never had any red crosses in Event Log.  Something has changed and not for the better.

    As the Aardvark says...please find a real fix!  We are at wits end this morning trying to find a solution.

    Gawds how I hate Windows search!!!
    Been There, Done That
    Friday, March 05, 2010 4:40 PM
  • Hellooooo..ooo?  Anybody there? I thought for a moment there was someone still in at Microsoft because the lights appeared to be on.

    Unfortunately, it's just us mugs! Conned into thinking they knew what they were doing and actually gave a stuff for customers. How foolish could I be????

    You lot really do take the pi$$

    Wednesday, March 10, 2010 12:03 PM
  • It hasn't been fixed. You're either a mug or an idiot (or both) if you think it has. Any likelihood of a real solution this side of the next millennium????



    Oh, it would seem that the previous poster has deleted his message out of embarrassment! A pity Microsoft don't have such scruples and feel the shame that they ought....
    • Edited by aardvark7 Saturday, March 13, 2010 9:26 PM
    Wednesday, March 10, 2010 12:05 PM
  • ...and so the wait goes on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...and on...

    I want a fix to get rid of these thousands of red crosses reporting 'benign events'. For crying out loud do me the courtesy and reply!!!!!!!!!
    Saturday, March 13, 2010 9:24 PM
  • I too am having this issue.... Windows 2003 R2 64-bit Enterprise, running Exchange 2007 SP1, Windows Search Service 4.0

     

    Event Type:    Error
    Event Source:    Windows Search Service
    Event Category:    (3)
    Event ID:    3083
    Date:        4/7/2010
    Time:        7:05:03 AM
    User:        N/A
    Computer:    XXXXXXX
    Description:
    The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered
    .


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

     

    still waiting on that answer....

     

     

    Wednesday, April 07, 2010 1:05 PM
  • I think you will be waiting forever! Microsoft seem to think it sensible to provide the Event ID system to let users see what is going wrong, then allow it to be filled with erroneous messages when something is going wrong that must be straightforward to fix!

    ar5e-about-face thinking, but that is Microsoft for you (and every other big computer company, come to that)!!!!!!

    Still, we wait in the vain hope someone might give a toss....

    Wednesday, April 07, 2010 5:20 PM
  • dont' add CLSID's if you don't know for what.
    just register the dll by running "regsvr32 c:\windows\system32\mssph.dll".


    This worked for me on 64bit W2K3 Standard running Exchange 2K7 Standard by adding similar registry entries to those described above by Steven Bland and Time Elvidge, however this method from Bytebiker is much quicker.

     

     

     

    Sunday, April 18, 2010 10:03 AM
  • Hi My searchindexer.exe is having the same problem as most here. Wont start and stay started.

    The is been happening since the very first day of installation. It was upto almost 15000 errors on searchindexer.exe before i realized what was going on and stopped it to sableize the system.

     Im running Win7 X64 enterprise. Build 7600.

    heres the log file . 1st the warning that is osted every now and then the the 2 errors that have been repeating every chance it got until it was stopped manually.

    Warning

    Event ID 1003 for the Windows Search Service has been suppressed 324 time(s) since 5:00:47 AM. This event is used to suppress Windows Search Service events that have occurred frequently within a short period of time. See Event ID 1003 for further details on this event.

     

    FIRST ERROR: Application Error Log event.

    Faulting application name: SearchIndexer.exe, version: 7.0.7600.16385, time stamp: 0x4a5bd212

    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0

    Exception code: 0xc0000005

    Fault offset: 0x000000000000aa7d

    Faulting process id: 0x19ac

    Faulting application start time: 0x01cae54080170d64

    Faulting application path: C:\Windows\system32\SearchIndexer.exe

    Faulting module path: C:\Windows\system32\KERNELBASE.dll

    Report Id: be0ebaa4-5133-11df-a67c-00044b15cc0d

     

    SECOND ERROR: Service Control Manager

    The Windows Search service terminated unexpectedly. It has done this 3703 time(s).

    The count is hi only because i leave my computer running all the time.  What bothers me more then any of this is, I had been beta testing the older versions for over a year without any problems. 

     Any Help Would be greatly appriciated. 

    Olin 

     

     

    Sunday, May 02, 2010 7:47 PM
  • I uninstalled Windows Search 4.0 and the error stopped. I still have the old traditional search that we all used before MS released the new windows search that we did not really need for just a file server.

    Server 2003 enterprise sp2

    Wednesday, May 05, 2010 1:45 PM
  • Same problem here.

    Running W2k3 64Bit + AD + WSUS. After last update (20100706) event log start to report this error: "The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered". Wsus Snap-ip wont' start. Explorer hang up when i try to display "My Computer". Control Panel can't load installed application so i can't remove windows search. System is hard to restart or shutdown.
    Solution posted here does not fix my problem.

    Does anyone have a real fix? :|

     

    tia, Loris

    Friday, June 18, 2010 7:31 AM
  • It sounds like there may be more issues with your system than just Search 4.0. However, a lot of the hanging could be down to your disks creating an index for Search 4.0, if you have the option ticked and your discs are large, with lots of data and fragmented.

    If you can open the control panel you should be able to click 'Folders' to get access to your disk properties and disable indexing. I'm not sure why Search 4.0 is not listed (check all possible names just in case you are expecting to see it listed as Windows Search 4.0, rather than Search 4.0).

    If it definitely isn't there, it may not have installed properly, which could be down to other issues, in which case you should download from Microsoft and try to re-install. This should create the listing for uninstall or even give you that option straightaway (re-install, repair or remove).

    As to a solution to the error, the reason is given that Search 4.0 is making a call to a non-existent handler. Why they simply can't stop it making the call is beyond me. Clearly, it is not needed because they say the error can be ignored. It is akin to having traffic lights on an island with no cars. The sensible thing to do is to turn off the lights!

    Sorry I can't help more.

    Thursday, June 24, 2010 7:16 AM
  • I recieved this error on my (2003R2SP2 64Bit) System, after I applied a "GPO" to harden my system. I also am having some issues getting  the cluster service to start on this box also when I back out the policy everything works fine. Is there anyway to tell what in the policy is causing the issues?
    Thursday, July 01, 2010 2:16 PM
  • This may be the fix: went to control panel, add remove programs, found the Microsoft Full Text Indexing Engine for Exchange, and repaired. The errors are now gone.

    This worked for me on my windows 2003 SP3 server running Exchange 2007 SP2.

    Friday, July 02, 2010 5:29 PM
  • Parallel problems here, but with XP 32-bit home, SP3 and with Nokia not MAPI. Similar “The protocol handler MDatastorePH.MDatastoreProtocol.1 cannot be loaded. Error description: Class not registered” 3083 message. Registry entry:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search\Gather\Windows\SystemIndex\Protocols\nokia.mplatform.mdatastore\0]

    "Included"=dword:00000001

    "ExtExclusionsUsed"=dword:00000001

    "PrefixName"=""

    "ProgIdHandler"="MDatastorePH.MDatastoreProtocol.1"

    @=""

    I tried deleting the entire protocols\nokia key, but could not. Even if the key appears to accept deletion, Search reinstates it on next reboot. The error occurs reliably just as Outlook is booted up, then recurs irregularly indefinitely.

    These two .exe files fire up at each incidence of the error:

    SearchProtocolHost.exe

    SearchFilterHost.exe

    both in system32. They run for just a minute or so, before expiring. The problem seems clearly to be in Search. Here the issue has occurred only since a fresh copy of Search was downloaded about a week ago.

    Thursday, August 26, 2010 11:17 AM
  • Worked beautifully! 

    thanks!

    Wednesday, October 13, 2010 3:04 AM
  • Eric,

    I am not running outlook or exchange servers.  I am up to date on all software and am still getting the - protocol handler search.mapi2handler.1 cannot be loaded - errors over and over again until this morning I got a new one - Event ID 1015 (Event ID 2083 for the Windows Search Service has been surpressed 6 times(s) since 8:25:30 PM. This event is used to suppress Windows Search Service events that have occurred frequently within a short period of time.  See Event ID 2083 for further details on this event.)  I'd be happy but I'm still getting the 3083 errors.  I have Windows 2003 server 64 bit os.  Any fixes I'm not getting on updates?  I sure don't want to mess with the registry since everything else seems to be clicking along just fine.  Thanks
    Delma

    Ok - I'm still waiting on a fix - I almost missed a hard drive failure because of the multiple entries I'm getting still.

    When is this going to be fixed?  Please don't ask me to mess with the registry - everything else is working just fine and when I mess with the registry, it may no longer be just fine.

     

    thanks

    Delma

    Tuesday, March 01, 2011 3:33 PM
  • Hi to everybody,

    I've Win 2003 server r2 x64 and i had the id. 3083.

    I've resolved it with steven bland commentary that can be read above.

    This is the procedure:

    1) search into regedit for {9E175BAF-F52A-11D8-B9A5-505054503030} in keys

    2) the path is HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{9E175BAF-F52A-11D8-B9A5-505054503030}

    3) Use File/export to save the key to a folder you prefer.

    4) Go to edit that key that you've saved.

    5) Delete the characters '\Wow6432Node' in each line and save

    6) Execute the key to replace it the registry.

    • Proposed as answer by aleonlore Wednesday, August 01, 2012 4:35 PM
    Wednesday, March 30, 2011 2:17 PM
  • Registering the dll as mentioned by bytebiker worked for us. We were getting this error message on 2 Windows 2003 R2 servers. Now we get none. Thanks ....


    Wednesday, June 29, 2011 5:32 PM
  • Editing my registery is NOT an option. This problem started for me when I ran the last updates on my server. Microsoft needs to pull their head out and fix THEIR problem! I have thousands of entries on my event log. I almost missed some errors that needed attention because of this.

    It is posting the error on my server approx every 5 minutes. It started 7/10 when I last ran the latest updates on my server. Windows search completes indexing, no problem, search is active and working. This doesn't seem to be a legit error as far as search working, however, it is clouding up my event viewer.

    FIX IT ALREADY.


    Saturday, July 30, 2011 6:54 PM
  • I just backed out Windows Search v4, which was updated on KB940157 and there are no errors being reported.

    Until Microsoft decides to address this issue with Windows Server 2003, and if you do not want to have to edit your registry, this seems to fix the issue for now

    • Proposed as answer by ServerLady Saturday, July 30, 2011 9:01 PM
    Saturday, July 30, 2011 9:01 PM
  • worked for me!  thanks!
    Wednesday, September 07, 2011 8:42 PM
  • NONE of you actually looked at the Windows Search parameters but instead viewed the registry, the process etc...

    Been watching these threads for a couple years, that error appearing every ten minutes or so on my lonely 2003R2 server.

    Today I looked at the service itself and you know what?  There are associations for .eml, .mht, .nws in the advanced section of Windows search options.  Just uncheck the associations and the problem goes away.  Not sure why its taken three years to find that as I have suffered the same, but there it is


    Been There, Done That

    • Proposed as answer by Fubar4Fun Tuesday, July 17, 2012 3:33 PM
    Tuesday, July 17, 2012 3:33 PM
  • worked for 64bit xp

    Alan Mitchell

    Wednesday, August 01, 2012 5:27 PM
  • Where do I get the fix. I'm running Windows Ultimate 64

    Thank you

    Tuesday, August 07, 2012 5:29 PM
  • dont' add CLSID's if you don't know for what.
    just register the dll by running "regsvr32 c:\windows\system32\mssph.dll".

    Thanks ByteBiker!

    That was the cure on our Windows 2003 R2 Sp2 64-bit system.


    Gustav Brock

    Tuesday, August 28, 2012 6:09 AM