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:
> 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'm actually wondering - given that you have done everything correctly as
> > far as WSS is concerned - whether this is actually a memory error
> > (presumably on the SQL Server server) rather than a WSS problem...
> >
> > What by the way did you mean by "everything within sharepoint works OK" -
> > that you can do changes to the WSS site but that these changes which work
> > also bring these SQL Server server errors ?
> >
> > Mike Walsh, Helsinki, Finland
> >
> > "dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
> > news:65F2B2C5-CA1D-4777-BC7A-4C1206B15CB9@.microsoft.com...
> > > 1. SQL server 2000, SP3A, running on win2k3 enterprise server (does not
> > > have
> > > sp1 installed)
> > >
> > > 2. The server i installed WSS on was our production IIS server, it had
> > > nothing but win2k3 standard edition (does not have sp1) and IIS 6.0 and
> > > asp.net was configured previously, that's all that's on the machine.
> > >
> > > 3. None of my servers have sp1 on them right now (waiting for corporate
> > > approval in case you are wondering). Yes, i did install the WSS that
> > > includes sp1.
> > >
> > > Now knowing this info, have you got any idea what's causing the problem? I
> > > can't find anything on google or technet about this.
> > >
> > > thanks,
> > >
> > > "Mike Walsh" wrote:
> > >
> > >> I only worked out that you were using *Windows SharePoint services* (WSS)
> > >> on
> > >> your very last line - please next time say WSS rather than "sharepoint"
> > >> which can mean lots of things to save readers time.
> > >>
> > >> Can you fill in the gaps please.
> > >>
> > >> 1. Is your SQL Server 2K SP3 on a different server to WSS and is it in
> > >> fact
> > >> SP 3A ?
> > >>
> > >> 2. Did you install WSS on a clean Win 2003 Server ? and before you
> > >> installed
> > >> WSS did you specify IIS 6.0 (I know you have IIS 6.0 but the question
> > >> here
> > >> is when) and as part of that ASP.NET support ?
> > >>
> > >> 3. Was the Win 2003 Server already at SP1 level before you installed WSS
> > >> ?
> > >> (I presume you installed the version of the WSS download that includes
> > >> WSS
> > >> SP1?).
> > >>
> > >> The safety approach is to have Win 2003 Server not at SP1 level; then
> > >> install WSS+WSS SP1 and then install the Win 2003 Server SP1. (Safety
> > >> because that's the order they came out - we have no *proof* as yet that
> > >> it
> > >> is 100% necessary.
> > >>
> > >> Mike Walsh, Helsinki, Finland
> > >> WSS FAQ at http://wss.collutions.com
> > >> Please reply to the newsgroup
> > >>
> > >> "dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
> > >> news:A7C0BB21-7244-4313-9667-A517FE30A9B4@.microsoft.com...
> > >> >i recently installed sharepoint as a server farm. i installed
> > >> >sharepoint
> > >> >on
> > >> > my IIS server, and pointed it to an existing sql server. everything
> > >> > within
> > >> > sharepoint works OK, but everytime i try to configure, change, or view
> > >> > anything within the sharepoint i get about 15 of these errors on my 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
> > >> >
> > >> >
> > >> > does anyone know how to resolve this? i'm running sql server 2000 sp3
> > >> > and
> > >> > on the IIS server it's IIS 6.0 and sharepoint services with sp1.
> > >> >
> > >> > thanks,
> > >>
> > >>
> > >>
> >
> >
> >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:
> 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:
> > 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'm actually wondering - given that you have done everything correctly as
> > > far as WSS is concerned - whether this is actually a memory error
> > > (presumably on the SQL Server server) rather than a WSS problem...
> > >
> > > What by the way did you mean by "everything within sharepoint works OK" -
> > > that you can do changes to the WSS site but that these changes which work
> > > also bring these SQL Server server errors ?
> > >
> > > Mike Walsh, Helsinki, Finland
> > >
> > > "dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
> > > news:65F2B2C5-CA1D-4777-BC7A-4C1206B15CB9@.microsoft.com...
> > > > 1. SQL server 2000, SP3A, running on win2k3 enterprise server (does not
> > > > have
> > > > sp1 installed)
> > > >
> > > > 2. The server i installed WSS on was our production IIS server, it had
> > > > nothing but win2k3 standard edition (does not have sp1) and IIS 6.0 and
> > > > asp.net was configured previously, that's all that's on the machine.
> > > >
> > > > 3. None of my servers have sp1 on them right now (waiting for corporate
> > > > approval in case you are wondering). Yes, i did install the WSS that
> > > > includes sp1.
> > > >
> > > > Now knowing this info, have you got any idea what's causing the problem? I
> > > > can't find anything on google or technet about this.
> > > >
> > > > thanks,
> > > >
> > > > "Mike Walsh" wrote:
> > > >
> > > >> I only worked out that you were using *Windows SharePoint services* (WSS)
> > > >> on
> > > >> your very last line - please next time say WSS rather than "sharepoint"
> > > >> which can mean lots of things to save readers time.
> > > >>
> > > >> Can you fill in the gaps please.
> > > >>
> > > >> 1. Is your SQL Server 2K SP3 on a different server to WSS and is it in
> > > >> fact
> > > >> SP 3A ?
> > > >>
> > > >> 2. Did you install WSS on a clean Win 2003 Server ? and before you
> > > >> installed
> > > >> WSS did you specify IIS 6.0 (I know you have IIS 6.0 but the question
> > > >> here
> > > >> is when) and as part of that ASP.NET support ?
> > > >>
> > > >> 3. Was the Win 2003 Server already at SP1 level before you installed WSS
> > > >> ?
> > > >> (I presume you installed the version of the WSS download that includes
> > > >> WSS
> > > >> SP1?).
> > > >>
> > > >> The safety approach is to have Win 2003 Server not at SP1 level; then
> > > >> install WSS+WSS SP1 and then install the Win 2003 Server SP1. (Safety
> > > >> because that's the order they came out - we have no *proof* as yet that
> > > >> it
> > > >> is 100% necessary.
> > > >>
> > > >> Mike Walsh, Helsinki, Finland
> > > >> WSS FAQ at http://wss.collutions.com
> > > >> Please reply to the newsgroup
> > > >>
> > > >> "dimsdale_007" <dimsdale007@.discussions.microsoft.com> wrote in message
> > > >> news:A7C0BB21-7244-4313-9667-A517FE30A9B4@.microsoft.com...
> > > >> >i recently installed sharepoint as a server farm. i installed
> > > >> >sharepoint
> > > >> >on
> > > >> > my IIS server, and pointed it to an existing sql server. everything
> > > >> > within
> > > >> > sharepoint works OK, but everytime i try to configure, change, or view
> > > >> > anything within the sharepoint i get about 15 of these errors on my 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
> > > >> >
> > > >> >
> > > >> > does anyone know how to resolve this? i'm running sql server 2000 sp3
> > > >> > and
> > > >> > on the IIS server it's IIS 6.0 and sharepoint services with sp1.
> > > >> >
> > > >> > thanks,
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >