AV & contineus stack dumps on SQL7.

Hi,
I've got SQL7-SP3 installation on NT4-SP6. Now, today I
noticed that for number of days it is generating stack
dumps every few minutes. It goes like this:
===================== SqlDumpExceptionHandler: Process 51 generated fatal
exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
is terminating this process.
* BEGIN STACK DUMP:
-
-
-
-
language_exec: Process 51 generated an access violation.
SQL Server is terminating this process.
====================== Input buffer always say:
* select rsc_type, req_mode, req_status from
master..syslockinfo
I tried to search the knowledge base, but it reports tons
of reasons for AV. I have seen AV & stack dumps number of
times in past (on different servers) that goes only for
once, but the one I am looking at currently is doing it
constantly at few minutes interval.
I havn't heard any performance cry yet and don't know how
it is affecting.
Anyone seen this kind of behaviour or have any input on
this are welcome to shed some light. Your input is
appreciated. Thanks.
Adi.We found a monitoring software that was querying
syslockinfo, causing AV and stack dump. Stopping this
monitoring software service stopped stack dumps.
Still I wonder how did it started happening as we have
ditto configuration and setup on number of other servers
where everything seems to be working fine.
Anyways, thanks for your replies guys. Appreciate it.
Adi ..
>--Original Message--
>Hi,
>I've got SQL7-SP3 installation on NT4-SP6. Now, today I
>noticed that for number of days it is generating stack
>dumps every few minutes. It goes like this:
>=====================>SqlDumpExceptionHandler: Process 51 generated fatal
>exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server
>is terminating this process.
>* BEGIN STACK DUMP:
>-
>-
>-
>-
>language_exec: Process 51 generated an access violation.
>SQL Server is terminating this process.
>======================>Input buffer always say:
>* select rsc_type, req_mode, req_status from
>master..syslockinfo
>I tried to search the knowledge base, but it reports tons
>of reasons for AV. I have seen AV & stack dumps number of
>times in past (on different servers) that goes only for
>once, but the one I am looking at currently is doing it
>constantly at few minutes interval.
>I havn't heard any performance cry yet and don't know how
>it is affecting.
>Anyone seen this kind of behaviour or have any input on
>this are welcome to shed some light. Your input is
>appreciated. Thanks.
>Adi.
>.
>

Autostart SQLServerAgent service

