Hi,
How does one install MSSQL 2000 on a machine that's already running MSDE 2000? Do i need to unintstall MSDE, or both can be installed seperately??
Is there a way to simply upgrade MSDE into MSSQL 2000?
Thanks!Its easy to upgrade from MSDE to SQL Server, review information from books online from the topic 'How to perform an edition upgrade within SQL Server 2000'sql
Showing posts with label installed. Show all posts
Showing posts with label installed. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MSSQL 2000 - cant connect to DB from remote computer
Please bare with me as I do not have much knowledge in this area with MSSQL.
I have installed MSSQL 2000 Developer and I have setup a database which I am able to connect to and work fine with from the actual server MSSQL is installed on.
The problem comes in when i try to connect to that same database from a different remote server. It will not connect to the DB from this remote server but I know all the connection information is correct so its something on the MSSQL DB server causing this and not on this remote server.
Someone I know has had this problem and has fixed it but they wont tell me how. All I know is they said something about manually opening the ports on the MSSQL server and he also said when you set it to dynamicly determine the port that MSSQL is listening on it errored out. however if you set it staticly to 1433 it worked fine.
Ive also installed SP4 in attempt to fix this but no luck with that either. And I can also get the same exact remote server to connect to completely different DB server without issues.
If anyone can please help walk me through this I would be greatly appreciate and I am also willing to pay some money if it will make my life easier.Can "Developer Version" be connected from a remote client?|||While these (http://msdn2.microsoft.com/en-us/library/ms175043.aspx) directions are specifically for SQL 2005, I'm pretty sure that they'll work for SQL-2000 too.
-PatP|||Ronin- Yes it can be done.
Pat- The firewall is completely disabled. It says Windows Firewall and ICS(internet connection sharing) is disabled when I try to go to the firewall settings so I dont think thats the problem unless I have to enable it and then do this but that doesnt make much sense.|||can anyone help?|||Which SQL network libraries did you select?
-PatP|||named pipes, tcp/ip, nwlink ipx/spx, VIA giganet
I have installed MSSQL 2000 Developer and I have setup a database which I am able to connect to and work fine with from the actual server MSSQL is installed on.
The problem comes in when i try to connect to that same database from a different remote server. It will not connect to the DB from this remote server but I know all the connection information is correct so its something on the MSSQL DB server causing this and not on this remote server.
Someone I know has had this problem and has fixed it but they wont tell me how. All I know is they said something about manually opening the ports on the MSSQL server and he also said when you set it to dynamicly determine the port that MSSQL is listening on it errored out. however if you set it staticly to 1433 it worked fine.
Ive also installed SP4 in attempt to fix this but no luck with that either. And I can also get the same exact remote server to connect to completely different DB server without issues.
If anyone can please help walk me through this I would be greatly appreciate and I am also willing to pay some money if it will make my life easier.Can "Developer Version" be connected from a remote client?|||While these (http://msdn2.microsoft.com/en-us/library/ms175043.aspx) directions are specifically for SQL 2005, I'm pretty sure that they'll work for SQL-2000 too.
-PatP|||Ronin- Yes it can be done.
Pat- The firewall is completely disabled. It says Windows Firewall and ICS(internet connection sharing) is disabled when I try to go to the firewall settings so I dont think thats the problem unless I have to enable it and then do this but that doesnt make much sense.|||can anyone help?|||Which SQL network libraries did you select?
-PatP|||named pipes, tcp/ip, nwlink ipx/spx, VIA giganet
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:
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:
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,
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >
Friday, March 23, 2012
MSQL Server Version with service pack
I just installed sp3 from micrsofot. how I would know that which service pack I have installed on MSSQL 2000.
thanks for help in advance.
KMType SELECT @.@.Version in the query analyzer and it will tell you all the version info on your SQL Server.|||Or you may go to Enterprise Manager and Right Click on the Server--Properties and under the Gereral Tab it gives you the SP information.
SQL 2000----No SP--8.00.194
SQL 2000------SP1--8.00.384
SQL 2000------SP2--8.00.534
SQL 2000------SP3--8.00.760|||I must say I had a devil of a time connecting to remote sites with ent manager. Until I finally installed sp3 - now I connect up with ease. must of been some bug in the software (winXP) sql server2k that the sp3 fixes.
thanks for help in advance.
KMType SELECT @.@.Version in the query analyzer and it will tell you all the version info on your SQL Server.|||Or you may go to Enterprise Manager and Right Click on the Server--Properties and under the Gereral Tab it gives you the SP information.
SQL 2000----No SP--8.00.194
SQL 2000------SP1--8.00.384
SQL 2000------SP2--8.00.534
SQL 2000------SP3--8.00.760|||I must say I had a devil of a time connecting to remote sites with ent manager. Until I finally installed sp3 - now I connect up with ease. must of been some bug in the software (winXP) sql server2k that the sp3 fixes.
MSOLAP 2000 SP4 and Pertlib errors
Hi all,
I just installed MSOLAP 2000 SP4, and now every 4 seconds or so I'm seeing 2 new messages in the Application log.
This first one is from MSSQLServerOLAPService:
The description for Event ID ( 2003 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt..
The Second is from Perflib:
The description for Event ID ( 2003 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt..
Any ideas on what might be happening?
Thank you all.
Try first to install the hotfix, there was a problem with the Service Pack 4 more information see below.
This article lists the hotfixes that were originally released for Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3), but that were not included in Service Pack 4 (SP4). These hotfixes are now available in a downloadable post-SP4 hotfix rollup package for SQL Server 2000 Analysis Services.
Hotfix rollup package for SQL Server 2000 Analysis Services Service Pack - Build 2174
MS SQL Server Analysis Services 2000:
http://support.microsoft.com/?kbid=907323&SD=tech
MS SQL Server 2000:
http://support.microsoft.com/kb/904660/en-us
|||I installed the hotfix, I'm still getting the same 2 event log messages every 5 seconds.|||Chris,
Where did you get SP 4 for OLAP ? Where can you download it? (I′ve saw the download place only for the SP 4 of SQL 2000)
Do you still have problems with SP 4, also after the install of the Hot Fixes ?
greetings,
Laura
Wednesday, March 21, 2012
Msg 8964 After applying sql server service pack 4
Even though I have installed the latest sql server service pack (4). When I
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanks
Hi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanks
Hi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
Msg 8964 After applying sql server service pack 4
Even though I have installed the latest sql server service pack (4). When I
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanksHi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanksHi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
Monday, March 19, 2012
Msg 8964 After applying sql server service pack 4
Even though I have installed the latest sql server service pack (4). When I
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanksHi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
run the dbcc checkdb statement with the arithabort set to on for one of my
production databases, I still get a few line with the error:
Server: Msg 8964, Level 16, State 1, Line 4
Table error: Object ID 2. The text, ntext, or image node at page (1:380425),
slot 2, text ID 2789285298176 is not referenced.
Even when I run: SELECT @.@.VERSION system stored procedure it returns
Microsoft SQL Server 2000 -8.00.2039(Intel x86)
As the version that I am using. I have also just today re-applied the
service pack following step by step the instruction in the sqlreadme for
service pack 4. I have read a solution that suggested re-installing sql
server but that is just not an option right now, because of the fact that it
is a production database that is in constant use. I'm also starting to think
that these arent necessarily errors that are critical. Could someone
help\advise?
Many thanksHi
There is nothing wrong with your SP level, but you have corruption in your
DB that applying a SP can not help to fix. SP's do not affect user DB's,
only system DB's.
run DBCC with the REPAIR_ALLOW_DATA_LOSS option. For more information on
the command, look in Books Online.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fazz" <farayi@.lovetm.co.uk> wrote in message
news:u%23QrmC9$FHA.2320@.TK2MSFTNGP11.phx.gbl...
> Even though I have installed the latest sql server service pack (4). When
> I run the dbcc checkdb statement with the arithabort set to on for one of
> my production databases, I still get a few line with the error:
> Server: Msg 8964, Level 16, State 1, Line 4
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:380425), slot 2, text ID 2789285298176 is not referenced.
> Even when I run: SELECT @.@.VERSION system stored procedure it returns
> Microsoft SQL Server 2000 -8.00.2039(Intel x86)
> As the version that I am using. I have also just today re-applied the
> service pack following step by step the instruction in the sqlreadme for
> service pack 4. I have read a solution that suggested re-installing sql
> server but that is just not an option right now, because of the fact that
> it is a production database that is in constant use. I'm also starting to
> think that these arent necessarily errors that are critical. Could someone
> help\advise?
> Many thanks
>
Friday, March 9, 2012
msdtssrvr.exe - sql 2005 sp2
Installed sp2 for sql 2005
cannot start msdtssrvr.exe
event viewer returns:
The SQL Server Integration Services service failed to start due to the following error:
The system cannot find the file specified.
I tried to locate the msdtssrvr.exe in C:\Program Files\Microsoft SQL Server\90\DTS\Binn\
I cannot locate the file .
Ron
You need to install SSIS from the installation media. The SSIS service is not installed by default, though I'm surprised you have a service listed for SSIS in the first place.MSDTS Transaction Failed.
Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason'
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/defaul...kb;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason'
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason'
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/defaul...kb;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason'
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
MSDTS Transaction Failed.
Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason?
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/default...b;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason?
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason?
Thanks a lot for your help.
*** Sent via Developersdex http://www.codecomments.com ***
This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/default...b;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason?
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
MSDTS Transaction Failed.
Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason'
Thanks a lot for your help.
*** Sent via Developersdex http://www.developersdex.com ***This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/default.aspx?scid=kb;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason'
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
server sp4. We are checking the logs for sql server and observe that
sometimes this error is displayed
Error: 8510, Severity: 20, State: 1
Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
Do you know what could be the reason'
Thanks a lot for your help.
*** Sent via Developersdex http://www.developersdex.com ***This could be one reason for 8510 errors:
SQL Server error 8510 may be reported unnecessarily
http://support.microsoft.com/default.aspx?scid=kb;en-us;307802
You are probably running into some other MSDTC problem if 8510 are logged to
SQL errorlogs. You should capture a Profiler trace on both linked servers
(with DTCTransaction and all Warnings and Error events) and review them for
other SQL errors leading up to 8510 errors. Also ensure that all connections
executing linked-server queries have SET XACT_ABORT ON.
Adrian
"MariaGuzman" <marisa@.devdex.com> wrote in message
news:uYyL0kGRFHA.3076@.tk2msftngp13.phx.gbl...
> Hi, we have sql server 2000 sp3 std edition installed on a windows 2000
> server sp4. We are checking the logs for sql server and observe that
> sometimes this error is displayed
> Error: 8510, Severity: 20, State: 1
> Enlist of MSDTC transaction failed: Result Code = 0x8004d00e..
> Do you know what could be the reason'
> Thanks a lot for your help.
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
MSDTC!
I have SQL Server 7.0 installed in my Win2K Pro machine. When I
navigate to Start-->SQL Server 7.0-->MSDTC Administrative Console, I
get the "Missing Shortcut" error. Even a search on 'dac.exe' doesn't
yield any result. Does this mean that the DTC console didn't get
installed while SQL Server 7.0 was installed? How do I install it
directly from the SQL Server Setup CD or do I have to uninstall & then
reinstall SQL Server 7.0 to make use of DTC? Or is there an altogether
different Setup CD for DTC?
This is the first time I am trying to use DTC.
Thanks,
Arpan
There isn't a seperate CD/setup for DTC. I would un-install and
re-install.
ALI
navigate to Start-->SQL Server 7.0-->MSDTC Administrative Console, I
get the "Missing Shortcut" error. Even a search on 'dac.exe' doesn't
yield any result. Does this mean that the DTC console didn't get
installed while SQL Server 7.0 was installed? How do I install it
directly from the SQL Server Setup CD or do I have to uninstall & then
reinstall SQL Server 7.0 to make use of DTC? Or is there an altogether
different Setup CD for DTC?
This is the first time I am trying to use DTC.
Thanks,
Arpan
There isn't a seperate CD/setup for DTC. I would un-install and
re-install.
ALI
MSDTC!
I have SQL Server 7.0 installed in my Win2K Pro machine. When I
navigate to Start-->SQL Server 7.0-->MSDTC Administrative Console, I
get the "Missing Shortcut" error. Even a search on 'dac.exe' doesn't
yield any result. Does this mean that the DTC console didn't get
installed while SQL Server 7.0 was installed? How do I install it
directly from the SQL Server Setup CD or do I have to uninstall & then
reinstall SQL Server 7.0 to make use of DTC? Or is there an altogether
different Setup CD for DTC?
This is the first time I am trying to use DTC.
Thanks,
ArpanThere isn't a seperate CD/setup for DTC. I would un-install and
re-install.
ALI
navigate to Start-->SQL Server 7.0-->MSDTC Administrative Console, I
get the "Missing Shortcut" error. Even a search on 'dac.exe' doesn't
yield any result. Does this mean that the DTC console didn't get
installed while SQL Server 7.0 was installed? How do I install it
directly from the SQL Server Setup CD or do I have to uninstall & then
reinstall SQL Server 7.0 to make use of DTC? Or is there an altogether
different Setup CD for DTC?
This is the first time I am trying to use DTC.
Thanks,
ArpanThere isn't a seperate CD/setup for DTC. I would un-install and
re-install.
ALI
MSDTC!
I have SQL Server 7.0 installed in my Win2K Pro machine. When I
navigate to Start-->SQL Server 7.0-->MSDTC Administrative Console, I
get the "Missing Shortcut" error. Even a search on 'dac.exe' doesn't
yield any result. Does this mean that the DTC console didn't get
installed while SQL Server 7.0 was installed? How do I install it
directly from the SQL Server Setup CD or do I have to uninstall & then
reinstall SQL Server 7.0 to make use of DTC? Or is there an altogether
different Setup CD for DTC?
This is the first time I am trying to use DTC.
Thanks,
ArpanThere isn't a seperate CD/setup for DTC. I would un-install and
re-install.
ALI
navigate to Start-->SQL Server 7.0-->MSDTC Administrative Console, I
get the "Missing Shortcut" error. Even a search on 'dac.exe' doesn't
yield any result. Does this mean that the DTC console didn't get
installed while SQL Server 7.0 was installed? How do I install it
directly from the SQL Server Setup CD or do I have to uninstall & then
reinstall SQL Server 7.0 to make use of DTC? Or is there an altogether
different Setup CD for DTC?
This is the first time I am trying to use DTC.
Thanks,
ArpanThere isn't a seperate CD/setup for DTC. I would un-install and
re-install.
ALI
MSDTC with Windows 2003 Server
I have installed SQL Server 2000 virtual server on my Windows 2003 Server
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:
> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:
> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,
MSDTC with Windows 2003 Server
I have installed SQL Server 2000 virtual server on my Windows 2003 Server
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,
Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:
> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,
Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:
> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,
MSDTC with Windows 2003 Server
I have installed SQL Server 2000 virtual server on my Windows 2003 Server
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:
> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,
Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
added any databases. But I did not know about the MSDTC step.
What steps do I need to complete to add MSDTC since to the cluster and to
the database configuration?
Thanks,Must install Componant Services. Documentation included will have
information on a clustered vs non-clustered install.
"Joe K." wrote:
> I have installed SQL Server 2000 virtual server on my Windows 2003 Server
> Active\Active Cluster. I have installed SQL Server 2000 SP3 but have not
> added any databases. But I did not know about the MSDTC step.
> What steps do I need to complete to add MSDTC since to the cluster and to
> the database configuration?
> Thanks,
Subscribe to:
Posts (Atom)