Your server is reporting an annoying "Search.Mapi2Handler.1 cannot be loaded" error message in the application events.
Believe it or not, this is not a SharePoint error. In fact it’s a Windows search error that appears when you use the program on a 64 bit machine and it’s probably running because you installed Windows Desktop Search (WDS). Since you’re reading this blog, you’re probably running a special Ifilter for SharePoint Search that required WDS to be installed in order for it to function properly. For example, Adobe uses the Ifilter interface as provided by Windows Desktop Search in order to thunk between 64 and their 32 bit implementation.
Architecturally, when you install Windows Desktop Search you end with two components running on your server. The first is the Windows Desktop Search user interface which is a bunch of components in IE, Outlook, the task bar, and the main search. The second component is the MSSearch service that runs under a process called SearchIndexer.exe.
What few people realize: neither the Windows Desktop Search or the Search Indexer need to be running for SharePoint search indexing to function. In addition, there’s really no reason Windows Desktop Search or any indexer needs to run on a Server in the first place. If you think about it, how often to you search for files when logged into the machine, and if you do should you really have an indexer enabled?
Stop and Disable MSSearch (runs as SearchIndexer.exe) by visiting Start >> Control Panel >> Administrative Tools >> Services and disabled Wsearch.
*** IF YOU SET THE SERVICE TO MANUAL THE SERVICE WILL STILL GET STARTED SO I RECOMMEND DISABLING THE SERVICE
Rating: 7.7/10 (3 votes cast)
Rating: +2 (from 2 votes)
Search.Mapi2Handler.1 cannot be loaded, 7.7 out of 10 based on 3 ratings
Ulysses Ludwig is a SharePoint architect with over 16 years in the IT and computer industry. Ulysses' primary focus is SharePoint but he dabbles in the latest web technologies and likes to develop software in his spare time.
If you are running Windows Server 2003 or a pre Windows Server 2008 R2 build then please refer to this article: http://www.sharepointassist.com/2009/01/27/61738644-f196-11d0-9953-00c04fd919c1-launch-permissions/...
A SQL Server alias is a tidy way to protect yourself from configuration changes in a SharePoint farm. Anybody who works with SharePoint on a regular basis knows that it is very difficult to move SharePoint...