Monday, March 26, 2012

mssdmn.exe error

if you read below, you'll get many details. basically, i've installed a
sharepoint server farm, and noticed when i add a web part then click on a
drop down arrow on the web part, i get an error on the sql server...
Application popup: mssdmn.exe - Application Error : The instruction at
"0x0040813d" referenced memory at "0x00000000". The memory could not be
"read".
Click on OK to terminate the program
Click on CANCEL to debug the program
i have been able to narrow this down to the sharepoint database. when i try
to populate (incremental or full) the catalog, then i receive this error. i
don't know why this happens and i need to get this resolved. the error does
not harm anything on the server nor does it stop the sharepoint services, so
i don't know if this will do the server any harm or not.
i'm running sql server 2000 sp 3a on a win2k3 enterprise edition dell server
(does not have sp1 installed)
does anyone have any idea what might be happening?
TIA
***previous conversations from another forum*******
update on this matter...i went to the sql database, and ran an incremental
population for the full text catalog, and that caused the error msg to pop up
on the sql server, so it's not technically wss that's causing the issue. do
you know what may be the problem or do i need to move this over to the sql
community now?
thanks,
"dimsdale_007" wrote:
[vbcol=seagreen]
> i can replicate the problem by opening up the sharepoint website, then click
> on modify this workspace, the add web parts...drag any of the web parts over
> onto the page, then click the drop down arrow on the web part itself, then
> click on modify shared web part...and then voila, the message pops up on the
> sql server.
> sometimes the error will pop up as soon as i click on the drop down arrow of
> a newly placed web part.
> this could be coincidence, but i've been able to replicate the issue over
> and over.
> while installing i went by the guidelines of the sams unleashed book to
> install sharepoint, so i'm hoping everything is set up correctly.
> thanks
>
> "Mike Walsh" wrote:
I am getting the same error when repopulating the full-text indexes using
SharePoint.
We didn't see this issue until researching another issue. The original issue
was that when we went to create an additional SharePoint content database, it
would sit for 10 minutes or so on the "Please wait while your changes are
processed" screen and then return the error "Thread was being aborted". It
appears the database was created and the full-text index was also created,
but we still get the errors.
I am currently on the phone with Microsoft support to resolve my issue.
"dimsdale_007" wrote:
[vbcol=seagreen]
> if you read below, you'll get many details. basically, i've installed a
> sharepoint server farm, and noticed when i add a web part then click on a
> drop down arrow on the web part, i get an error on the sql server...
> Application popup: mssdmn.exe - Application Error : The instruction at
> "0x0040813d" referenced memory at "0x00000000". The memory could not be
> "read".
> Click on OK to terminate the program
> Click on CANCEL to debug the program
> i have been able to narrow this down to the sharepoint database. when i try
> to populate (incremental or full) the catalog, then i receive this error. i
> don't know why this happens and i need to get this resolved. the error does
> not harm anything on the server nor does it stop the sharepoint services, so
> i don't know if this will do the server any harm or not.
> i'm running sql server 2000 sp 3a on a win2k3 enterprise edition dell server
> (does not have sp1 installed)
> does anyone have any idea what might be happening?
> TIA
>
> ***previous conversations from another forum*******
> update on this matter...i went to the sql database, and ran an incremental
> population for the full text catalog, and that caused the error msg to pop up
> on the sql server, so it's not technically wss that's causing the issue. do
> you know what may be the problem or do i need to move this over to the sql
> community now?
> thanks,
> "dimsdale_007" wrote:

No comments:

Post a Comment