Sometimes you get an application popup from MSSDMN (Microsoft Search Service Daemon) with following error message:
mssdmn.exe – Application Error
The instruction at „0x77ef6114“ referenced memory at „0x0000000087“. The memory could not be „written“.
Click on OK to terminate the program
or
mssdmn.exe – Application Error
The instruction at „0xffffffff“ referenced memory at „0x00000000f5“. The memory could not be „read“.
Click on OK to terminate the program
The messages are different even on the same system!
If you look a bit closer you will find following information message within your system log:
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 20.09.2008
Time: 02:03:51
User: N/A
Computer: <yourServerName>
Description:
Application popup: mssdmn.exe – Application Error : The instruction at „0x26439134“ referenced memory at „0x000000c0“. The memory could not be „read“.
Click on OK to terminate the program
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Be care that message in your system log can deffered from your application popup. This is because the message popup comes when you make a crawl of your content.
For analysing check the time stamps on all EventID’s 26. You will see that they are a kind of „periodically“.
Why this happens? Do you have FoxIT PDF IFilter (mostly on x64 systems) installed? You will. This do not happen if you use the Adobe PDF IFilter. The problem is that you don’t have any choice right now within x64 systems.
This comming up from FoxIT directly:
We are pretty certain that these errors arise when a searchable PDF has been created from a „dirty“ scan where there is a lot of background „mush“ behind the text in the PDF.
As soon as the Foxit iFilter x64 tries to index one of these „dirty“ PDFs, the server throws this app error.
For a fix you have to wait for a next version of FoxIT (v1.0.0.1729 wont fix this problem).
Right now I see no issue within a production environment. So you can still use it.
Timo