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:
Showing posts with label below. Show all posts
Showing posts with label below. Show all posts
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 u
p
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 cli
ck
> on modify this workspace, the add web parts...drag any of the web parts ov
er
> 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 t
he
> 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, i
t
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 t
ry
> 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 do
es
> 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 serv
er
> (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:
>
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 u
p
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 cli
ck
> on modify this workspace, the add web parts...drag any of the web parts ov
er
> 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 t
he
> 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, i
t
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 t
ry
> 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 do
es
> 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 serv
er
> (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:
>
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,
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
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,
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
MSRT - Error with Exporting the Reports to Excel Format.
I tried to export a report to excel format. I am getting the below error(Array Index out of bounds). The report is around 12 pages. Any thoughts on this? Server Error in '/Reports' Application.
Stack Trace: 
.
Server Error in '/Reports' Application.
Index was outside the bounds of the array.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.Exception: Index was outside the bounds of the array.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[Exception: An error occurred during rendering of the report.]
[Exception: An error occurred during rendering of the report.]
Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension) +489
Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +924
Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& fileExtension) +84
Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +153
Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +75
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +303
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
Santhosh
Santosh,
Do you get this for all reports or just for one particular report. If it is for one particular report next thing is do you know if it is for a particular field?
|||Im getting just this particular report and in the pre prod the same report is working fine only in production Im having this issue. That too it works fine on one day and breaks on the next day.
Monday, March 19, 2012
Msg 5133, Level 16, State 1, Line 1
Hi all,
I am try to restore a database from external hard drive and I am get the
errors below. Do you have any ideas how to resolve these errors?. Thank you
in advance.
Errors:
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "E:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" failed with the operating system
error 3(The system cannot find the path specified.).
Msg 3156, Level 16, State 3, Line 1
File 'SCData_prosum' cannot be restored to 'E:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf'. Use WITH MOVE to identify a
valid location for the file.
Msg 3119, Level 16, State 1, Line 1
Problems were identified while planning for the RESTORE statement. Previous
messages provide details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
-- Create databse file under: c:\mssql\data\...
c\msssql\Log\....
-- Here is my script try to restore the database.
EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', True
GO
PRINT 'Begin restore SCData_prosum database, please wait...'
RESTORE DATABASE SCData_prosum
FROM DISK = 'C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
WITH REPLACE,
RECOVERY,
STATS = 10
GO
EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', False
GOHi
Does the directory "E:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\" exist?
If not you will need to change the location of where the database file will
be placed
e.g. ( be careful if this wraps around)
RESTORE DATABASE SCData_prosum
FROM DISK ='C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
WITH MOVE 'SCData_prosum_Data' TO 'C:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf',
MOVE 'SCData_prosum_Log' TO ''C:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.ldf';
GO
To get the name of the logical files and where it expects to put them you
can use
RESTORE FILELISTONLY SCData_prosum
FROM DISK ='C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
GO
If the directory does exist then it may be a permissions issue.
John
"Lam Nguyen" wrote:
> Hi all,
> I am try to restore a database from external hard drive and I am get the
> errors below. Do you have any ideas how to resolve these errors?. Thank you
> in advance.
> Errors:
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" failed with the operating system
> error 3(The system cannot find the path specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'SCData_prosum' cannot be restored to 'E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 3119, Level 16, State 1, Line 1
> Problems were identified while planning for the RESTORE statement. Previous
> messages provide details.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> -- Create databse file under: c:\mssql\data\...
> c\msssql\Log\....
> -- Here is my script try to restore the database.
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', True
> GO
> PRINT 'Begin restore SCData_prosum database, please wait...'
> RESTORE DATABASE SCData_prosum
> FROM DISK => 'C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
> WITH REPLACE,
> RECOVERY,
> STATS = 10
> GO
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', False
> GO
>|||You are trying to replace your backup as John mentions.
If you are using SSMS to restore your backup then in the Restore Database
window click to Options from the left panel and check out "Restore the
database files as:" in the list view, you will see 3 columns. One of them is
Original File Name and the other is Restore As.
Both columns' values must be the same in your situation and they both must
be "E:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" so your
restore operation fails.
Change the values in the Restore As column. So you will be able to restore
your backup successfully.
--
Ekrem Ã?nsoy
"Lam Nguyen" <LamNguyen@.discussions.microsoft.com> wrote in message
news:DE41AA77-9CA3-427A-888C-F759BA1AFD07@.microsoft.com...
> Hi all,
> I am try to restore a database from external hard drive and I am get the
> errors below. Do you have any ideas how to resolve these errors?. Thank
> you
> in advance.
> Errors:
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" failed with the operating
> system
> error 3(The system cannot find the path specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'SCData_prosum' cannot be restored to 'E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 3119, Level 16, State 1, Line 1
> Problems were identified while planning for the RESTORE statement.
> Previous
> messages provide details.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> -- Create databse file under: c:\mssql\data\...
> c\msssql\Log\....
> -- Here is my script try to restore the database.
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', True
> GO
> PRINT 'Begin restore SCData_prosum database, please wait...'
> RESTORE DATABASE SCData_prosum
> FROM DISK => 'C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
> WITH REPLACE,
> RECOVERY,
> STATS = 10
> GO
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', False
> GO
>
I am try to restore a database from external hard drive and I am get the
errors below. Do you have any ideas how to resolve these errors?. Thank you
in advance.
Errors:
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "E:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" failed with the operating system
error 3(The system cannot find the path specified.).
Msg 3156, Level 16, State 3, Line 1
File 'SCData_prosum' cannot be restored to 'E:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf'. Use WITH MOVE to identify a
valid location for the file.
Msg 3119, Level 16, State 1, Line 1
Problems were identified while planning for the RESTORE statement. Previous
messages provide details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
-- Create databse file under: c:\mssql\data\...
c\msssql\Log\....
-- Here is my script try to restore the database.
EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', True
GO
PRINT 'Begin restore SCData_prosum database, please wait...'
RESTORE DATABASE SCData_prosum
FROM DISK = 'C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
WITH REPLACE,
RECOVERY,
STATS = 10
GO
EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', False
GOHi
Does the directory "E:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\" exist?
If not you will need to change the location of where the database file will
be placed
e.g. ( be careful if this wraps around)
RESTORE DATABASE SCData_prosum
FROM DISK ='C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
WITH MOVE 'SCData_prosum_Data' TO 'C:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf',
MOVE 'SCData_prosum_Log' TO ''C:\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\SCData_prosum.ldf';
GO
To get the name of the logical files and where it expects to put them you
can use
RESTORE FILELISTONLY SCData_prosum
FROM DISK ='C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
GO
If the directory does exist then it may be a permissions issue.
John
"Lam Nguyen" wrote:
> Hi all,
> I am try to restore a database from external hard drive and I am get the
> errors below. Do you have any ideas how to resolve these errors?. Thank you
> in advance.
> Errors:
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" failed with the operating system
> error 3(The system cannot find the path specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'SCData_prosum' cannot be restored to 'E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 3119, Level 16, State 1, Line 1
> Problems were identified while planning for the RESTORE statement. Previous
> messages provide details.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> -- Create databse file under: c:\mssql\data\...
> c\msssql\Log\....
> -- Here is my script try to restore the database.
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', True
> GO
> PRINT 'Begin restore SCData_prosum database, please wait...'
> RESTORE DATABASE SCData_prosum
> FROM DISK => 'C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
> WITH REPLACE,
> RECOVERY,
> STATS = 10
> GO
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', False
> GO
>|||You are trying to replace your backup as John mentions.
If you are using SSMS to restore your backup then in the Restore Database
window click to Options from the left panel and check out "Restore the
database files as:" in the list view, you will see 3 columns. One of them is
Original File Name and the other is Restore As.
Both columns' values must be the same in your situation and they both must
be "E:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" so your
restore operation fails.
Change the values in the Restore As column. So you will be able to restore
your backup successfully.
--
Ekrem Ã?nsoy
"Lam Nguyen" <LamNguyen@.discussions.microsoft.com> wrote in message
news:DE41AA77-9CA3-427A-888C-F759BA1AFD07@.microsoft.com...
> Hi all,
> I am try to restore a database from external hard drive and I am get the
> errors below. Do you have any ideas how to resolve these errors?. Thank
> you
> in advance.
> Errors:
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf" failed with the operating
> system
> error 3(The system cannot find the path specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'SCData_prosum' cannot be restored to 'E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\DATA\SCData_prosum.mdf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 3119, Level 16, State 1, Line 1
> Problems were identified while planning for the RESTORE statement.
> Previous
> messages provide details.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
> -- Create databse file under: c:\mssql\data\...
> c\msssql\Log\....
> -- Here is my script try to restore the database.
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', True
> GO
> PRINT 'Begin restore SCData_prosum database, please wait...'
> RESTORE DATABASE SCData_prosum
> FROM DISK => 'C:\MSSQL\Backup\SCData_Prosum\SCData_prosum_backup_200709061759.bak'
> WITH REPLACE,
> RECOVERY,
> STATS = 10
> GO
> EXECute Master.dbo.sp_dboption 'SCData_prosum', 'Single', False
> GO
>
Friday, March 9, 2012
Msg 107, Level 16, State 2, Line 1
Hi,
I am getting the following error from the query below against SQL
Server 8.00.2039 (SP4)
Error:
====
Server: Msg 107, Level 16, State 2, Line 1
The column prefix 'd' does not match with a table name or alias name
used in the query.
Select Statement:
=============
select ...
from trades a,
gems_product_groups b,
portfolio_nav_mapping c,
products d,
limit_types e
left outer join gems_prod_trade_mod f on d.product_id =
f.product_ID
I know this was a known bug in MS-SQL7, but I thought it had been fixed
in 2000.
Can anyone help?
Thanks(billdonovan1947@.yahoo.com.au) writes:
> I am getting the following error from the query below against SQL
> Server 8.00.2039 (SP4)
> Error:
>====
> Server: Msg 107, Level 16, State 2, Line 1
> The column prefix 'd' does not match with a table name or alias name
> used in the query.
> Select Statement:
>=============
> select ...
> from trades a,
> gems_product_groups b,
> portfolio_nav_mapping c,
> products d,
> limit_types e
> left outer join gems_prod_trade_mod f on d.product_id =
> f.product_ID
> I know this was a known bug in MS-SQL7, but I thought it had been fixed
> in 2000.
Without seeing the entire query, it's difficult to see what might be
wrong, but try rewrite the query to use JOIN syntax throughout:
SELECT ...
FROM trades a
JOIN gems_product_groups b ON ...
JOIN portfolio_nav_mapping c ON ...
JOIN products d ON ...
JOIN limit_types e ON ...
LEFT JOIN gems_prod_trade_mod f on d.product_id = ...
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||>From what I've observed, "left join" requires the tables that you're
joining to be adjacent in the list, at least when mixed with other
joins written the way you have them. In your case you have limit_types
between products and the left join. If you simply swap the positions of
products and limit_types then it should work. e.g:
select ...
from trades a,
gems_product_groups b,
portfolio_nav_mapping c,
limit_types e,
products d
left outer join gems_prod_trade_mod f on d.product_id =
f.product_ID
Malcolm|||>>>From what I've observed, "left join" requires the tables that you're
>>joining to be adjacent in the list, at least when mixed with other
>>joins written the way you have them.
Brilliant! That works. Thanks for all your help.
Msg 107, Level 16, State 2, Line 1
Hi,
I am getting the following error from the query below against SQL
Server 8.00.2039 (SP4)
Error:
====
Server: Msg 107, Level 16, State 2, Line 1
The column prefix 'd' does not match with a table name or alias name
used in the query.
Select Statement:
=============
select ...
from trades a,
gems_product_groups b,
portfolio_nav_mapping c,
products d,
limit_types e
left outer join gems_prod_trade_mod f on d.product_id =
f.product_ID
I know this was a known bug in MS-SQL7, but I thought it had been fixed
in 2000.
Can anyone help?
ThanksBill
It worked on my workstation (SQL Server 2000 SP3)
BTW why would you want to use an 'old' style and not OUTER JOIN?
"bill1947" <billdonovan1947@.yahoo.com.au> wrote in message
news:1138768112.996524.20860@.g14g2000cwa.googlegroups.com...
> Hi,
> I am getting the following error from the query below against SQL
> Server 8.00.2039 (SP4)
> Error:
> ====
> Server: Msg 107, Level 16, State 2, Line 1
> The column prefix 'd' does not match with a table name or alias name
> used in the query.
> Select Statement:
> =============
> select ...
> from trades a,
> gems_product_groups b,
> portfolio_nav_mapping c,
> products d,
> limit_types e
> left outer join gems_prod_trade_mod f on d.product_id =
> f.product_ID
> I know this was a known bug in MS-SQL7, but I thought it had been fixed
> in 2000.
> Can anyone help?
> Thanks
>|||Uri,
I changed the order of the tables to
gems_product_groups b,
portfolio_nav_mapping c,
limit_types e,
products d
left outer join gems_prod_trade_mod f on d.product_id =
f.product_ID
and it works. In the previous incarnation I tried every type of join
and got the same error.
I am getting the following error from the query below against SQL
Server 8.00.2039 (SP4)
Error:
====
Server: Msg 107, Level 16, State 2, Line 1
The column prefix 'd' does not match with a table name or alias name
used in the query.
Select Statement:
=============
select ...
from trades a,
gems_product_groups b,
portfolio_nav_mapping c,
products d,
limit_types e
left outer join gems_prod_trade_mod f on d.product_id =
f.product_ID
I know this was a known bug in MS-SQL7, but I thought it had been fixed
in 2000.
Can anyone help?
ThanksBill
It worked on my workstation (SQL Server 2000 SP3)
BTW why would you want to use an 'old' style and not OUTER JOIN?
"bill1947" <billdonovan1947@.yahoo.com.au> wrote in message
news:1138768112.996524.20860@.g14g2000cwa.googlegroups.com...
> Hi,
> I am getting the following error from the query below against SQL
> Server 8.00.2039 (SP4)
> Error:
> ====
> Server: Msg 107, Level 16, State 2, Line 1
> The column prefix 'd' does not match with a table name or alias name
> used in the query.
> Select Statement:
> =============
> select ...
> from trades a,
> gems_product_groups b,
> portfolio_nav_mapping c,
> products d,
> limit_types e
> left outer join gems_prod_trade_mod f on d.product_id =
> f.product_ID
> I know this was a known bug in MS-SQL7, but I thought it had been fixed
> in 2000.
> Can anyone help?
> Thanks
>|||Uri,
I changed the order of the tables to
gems_product_groups b,
portfolio_nav_mapping c,
limit_types e,
products d
left outer join gems_prod_trade_mod f on d.product_id =
f.product_ID
and it works. In the previous incarnation I tried every type of join
and got the same error.
Subscribe to:
Posts (Atom)