Hi,
During our server installation SQL Server 2000 SP4 SQLServerAgent is
not started (it was also not needed). But since a few weeks we are
using SQL jobs to make a SQL Backup very day
My first actions were:
SC CONFIG sqlserveragent start= auto
and
NET START sqlserveragent
I thought this was enough, but...
After a boot (weekly boot) the SQLServerAgent service was stopped and
configured manual... and thus the backup was not made!
For the moment I now have the following workaround:
CREATE PROCEDURE dbo.PRXAutoAgent
AS
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
GO
--Set new stored procedure as start up stored procedure
EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
GO
Everytime the server boots and SQLServer is starting up, the stored
procedure 'PRXAutoAgent' is started.
My question(s): how is it possible that every time the server boots the
SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1?
Is there a solution to this problem?
Hope to hear,
Andr
Hi
Go to the Services on the server and Start the Agent in automatic regime
"DrDre" <avwg@.planet.nl> wrote in message
news:1163487650.945207.264300@.k70g2000cwa.googlegr oups.com...
Hi,
During our server installation SQL Server 2000 SP4 SQLServerAgent is
not started (it was also not needed). But since a few weeks we are
using SQL jobs to make a SQL Backup very day
My first actions were:
SC CONFIG sqlserveragent start= auto
and
NET START sqlserveragent
I thought this was enough, but...
After a boot (weekly boot) the SQLServerAgent service was stopped and
configured manual... and thus the backup was not made!
For the moment I now have the following workaround:
CREATE PROCEDURE dbo.PRXAutoAgent
AS
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
GO
--Set new stored procedure as start up stored procedure
EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
GO
Everytime the server boots and SQLServer is starting up, the stored
procedure 'PRXAutoAgent' is started.
My question(s): how is it possible that every time the server boots the
SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1?
Is there a solution to this problem?
Hope to hear,
Andr
|||Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Andr
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegr oups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start= auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1?
> Is there a solution to this problem?
> Hope to hear,
> Andr
|||DrDre
>This was known to me and done/tested by me, but still, after a boot the
>SQLServerAgent doesnot run and is configured manual..
Any info in Event Viewer ,ERROR.LOG?
"DrDre" <avwg@.planet.nl> wrote in message
news:1163492345.735336.128170@.i42g2000cwa.googlegr oups.com...
Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Andr
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegr oups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start= auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1?
> Is there a solution to this problem?
> Hope to hear,
> Andr
|||Uri,
Nope, looked there--> no errors :-(
No problems at all, except a non-running SQLServerAgent after a boot
Uri Dimant wrote:[vbcol=seagreen]
> DrDre
> Any info in Event Viewer ,ERROR.LOG?
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163492345.735336.128170@.i42g2000cwa.googlegr oups.com...
> Hi Uri,
> This was known to me and done/tested by me, but still, after a boot the
> SQLServerAgent doesnot run and is configured manual..
> Andr
> Uri Dimant wrote:
|||"DrDre" <avwg@.planet.nl> wrote in message
news:1163492345.735336.128170@.i42g2000cwa.googlegr oups.com...
Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Confirm in the SERVICES Applet in the control panel that SQL Server Agent is
set to automatic and depends on SQL Server.
Andr
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegr oups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start= auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1?
> Is there a solution to this problem?
> Hope to hear,
> Andr

Autostart SQLServerAgent service

Hi,
During our server installation SQL Server 2000 SP4 SQLServerAgent is
not started (it was also not needed). But since a few weeks we are
using SQL jobs to make a SQL Backup very day
My first actions were:
SC CONFIG sqlserveragent start=3D auto
and
NET START sqlserveragent
I thought this was enough, but...
After a boot (weekly boot) the SQLServerAgent service was stopped and
configured manual... and thus the backup was not made!
For the moment I now have the following workaround:
CREATE PROCEDURE dbo.PRXAutoAgent
AS
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
GO
--Set new stored procedure as start up stored procedure
EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
GO
Everytime the server boots and SQLServer is starting up, the stored
procedure 'PRXAutoAgent' is started.
My question(s): how is it possible that every time the server boots the
SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
Is there a solution to this problem?
Hope to hear,
Andr=E9Hi
Go to the Services on the server and Start the Agent in automatic regime
"DrDre" <avwg@.planet.nl> wrote in message
news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
Hi,
During our server installation SQL Server 2000 SP4 SQLServerAgent is
not started (it was also not needed). But since a few weeks we are
using SQL jobs to make a SQL Backup very day
My first actions were:
SC CONFIG sqlserveragent start= auto
and
NET START sqlserveragent
I thought this was enough, but...
After a boot (weekly boot) the SQLServerAgent service was stopped and
configured manual... and thus the backup was not made!
For the moment I now have the following workaround:
CREATE PROCEDURE dbo.PRXAutoAgent
AS
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
GO
--Set new stored procedure as start up stored procedure
EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
GO
Everytime the server boots and SQLServer is starting up, the stored
procedure 'PRXAutoAgent' is started.
My question(s): how is it possible that every time the server boots the
SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
Is there a solution to this problem?
Hope to hear,
André|||Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Andr=E9
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start=3D auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
> > Is there a solution to this problem?
> > Hope to hear,
> > Andr=E9|||DrDre
>This was known to me and done/tested by me, but still, after a boot the
>SQLServerAgent doesnot run and is configured manual..
Any info in Event Viewer ,ERROR.LOG?
"DrDre" <avwg@.planet.nl> wrote in message
news:1163492345.735336.128170@.i42g2000cwa.googlegroups.com...
Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
André
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start= auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
> Is there a solution to this problem?
> Hope to hear,
> André|||Uri,
Nope, looked there--> no errors :-(
No problems at all, except a non-running SQLServerAgent after a boot
Uri Dimant wrote:
> DrDre
> >This was known to me and done/tested by me, but still, after a boot the
> >SQLServerAgent doesnot run and is configured manual..
> Any info in Event Viewer ,ERROR.LOG?
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163492345.735336.128170@.i42g2000cwa.googlegroups.com...
> Hi Uri,
> This was known to me and done/tested by me, but still, after a boot the
> SQLServerAgent doesnot run and is configured manual..
> Andr=E9
> Uri Dimant wrote:
> > Hi
> > Go to the Services on the server and Start the Agent in automatic regime
> >
> >
> >
> > "DrDre" <avwg@.planet.nl> wrote in message
> > news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
> > Hi,
> >
> > During our server installation SQL Server 2000 SP4 SQLServerAgent is
> > not started (it was also not needed). But since a few weeks we are
> > using SQL jobs to make a SQL Backup very day
> >
> > My first actions were:
> > SC CONFIG sqlserveragent start=3D auto
> > and
> > NET START sqlserveragent
> >
> > I thought this was enough, but...
> >
> > After a boot (weekly boot) the SQLServerAgent service was stopped and
> > configured manual... and thus the backup was not made!
> >
> > For the moment I now have the following workaround:
> >
> > CREATE PROCEDURE dbo.PRXAutoAgent
> > AS
> > EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> > GO
> > --Set new stored procedure as start up stored procedure
> > EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> > GO
> > Everytime the server boots and SQLServer is starting up, the stored
> > procedure 'PRXAutoAgent' is started.
> >
> > My question(s): how is it possible that every time the server boots the
> > SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
> >
> > Is there a solution to this problem?
> >
> > Hope to hear,
> >
> > Andr=E9|||"DrDre" <avwg@.planet.nl> wrote in message
news:1163492345.735336.128170@.i42g2000cwa.googlegroups.com...
Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Confirm in the SERVICES Applet in the control panel that SQL Server Agent is
set to automatic and depends on SQL Server.
André
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start= auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
> Is there a solution to this problem?
> Hope to hear,
> André

Autostart SQLServerAgent service

Hi,
During our server installation SQL Server 2000 SP4 SQLServerAgent is
not started (it was also not needed). But since a few weeks we are
using SQL jobs to make a SQL Backup very day
My first actions were:
SC CONFIG sqlserveragent start=3D auto
and
NET START sqlserveragent
I thought this was enough, but...
After a boot (weekly boot) the SQLServerAgent service was stopped and
configured manual... and thus the backup was not made!
For the moment I now have the following workaround:
CREATE PROCEDURE dbo.PRXAutoAgent
AS
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
GO
--Set new stored procedure as start up stored procedure
EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
GO
Everytime the server boots and SQLServer is starting up, the stored
procedure 'PRXAutoAgent' is started.
My question(s): how is it possible that every time the server boots the
SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
Is there a solution to this problem?
Hope to hear,
Andr=E9Hi
Go to the Services on the server and Start the Agent in automatic regime
"DrDre" <avwg@.planet.nl> wrote in message
news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
Hi,
During our server installation SQL Server 2000 SP4 SQLServerAgent is
not started (it was also not needed). But since a few weeks we are
using SQL jobs to make a SQL Backup very day
My first actions were:
SC CONFIG sqlserveragent start= auto
and
NET START sqlserveragent
I thought this was enough, but...
After a boot (weekly boot) the SQLServerAgent service was stopped and
configured manual... and thus the backup was not made!
For the moment I now have the following workaround:
CREATE PROCEDURE dbo.PRXAutoAgent
AS
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
GO
--Set new stored procedure as start up stored procedure
EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
GO
Everytime the server boots and SQLServer is starting up, the stored
procedure 'PRXAutoAgent' is started.
My question(s): how is it possible that every time the server boots the
SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
Is there a solution to this problem?
Hope to hear,
Andr|||Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Andr=E9
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start=3D auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
>=20
> Is there a solution to this problem?
>=20
> Hope to hear,
>=20
> Andr=E9|||DrDre
>This was known to me and done/tested by me, but still, after a boot the
>SQLServerAgent doesnot run and is configured manual..
Any info in Event Viewer ,ERROR.LOG?
"DrDre" <avwg@.planet.nl> wrote in message
news:1163492345.735336.128170@.i42g2000cwa.googlegroups.com...
Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Andr
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start= auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
> Is there a solution to this problem?
> Hope to hear,
> Andr|||Uri,
Nope, looked there--> no errors :-(
No problems at all, except a non-running SQLServerAgent after a boot
Uri Dimant wrote:[vbcol=seagreen]
> DrDre
> Any info in Event Viewer ,ERROR.LOG?
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163492345.735336.128170@.i42g2000cwa.googlegroups.com...
> Hi Uri,
> This was known to me and done/tested by me, but still, after a boot the
> SQLServerAgent doesnot run and is configured manual..
> Andr=E9
> Uri Dimant wrote:|||"DrDre" <avwg@.planet.nl> wrote in message
news:1163492345.735336.128170@.i42g2000cwa.googlegroups.com...
Hi Uri,
This was known to me and done/tested by me, but still, after a boot the
SQLServerAgent doesnot run and is configured manual..
Confirm in the SERVICES Applet in the control panel that SQL Server Agent is
set to automatic and depends on SQL Server.
Andr
Uri Dimant wrote:
> Hi
> Go to the Services on the server and Start the Agent in automatic regime
>
> "DrDre" <avwg@.planet.nl> wrote in message
> news:1163487650.945207.264300@.k70g2000cwa.googlegroups.com...
> Hi,
> During our server installation SQL Server 2000 SP4 SQLServerAgent is
> not started (it was also not needed). But since a few weeks we are
> using SQL jobs to make a SQL Backup very day
> My first actions were:
> SC CONFIG sqlserveragent start= auto
> and
> NET START sqlserveragent
> I thought this was enough, but...
> After a boot (weekly boot) the SQLServerAgent service was stopped and
> configured manual... and thus the backup was not made!
> For the moment I now have the following workaround:
> CREATE PROCEDURE dbo.PRXAutoAgent
> AS
> EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'
> GO
> --Set new stored procedure as start up stored procedure
> EXEC dbo.sp_procoption 'PRXAutoAgent', 'startup','TRUE'
> GO
> Everytime the server boots and SQLServer is starting up, the stored
> procedure 'PRXAutoAgent' is started.
> My question(s): how is it possible that every time the server boots the
> SQLServerAgent service is reconfigured? Is it Windows Server 2003 SP1'
> Is there a solution to this problem?
> Hope to hear,
> Andr