Re: mssdmn.exe application error

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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:65F2B2C5-CA1D-4777-BC7A-4C1206B15CB9@xxxxxxxxxxxxxxxx
> > 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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:A7C0BB21-7244-4313-9667-A517FE30A9B4@xxxxxxxxxxxxxxxx
> >> >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,
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: Cannot upgrade WSS 2.0 to 3.0
    ... I remember seeing some threads about problems with WSUS and WSS v3 (I think ... It all seemed to function correctly at that point in terms of WSS ... Could you say everything you did on this server before starting to ... install WSS 3.0 and als when you installed WSS 3.0 did you select Basic ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS Cant Extend New Web Sites Created In IIS
    ... Windows 2003 Server ... Install SQL Server 2K SP3a at least (seems to be easier to get to work even ... install WSS SP2. ... I just don't see why IIS is stamping new sites with Version 5. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Cannot upgrade WSS 2.0 to 3.0
    ... It all seemed to function correctly at that point in terms of WSS useability ... Could you say everything you did on this server before starting to install ... configuration tasks has failed or some tasks were not run ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Installing WSS3 on remote SQL Server 2005 & Different Internet
    ... I haven't extensively checked the WSS team blog. ... installing on should only be a front-end server. ... Not sure about the port. ... I'm attempting to install the recently released Windows Sharepoint Services ...
    (microsoft.public.sharepoint.windowsservices)
  • SBS 2003, AD installation
    ... server start rebooting itself. ... is to install AD. ... Or is there reg key to modify that will not reboot ...
    (microsoft.public.windows.server.sbs)
Loading