mssdmn.exe pop-up errors on SharePoint Search Server

[BaileyG]

In our large-farm SharePoint environment:
MOSS 2007 SP1
WSS 3.0 SP1
12.0.0.6219
Windows Server 2003 R2
Enterprise x64 Edition, SP2

We have almost 2.5 million items in our index and we were experiencing difficulties with the Adobe ifilter so we uninstalled it and then bought Foxit's iFilter and installed it.

Since then our poor search server has been inundated with pop-up memory errors and we've got hundreds of Event ID 26 in our event log.

Like so:
Application popup: mssdmn.exe - Application Error : The instruction at "0x2a3682e6" referenced memory at "0xffffffff". The memory could not be "read".
Application popup: mssdmn.exe - Application Error : The instruction at "0x77ef60f1" referenced memory at "0x000000f5". The memory could not be "read".

Has anyone experienced anything similar? If so, what was the resolution?


Thanks.

Bailey G

[kwright7878]

I am having the same exact errors. Have you found a resolution for this?

[BaileyG]

No and I was hoping by now that someone from Foxit would speak up.

Bailey G

[AmyLin]

Hello all,

Thank you for your feedback.IFilter Team is looking into this issue.

[BaileyG]

Is there a traditional method of calling in for support? Should I have attempted to obtain support for the product we purchased through a different channel?

Do you need more information?

[Erik_Bryant]

The best way for support for the IFilter is to go through a Support Ticket or support e-mails. That way we have enough information to try and reproduce the issues. You can also call our support number for basic support.

http://www.foxitsoftware.com/support/

[mike.joyce@prim]

We are just deploying a single server MOSS2007 on Win2003 R2 x64, MOSS x64, SQL2005 Std x64.

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.

We hope that Foxit will resolve this with an update for the iFilter soon as we have a great many similar "dirty" PDF to upload into searchable Sharepoint libraries.

[Marvel]

Hi there! Found this thread doing a Google search this morning trying to find out why my MOSS server is throwing this error. I'm wondering if there is a quick "fix" for this that I can try. I will be calling Support in a few minutes but it would be most helpful to everyone to have some information posted on this issue.

[AmyLin]

This issue has been fixed in 1.0.0.2405

[bijayani]

As we will see in SharePoint 2003, it was not possible to add a simple piece of server side code in the content pages. But in SharePoint 2007 adding server side code to the content pages is possible. This can be achieved by modifying the web.config file. In the web.config file you can find <PageParserPaths> tag where we need to add some lines of code.

<SharePoint>
<SafeModeMaxControls="200"CallStack="false"DirectF ileDependencies="10"TotalFileDependencies="50"Allo wPageLevelTrace="false">
<PageParserPaths>
<PageParserPathVirtualPath="/*"CompilationMode="Always"AllowServerSideScript="t rue"IncludeSubFolders="true" />
</PageParserPaths>
</SafeMode>

Thanks,
Bijayani
Learn about SharePoint Migration.