Folk
I have multiple SQL SERVERs over 15 Servers. I have couple of test machines. I don't want to go to every machine and add evry single registration of every servers in mmc. that just way too much work. can i import an mmc console from one machine to another
if yes , how can i do it
Thank
GirishI exported registry keys under
HKEY_CURRENT_USER\Software\Microsoft\MSSQLServer\SQLEW\Registered
Servers X
when I did it last time on MSSQL7
Bart Simpson
Last time
On Tue, 2 Mar 2004 08:36:07 -0800, Girish
<anonymous@.discussions.microsoft.com> wrote:
>Folks
>I have multiple SQL SERVERs over 15 Servers. I have couple of test machines. I don't want to go to every machine and add evry single registration of every servers in mmc. that just way too much work. can i import an mmc console from one machine to another ?
>if yes , how can i do it ?
>Thanks
>Girish
Showing posts with label couple. Show all posts
Showing posts with label couple. Show all posts
Friday, March 23, 2012
Mulitiple DBs
Folks
I have multiple SQL SERVERs over 15 Servers. I have couple of test machines.
I don't want to go to every machine and add evry single registration of eve
ry servers in mmc. that just way too much work. can i import an mmc console
from one machine to another
?
if yes , how can i do it ?
Thanks
GirishI exported registry keys under
HKEY_CURRENT_USER\Software\Microsoft\MSS
QLServer\SQLEW\Registered
Servers X
when I did it last time on MSSQL7
Bart Simpson
Last time
On Tue, 2 Mar 2004 08:36:07 -0800, Girish
<anonymous@.discussions.microsoft.com> wrote:
>Folks
>I have multiple SQL SERVERs over 15 Servers. I have couple of test machines. I don'
t want to go to every machine and add evry single registration of every servers in m
mc. that just way too much work. can i import an mmc console from one machine to ano
the
r ?
>if yes , how can i do it ?
>Thanks
>Girish
I have multiple SQL SERVERs over 15 Servers. I have couple of test machines.
I don't want to go to every machine and add evry single registration of eve
ry servers in mmc. that just way too much work. can i import an mmc console
from one machine to another
?
if yes , how can i do it ?
Thanks
GirishI exported registry keys under
HKEY_CURRENT_USER\Software\Microsoft\MSS
QLServer\SQLEW\Registered
Servers X
when I did it last time on MSSQL7
Bart Simpson
Last time
On Tue, 2 Mar 2004 08:36:07 -0800, Girish
<anonymous@.discussions.microsoft.com> wrote:
>Folks
>I have multiple SQL SERVERs over 15 Servers. I have couple of test machines. I don'
t want to go to every machine and add evry single registration of every servers in m
mc. that just way too much work. can i import an mmc console from one machine to ano
the
r ?
>if yes , how can i do it ?
>Thanks
>Girish
Wednesday, March 21, 2012
MSX server in SQL 2005
I currently have a master server in SQL2000 and I have now have a couple of
new SQL2005 installs on different servers. I wish to make these new servers
target servers. So my question is - can a Master SQL2000 sever, target a
SQL2005 server?
Thanks
WendyWendy
Did you discover anything on this?
I'm in a similar situation where we'll probably have a mixture of SQL 2005
and SQL 2000 server due to vendors not upgrading to SQL 2005.
Would dearly love to know if there is any compatibility between versions for
the MSX/TSX setup.
Thanks
Phill
"Woo" wrote:
> I currently have a master server in SQL2000 and I have now have a couple o
f
> new SQL2005 installs on different servers. I wish to make these new serve
rs
> target servers. So my question is - can a Master SQL2000 sever, target a
> SQL2005 server?
> Thanks
> Wendy|||Hi Phill,
I did not get any reponses but I found this article, so it looks like you
cannot setup a SQL2000 as a master server to connect to SQL2005 target
servers. Something we are considering is installing a named instance of
SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
tried it yet though!
http://msdn2.microsoft.com/en-us/ms188926.aspx
Cheers
Wendy
"Phill" wrote:
[vbcol=seagreen]
> Wendy
> Did you discover anything on this?
> I'm in a similar situation where we'll probably have a mixture of SQL 2005
> and SQL 2000 server due to vendors not upgrading to SQL 2005.
> Would dearly love to know if there is any compatibility between versions f
or
> the MSX/TSX setup.
> --
> Thanks
> Phill
>
> "Woo" wrote:
>|||Please let me know how you get on with that solution.
I've tried setting up a SQL 2005 MSX but get version errors when I try and
enlist SQL 2000 TSX's
Thanks
Phill
"Woo" wrote:
[vbcol=seagreen]
> Hi Phill,
> I did not get any reponses but I found this article, so it looks like you
> cannot setup a SQL2000 as a master server to connect to SQL2005 target
> servers. Something we are considering is installing a named instance of
> SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
> tried it yet though!
> http://msdn2.microsoft.com/en-us/ms188926.aspx
> Cheers
> Wendy
>
>
> "Phill" wrote:
>
new SQL2005 installs on different servers. I wish to make these new servers
target servers. So my question is - can a Master SQL2000 sever, target a
SQL2005 server?
Thanks
WendyWendy
Did you discover anything on this?
I'm in a similar situation where we'll probably have a mixture of SQL 2005
and SQL 2000 server due to vendors not upgrading to SQL 2005.
Would dearly love to know if there is any compatibility between versions for
the MSX/TSX setup.
Thanks
Phill
"Woo" wrote:
> I currently have a master server in SQL2000 and I have now have a couple o
f
> new SQL2005 installs on different servers. I wish to make these new serve
rs
> target servers. So my question is - can a Master SQL2000 sever, target a
> SQL2005 server?
> Thanks
> Wendy|||Hi Phill,
I did not get any reponses but I found this article, so it looks like you
cannot setup a SQL2000 as a master server to connect to SQL2005 target
servers. Something we are considering is installing a named instance of
SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
tried it yet though!
http://msdn2.microsoft.com/en-us/ms188926.aspx
Cheers
Wendy
"Phill" wrote:
[vbcol=seagreen]
> Wendy
> Did you discover anything on this?
> I'm in a similar situation where we'll probably have a mixture of SQL 2005
> and SQL 2000 server due to vendors not upgrading to SQL 2005.
> Would dearly love to know if there is any compatibility between versions f
or
> the MSX/TSX setup.
> --
> Thanks
> Phill
>
> "Woo" wrote:
>|||Please let me know how you get on with that solution.
I've tried setting up a SQL 2005 MSX but get version errors when I try and
enlist SQL 2000 TSX's
Thanks
Phill
"Woo" wrote:
[vbcol=seagreen]
> Hi Phill,
> I did not get any reponses but I found this article, so it looks like you
> cannot setup a SQL2000 as a master server to connect to SQL2005 target
> servers. Something we are considering is installing a named instance of
> SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
> tried it yet though!
> http://msdn2.microsoft.com/en-us/ms188926.aspx
> Cheers
> Wendy
>
>
> "Phill" wrote:
>
MSX server in SQL 2005
I currently have a master server in SQL2000 and I have now have a couple of
new SQL2005 installs on different servers. I wish to make these new servers
target servers. So my question is - can a Master SQL2000 sever, target a
SQL2005 server?
Thanks
WendyWendy
Did you discover anything on this?
I'm in a similar situation where we'll probably have a mixture of SQL 2005
and SQL 2000 server due to vendors not upgrading to SQL 2005.
Would dearly love to know if there is any compatibility between versions for
the MSX/TSX setup.
--
Thanks
Phill
"Woo" wrote:
> I currently have a master server in SQL2000 and I have now have a couple of
> new SQL2005 installs on different servers. I wish to make these new servers
> target servers. So my question is - can a Master SQL2000 sever, target a
> SQL2005 server?
> Thanks
> Wendy|||Hi Phill,
I did not get any reponses but I found this article, so it looks like you
cannot setup a SQL2000 as a master server to connect to SQL2005 target
servers. Something we are considering is installing a named instance of
SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
tried it yet though!
http://msdn2.microsoft.com/en-us/ms188926.aspx
Cheers
Wendy
"Phill" wrote:
> Wendy
> Did you discover anything on this?
> I'm in a similar situation where we'll probably have a mixture of SQL 2005
> and SQL 2000 server due to vendors not upgrading to SQL 2005.
> Would dearly love to know if there is any compatibility between versions for
> the MSX/TSX setup.
> --
> Thanks
> Phill
>
> "Woo" wrote:
> > I currently have a master server in SQL2000 and I have now have a couple of
> > new SQL2005 installs on different servers. I wish to make these new servers
> > target servers. So my question is - can a Master SQL2000 sever, target a
> > SQL2005 server?
> >
> > Thanks
> > Wendy|||Please let me know how you get on with that solution.
I've tried setting up a SQL 2005 MSX but get version errors when I try and
enlist SQL 2000 TSX's
Thanks
Phill
"Woo" wrote:
> Hi Phill,
> I did not get any reponses but I found this article, so it looks like you
> cannot setup a SQL2000 as a master server to connect to SQL2005 target
> servers. Something we are considering is installing a named instance of
> SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
> tried it yet though!
> http://msdn2.microsoft.com/en-us/ms188926.aspx
> Cheers
> Wendy
>
>
> "Phill" wrote:
> > Wendy
> >
> > Did you discover anything on this?
> >
> > I'm in a similar situation where we'll probably have a mixture of SQL 2005
> > and SQL 2000 server due to vendors not upgrading to SQL 2005.
> >
> > Would dearly love to know if there is any compatibility between versions for
> > the MSX/TSX setup.
> >
> > --
> >
> > Thanks
> > Phill
> >
> >
> > "Woo" wrote:
> >
> > > I currently have a master server in SQL2000 and I have now have a couple of
> > > new SQL2005 installs on different servers. I wish to make these new servers
> > > target servers. So my question is - can a Master SQL2000 sever, target a
> > > SQL2005 server?
> > >
> > > Thanks
> > > Wendy
new SQL2005 installs on different servers. I wish to make these new servers
target servers. So my question is - can a Master SQL2000 sever, target a
SQL2005 server?
Thanks
WendyWendy
Did you discover anything on this?
I'm in a similar situation where we'll probably have a mixture of SQL 2005
and SQL 2000 server due to vendors not upgrading to SQL 2005.
Would dearly love to know if there is any compatibility between versions for
the MSX/TSX setup.
--
Thanks
Phill
"Woo" wrote:
> I currently have a master server in SQL2000 and I have now have a couple of
> new SQL2005 installs on different servers. I wish to make these new servers
> target servers. So my question is - can a Master SQL2000 sever, target a
> SQL2005 server?
> Thanks
> Wendy|||Hi Phill,
I did not get any reponses but I found this article, so it looks like you
cannot setup a SQL2000 as a master server to connect to SQL2005 target
servers. Something we are considering is installing a named instance of
SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
tried it yet though!
http://msdn2.microsoft.com/en-us/ms188926.aspx
Cheers
Wendy
"Phill" wrote:
> Wendy
> Did you discover anything on this?
> I'm in a similar situation where we'll probably have a mixture of SQL 2005
> and SQL 2000 server due to vendors not upgrading to SQL 2005.
> Would dearly love to know if there is any compatibility between versions for
> the MSX/TSX setup.
> --
> Thanks
> Phill
>
> "Woo" wrote:
> > I currently have a master server in SQL2000 and I have now have a couple of
> > new SQL2005 installs on different servers. I wish to make these new servers
> > target servers. So my question is - can a Master SQL2000 sever, target a
> > SQL2005 server?
> >
> > Thanks
> > Wendy|||Please let me know how you get on with that solution.
I've tried setting up a SQL 2005 MSX but get version errors when I try and
enlist SQL 2000 TSX's
Thanks
Phill
"Woo" wrote:
> Hi Phill,
> I did not get any reponses but I found this article, so it looks like you
> cannot setup a SQL2000 as a master server to connect to SQL2005 target
> servers. Something we are considering is installing a named instance of
> SQL2005 on our SQL2000 master server, to create a MSX 2005 server. Havent
> tried it yet though!
> http://msdn2.microsoft.com/en-us/ms188926.aspx
> Cheers
> Wendy
>
>
> "Phill" wrote:
> > Wendy
> >
> > Did you discover anything on this?
> >
> > I'm in a similar situation where we'll probably have a mixture of SQL 2005
> > and SQL 2000 server due to vendors not upgrading to SQL 2005.
> >
> > Would dearly love to know if there is any compatibility between versions for
> > the MSX/TSX setup.
> >
> > --
> >
> > Thanks
> > Phill
> >
> >
> > "Woo" wrote:
> >
> > > I currently have a master server in SQL2000 and I have now have a couple of
> > > new SQL2005 installs on different servers. I wish to make these new servers
> > > target servers. So my question is - can a Master SQL2000 sever, target a
> > > SQL2005 server?
> > >
> > > Thanks
> > > Wendy
Monday, March 19, 2012
MSSQLSERVER service terminated unexpectedly
This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:
> I have a couple of sites that are running MS SQL 2000 Service pack 4 that
are
> stopping (apperantly randomly) and restarting itself. This is causing gre
at
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQ
L
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.I have a couple of sites that are running MS SQL 2000 Service pack 4 that ar
e
stopping (apperantly randomly) and restarting itself. This is causing great
havoc on some of my applications that are attached to this database. The
server is dedicated for this purpose only and is hosting only on database.
reviewing the error logs have not resulted in any explanation as to why SQL
is dying. Google & MS knowledgebase has also resulted in no
explanation/solution. Any assistance would be greatly appreciated.|||This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:
> I have a couple of sites that are running MS SQL 2000 Service pack 4 that
are
> stopping (apperantly randomly) and restarting itself. This is causing gre
at
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQ
L
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
[vbcol=seagreen]
> This probably does not apply, but we had a similar problem and it had to d
o
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
>|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
[vbcol=seagreen]
> This probably does not apply, but we had a similar problem and it had to d
o
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
>|||What does the sql errorlog say?
Martin Paterson wrote:[vbcol=seagreen]
> I looked at KB822360 and it appears to be for active directory issues. Th
e
> SQL server that is having this problem does not sit on a domain. thanks i
n
> advance for your assistance.
> "CLM" wrote:
>|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (
4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7
)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:
> What does the sql errorlog say?
>
> Martin Paterson wrote:
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (
4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7
)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:
> What does the sql errorlog say?
>
> Martin Paterson wrote:
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:
> I have a couple of sites that are running MS SQL 2000 Service pack 4 that
are
> stopping (apperantly randomly) and restarting itself. This is causing gre
at
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQ
L
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.I have a couple of sites that are running MS SQL 2000 Service pack 4 that ar
e
stopping (apperantly randomly) and restarting itself. This is causing great
havoc on some of my applications that are attached to this database. The
server is dedicated for this purpose only and is hosting only on database.
reviewing the error logs have not resulted in any explanation as to why SQL
is dying. Google & MS knowledgebase has also resulted in no
explanation/solution. Any assistance would be greatly appreciated.|||This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:
> I have a couple of sites that are running MS SQL 2000 Service pack 4 that
are
> stopping (apperantly randomly) and restarting itself. This is causing gre
at
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQ
L
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
[vbcol=seagreen]
> This probably does not apply, but we had a similar problem and it had to d
o
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
>|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
[vbcol=seagreen]
> This probably does not apply, but we had a similar problem and it had to d
o
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
>|||What does the sql errorlog say?
Martin Paterson wrote:[vbcol=seagreen]
> I looked at KB822360 and it appears to be for active directory issues. Th
e
> SQL server that is having this problem does not sit on a domain. thanks i
n
> advance for your assistance.
> "CLM" wrote:
>|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (
4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7
)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:
> What does the sql errorlog say?
>
> Martin Paterson wrote:
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] L
ock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (
4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7
)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:
> What does the sql errorlog say?
>
> Martin Paterson wrote:
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.
MSSQLSERVER service terminated unexpectedly
I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
stopping (apperantly randomly) and restarting itself. This is causing great
havoc on some of my applications that are attached to this database. The
server is dedicated for this purpose only and is hosting only on database.
reviewing the error logs have not resulted in any explanation as to why SQL
is dying. Google & MS knowledgebase has also resulted in no
explanation/solution. Any assistance would be greatly appreciated.This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:
> I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> stopping (apperantly randomly) and restarting itself. This is causing great
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQL
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
> This probably does not apply, but we had a similar problem and it had to do
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
> > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > stopping (apperantly randomly) and restarting itself. This is causing great
> > havoc on some of my applications that are attached to this database. The
> > server is dedicated for this purpose only and is hosting only on database.
> > reviewing the error logs have not resulted in any explanation as to why SQL
> > is dying. Google & MS knowledgebase has also resulted in no
> > explanation/solution. Any assistance would be greatly appreciated.|||What does the sql errorlog say?
Martin Paterson wrote:
> I looked at KB822360 and it appears to be for active directory issues. The
> SQL server that is having this problem does not sit on a domain. thanks in
> advance for your assistance.
> "CLM" wrote:
> > This probably does not apply, but we had a similar problem and it had to do
> > with the following article:
> > KB article 822360
> > MS had us put in a couple of hot fixes and it seems to have taken care of
> > the problem.
> >
> > "Martin Paterson" wrote:
> >
> > > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > > stopping (apperantly randomly) and restarting itself. This is causing great
> > > havoc on some of my applications that are attached to this database. The
> > > server is dedicated for this purpose only and is hosting only on database.
> > > reviewing the error logs have not resulted in any explanation as to why SQL
> > > is dying. Google & MS knowledgebase has also resulted in no
> > > explanation/solution. Any assistance would be greatly appreciated.|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:
> What does the sql errorlog say?
>
> Martin Paterson wrote:
> > I looked at KB822360 and it appears to be for active directory issues. The
> > SQL server that is having this problem does not sit on a domain. thanks in
> > advance for your assistance.
> >
> > "CLM" wrote:
> >
> > > This probably does not apply, but we had a similar problem and it had to do
> > > with the following article:
> > > KB article 822360
> > > MS had us put in a couple of hot fixes and it seems to have taken care of
> > > the problem.
> > >
> > > "Martin Paterson" wrote:
> > >
> > > > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > > > stopping (apperantly randomly) and restarting itself. This is causing great
> > > > havoc on some of my applications that are attached to this database. The
> > > > server is dedicated for this purpose only and is hosting only on database.
> > > > reviewing the error logs have not resulted in any explanation as to why SQL
> > > > is dying. Google & MS knowledgebase has also resulted in no
> > > > explanation/solution. Any assistance would be greatly appreciated.
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.|||I have looked through all the error logs (errorlogs.1 -> .6) and they are all
the same. The only thing is that the modified date and time are the same as
the eventlog time stating that MSSQLSERVER has died and that it has done this
xx number of times before. I have yet been able to determine what is causing
it. No error messages in the errorlog or eventlog. I have looked to see if
there is additional parameters that need to be set to show more in the
errorlog on failure but I have not been able to find anything
"Tracy McKibben" wrote:
> Martin Paterson wrote:
> > there are no errors that I can see...but here is an example of what is
> > displayed:
> > 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> > (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> >
> > 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> That's the current log that was generated when SQL restarted. What does
> the archived error log contain? Last 15-20 lines should be sufficient.
>|||For the person that first posted their original problem in this threa
regarding ODSOLE70.dll 2000.80.2039 , did you ever come up with
solution? We are experiencing the exact same dynamic link librar
showing up in our logs when our error occurs. I am having little luc
finding any other solutions fto get around it. I wondered if perhap
you might be using the same software? or would like to confirm that yo
aren't so I can rule that as the problem. Please advise?
Our problem occurs the minute we try to generate a schedule usin
software called Schedulesoft and then starts the generation and neve
ends (hangs) requiring us to cancel it. Then in the log I find the sam
reference to ODSOLE70.dll 2000.80 2039 Does anyone have any ideas o
where I might look. We are also on fix pack 4 using SQL Server 200
--
shanleatherma
----
shanleatherman's Profile: http://unixadmintalk.com/59
View this thread: http://unixadmintalk.com/showthread.php?t=18590
stopping (apperantly randomly) and restarting itself. This is causing great
havoc on some of my applications that are attached to this database. The
server is dedicated for this purpose only and is hosting only on database.
reviewing the error logs have not resulted in any explanation as to why SQL
is dying. Google & MS knowledgebase has also resulted in no
explanation/solution. Any assistance would be greatly appreciated.This probably does not apply, but we had a similar problem and it had to do
with the following article:
KB article 822360
MS had us put in a couple of hot fixes and it seems to have taken care of
the problem.
"Martin Paterson" wrote:
> I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> stopping (apperantly randomly) and restarting itself. This is causing great
> havoc on some of my applications that are attached to this database. The
> server is dedicated for this purpose only and is hosting only on database.
> reviewing the error logs have not resulted in any explanation as to why SQL
> is dying. Google & MS knowledgebase has also resulted in no
> explanation/solution. Any assistance would be greatly appreciated.|||I looked at KB822360 and it appears to be for active directory issues. The
SQL server that is having this problem does not sit on a domain. thanks in
advance for your assistance.
"CLM" wrote:
> This probably does not apply, but we had a similar problem and it had to do
> with the following article:
> KB article 822360
> MS had us put in a couple of hot fixes and it seems to have taken care of
> the problem.
> "Martin Paterson" wrote:
> > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > stopping (apperantly randomly) and restarting itself. This is causing great
> > havoc on some of my applications that are attached to this database. The
> > server is dedicated for this purpose only and is hosting only on database.
> > reviewing the error logs have not resulted in any explanation as to why SQL
> > is dying. Google & MS knowledgebase has also resulted in no
> > explanation/solution. Any assistance would be greatly appreciated.|||What does the sql errorlog say?
Martin Paterson wrote:
> I looked at KB822360 and it appears to be for active directory issues. The
> SQL server that is having this problem does not sit on a domain. thanks in
> advance for your assistance.
> "CLM" wrote:
> > This probably does not apply, but we had a similar problem and it had to do
> > with the following article:
> > KB article 822360
> > MS had us put in a couple of hot fixes and it seems to have taken care of
> > the problem.
> >
> > "Martin Paterson" wrote:
> >
> > > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > > stopping (apperantly randomly) and restarting itself. This is causing great
> > > havoc on some of my applications that are attached to this database. The
> > > server is dedicated for this purpose only and is hosting only on database.
> > > reviewing the error logs have not resulted in any explanation as to why SQL
> > > is dying. Google & MS knowledgebase has also resulted in no
> > > explanation/solution. Any assistance would be greatly appreciated.|||there are no errors that I can see...but here is an example of what is
displayed:
2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
(Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-06-19 07:01:01.44 server All rights reserved.
2006-06-19 07:01:01.44 server Server Process ID is 2032.
2006-06-19 07:01:01.44 server Logging SQL Server messages in file
'F:\Program Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2006-06-19 07:01:01.46 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2006-06-19 07:01:01.57 server SQL Server configured for thread mode
processing.
2006-06-19 07:01:01.60 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2006-06-19 07:01:02.08 server Attempting to initialize Distributed
Transaction Coordinator.
2006-06-19 07:01:05.10 spid3 Starting up database 'master'.
2006-06-19 07:01:05.24 spid3 0 transactions rolled back in database
'master' (1).
2006-06-19 07:01:05.24 spid3 Recovery is checkpointing database 'master'
(1)
2006-06-19 07:01:05.36 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2006-06-19 07:01:05.36 spid5 Starting up database 'model'.
2006-06-19 07:01:05.38 spid3 Server name is 'SECDB'.
2006-06-19 07:01:05.40 spid8 Starting up database 'msdb'.
2006-06-19 07:01:05.40 spid9 Starting up database 'pubs'.
2006-06-19 07:01:05.40 spid10 Starting up database 'Northwind'.
2006-06-19 07:01:05.40 spid11 Starting up database 'SSW'.
2006-06-19 07:01:05.60 server SQL server listening on www.xxx.yyy.zzz:
1433.
2006-06-19 07:01:05.60 server SQL server listening on 127.0.0.1: 1433.
2006-06-19 07:01:05.61 spid5 Clearing tempdb database.
2006-06-19 07:01:05.85 spid8 134 transactions rolled forward in database
'msdb' (4).
2006-06-19 07:01:05.91 spid8 0 transactions rolled back in database
'msdb' (4).
2006-06-19 07:01:05.93 spid8 Recovery is checkpointing database 'msdb' (4)
2006-06-19 07:01:06.27 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-06-19 07:01:06.27 server SQL Server is ready for client connections
2006-06-19 07:01:07.19 spid5 Starting up database 'tempdb'.
2006-06-19 07:01:08.35 spid11 314 transactions rolled forward in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 0 transactions rolled back in database
'SiteSecure' (7).
2006-06-19 07:01:08.43 spid11 Recovery is checkpointing database 'SSW' (7)
2006-06-19 07:01:09.44 spid53 Using 'odsole70.dll' version '2000.80.2039'
to execute extended stored procedure 'sp_OACreate'.
"SQLPoet" wrote:
> What does the sql errorlog say?
>
> Martin Paterson wrote:
> > I looked at KB822360 and it appears to be for active directory issues. The
> > SQL server that is having this problem does not sit on a domain. thanks in
> > advance for your assistance.
> >
> > "CLM" wrote:
> >
> > > This probably does not apply, but we had a similar problem and it had to do
> > > with the following article:
> > > KB article 822360
> > > MS had us put in a couple of hot fixes and it seems to have taken care of
> > > the problem.
> > >
> > > "Martin Paterson" wrote:
> > >
> > > > I have a couple of sites that are running MS SQL 2000 Service pack 4 that are
> > > > stopping (apperantly randomly) and restarting itself. This is causing great
> > > > havoc on some of my applications that are attached to this database. The
> > > > server is dedicated for this purpose only and is hosting only on database.
> > > > reviewing the error logs have not resulted in any explanation as to why SQL
> > > > is dying. Google & MS knowledgebase has also resulted in no
> > > > explanation/solution. Any assistance would be greatly appreciated.
>|||Martin Paterson wrote:
> there are no errors that I can see...but here is an example of what is
> displayed:
> 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> (Intel X86)
> May 3 2005 23:18:38
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> Corporation.
That's the current log that was generated when SQL restarted. What does
the archived error log contain? Last 15-20 lines should be sufficient.|||I have looked through all the error logs (errorlogs.1 -> .6) and they are all
the same. The only thing is that the modified date and time are the same as
the eventlog time stating that MSSQLSERVER has died and that it has done this
xx number of times before. I have yet been able to determine what is causing
it. No error messages in the errorlog or eventlog. I have looked to see if
there is additional parameters that need to be set to show more in the
errorlog on failure but I have not been able to find anything
"Tracy McKibben" wrote:
> Martin Paterson wrote:
> > there are no errors that I can see...but here is an example of what is
> > displayed:
> > 2006-06-19 07:01:01.44 server Microsoft SQL Server 2000 - 8.00.2039
> > (Intel X86)
> > May 3 2005 23:18:38
> > Copyright (c) 1988-2003 Microsoft Corporation
> > Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> >
> > 2006-06-19 07:01:01.44 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> That's the current log that was generated when SQL restarted. What does
> the archived error log contain? Last 15-20 lines should be sufficient.
>|||For the person that first posted their original problem in this threa
regarding ODSOLE70.dll 2000.80.2039 , did you ever come up with
solution? We are experiencing the exact same dynamic link librar
showing up in our logs when our error occurs. I am having little luc
finding any other solutions fto get around it. I wondered if perhap
you might be using the same software? or would like to confirm that yo
aren't so I can rule that as the problem. Please advise?
Our problem occurs the minute we try to generate a schedule usin
software called Schedulesoft and then starts the generation and neve
ends (hangs) requiring us to cancel it. Then in the log I find the sam
reference to ODSOLE70.dll 2000.80 2039 Does anyone have any ideas o
where I might look. We are also on fix pack 4 using SQL Server 200
--
shanleatherma
----
shanleatherman's Profile: http://unixadmintalk.com/59
View this thread: http://unixadmintalk.com/showthread.php?t=18590
Subscribe to:
Comments (Atom)