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
Showing posts with label autostart. Show all posts
Showing posts with label autostart. Show all posts
Sunday, February 12, 2012
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é
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
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
Autostart Sql Server Agent
In sql server 2005 how do you change the settings for autostarting the sqlserver agent when the OS starts. For eg in sql server 2000 when you click the server properties you can cha nge it there but what about sql server 2005?right click My Computer and then Manage. Once there, expand Services and Applications, then click on Services. From there, you can find the SQL Server Agent() service, go to properties, and make the startup type Automatic.|||
Hello Tim,
Thanks for this info, but i wanted to know how could you do it from management console. like how you can do it from Enterprise manager in SQL server 2000. This will help my cause but just for better knowledge i wanted to know.
|||SQL Server Configuration Manager is the tool to be used in sql server 2005 for any administration of Services, protocols etc... You can find it Programs --MSSQLServer 2005 --Configuration Tool.
Right click on any service and do whatever setting you want there.
ref : http://msdn2.microsoft.com/en-us/library/ms174212.aspx
Madhu
|||Thanks a lot Madhu. I appreciate that.|||Make sure you mark it as "Answered"
yes, SQL Configuration Tool would be the place to configure Service Start type of services
Autostart MS Agent on Win98/Me
Hello,
does anyone know how I could autostart the MSAgent on Win98/Me with a
named instance.
I try with
scm.exe -Action 1 -Service SQLAgent$$" & str_InstanceName
where str_InstanceName is the name of the MSDE Instance.
The password is correct (I exported the crypted password from a computer
with Entreprise manager and the agent start with WinNT...
It can also start manually.
On Winnt, 2K and XP, all is fine, on Win98/Me, I receive the message
Service operation has been completed successfully but the agent did not
start. I can manually start the agent with the MSDE service manager, but
if my custommer forget it then he has no automatic backup of his database.
Thank you
Marc Allard
Allcomp
If you really rely on SQL Server Agent being started and you have not a lot
of control over the machine, start SQL Server Agent from within SQL Server:
-- Create a procedure to start SQL Server Agent
USE master
GO
CREATE PROC usp_start_sqlserveragent
AS
EXEC master..xp_cmdshell 'net start SQLServerAgent'
GO
-- Mark stored procedure to run on SQL Server start
EXEC sp_procoption 'usp_start_sqlserveragent', 'startup', 'true'
Jacco Schalkwijk
SQL Server MVP
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e279f2$0$2676$ba620e4c@.news.skynet.be...
> Hello,
> does anyone know how I could autostart the MSAgent on Win98/Me with a
> named instance.
> I try with
> scm.exe -Action 1 -Service SQLAgent$$" & str_InstanceName
> where str_InstanceName is the name of the MSDE Instance.
> The password is correct (I exported the crypted password from a computer
> with Entreprise manager and the agent start with WinNT...
> It can also start manually.
> On Winnt, 2K and XP, all is fine, on Win98/Me, I receive the message
> Service operation has been completed successfully but the agent did not
> start. I can manually start the agent with the MSDE service manager, but
> if my custommer forget it then he has no automatic backup of his database.
>
> Thank you
> Marc Allard
> Allcomp
|||That will never work on Windows 9x based OS's since there is no concept of a
real service which gets started with NET START. Only Windows NT based OS's
(and OS/2) have NET START.
You can use SCM.EXE instead
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:eU1Ed3y9EHA.2876@.TK2MSFTNGP12.phx.gbl...
> If you really rely on SQL Server Agent being started and you have not a
> lot of control over the machine, start SQL Server Agent from within SQL
> Server:
> -- Create a procedure to start SQL Server Agent
> USE master
> GO
> CREATE PROC usp_start_sqlserveragent
> AS
> EXEC master..xp_cmdshell 'net start SQLServerAgent'
> GO
> -- Mark stored procedure to run on SQL Server start
> EXEC sp_procoption 'usp_start_sqlserveragent', 'startup', 'true'
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e279f2$0$2676$ba620e4c@.news.skynet.be...
>
|||Right. Seems Win9x is a bit too long ago for me. I better not answer any
more questions that involve Win 9x
Jacco Schalkwijk
SQL Server MVP
"Gert E.R. Drapers" <GertD@.SQLDev.Net> wrote in message
news:eyuMfi09EHA.1544@.TK2MSFTNGP11.phx.gbl...
> That will never work on Windows 9x based OS's since there is no concept of
> a real service which gets started with NET START. Only Windows NT based
> OS's (and OS/2) have NET START.
> You can use SCM.EXE instead
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2004 All rights reserved.
> "Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid >
> wrote in message news:eU1Ed3y9EHA.2876@.TK2MSFTNGP12.phx.gbl...
>
|||Hello,
Thank you for your answers, but I already try to start the agent with
scm, but it doesn't start. If I start it manually with SQL Server
Service Manager, then it is working.
Is there something to do an automatic backup without the agent?
Thank you
Marc Allard
Allcomp
Jacco Schalkwijk wrote:
> Right. Seems Win9x is a bit too long ago for me. I better not answer any
> more questions that involve Win 9x
>
does anyone know how I could autostart the MSAgent on Win98/Me with a
named instance.
I try with
scm.exe -Action 1 -Service SQLAgent$$" & str_InstanceName
where str_InstanceName is the name of the MSDE Instance.
The password is correct (I exported the crypted password from a computer
with Entreprise manager and the agent start with WinNT...
It can also start manually.
On Winnt, 2K and XP, all is fine, on Win98/Me, I receive the message
Service operation has been completed successfully but the agent did not
start. I can manually start the agent with the MSDE service manager, but
if my custommer forget it then he has no automatic backup of his database.
Thank you
Marc Allard
Allcomp
If you really rely on SQL Server Agent being started and you have not a lot
of control over the machine, start SQL Server Agent from within SQL Server:
-- Create a procedure to start SQL Server Agent
USE master
GO
CREATE PROC usp_start_sqlserveragent
AS
EXEC master..xp_cmdshell 'net start SQLServerAgent'
GO
-- Mark stored procedure to run on SQL Server start
EXEC sp_procoption 'usp_start_sqlserveragent', 'startup', 'true'
Jacco Schalkwijk
SQL Server MVP
"Allcomp" <marc@.nospam.allcomp.be> wrote in message
news:41e279f2$0$2676$ba620e4c@.news.skynet.be...
> Hello,
> does anyone know how I could autostart the MSAgent on Win98/Me with a
> named instance.
> I try with
> scm.exe -Action 1 -Service SQLAgent$$" & str_InstanceName
> where str_InstanceName is the name of the MSDE Instance.
> The password is correct (I exported the crypted password from a computer
> with Entreprise manager and the agent start with WinNT...
> It can also start manually.
> On Winnt, 2K and XP, all is fine, on Win98/Me, I receive the message
> Service operation has been completed successfully but the agent did not
> start. I can manually start the agent with the MSDE service manager, but
> if my custommer forget it then he has no automatic backup of his database.
>
> Thank you
> Marc Allard
> Allcomp
|||That will never work on Windows 9x based OS's since there is no concept of a
real service which gets started with NET START. Only Windows NT based OS's
(and OS/2) have NET START.
You can use SCM.EXE instead
GertD@.SQLDev.Net
Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2004 All rights reserved.
"Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid > wrote
in message news:eU1Ed3y9EHA.2876@.TK2MSFTNGP12.phx.gbl...
> If you really rely on SQL Server Agent being started and you have not a
> lot of control over the machine, start SQL Server Agent from within SQL
> Server:
> -- Create a procedure to start SQL Server Agent
> USE master
> GO
> CREATE PROC usp_start_sqlserveragent
> AS
> EXEC master..xp_cmdshell 'net start SQLServerAgent'
> GO
> -- Mark stored procedure to run on SQL Server start
> EXEC sp_procoption 'usp_start_sqlserveragent', 'startup', 'true'
> --
> Jacco Schalkwijk
> SQL Server MVP
>
> "Allcomp" <marc@.nospam.allcomp.be> wrote in message
> news:41e279f2$0$2676$ba620e4c@.news.skynet.be...
>
|||Right. Seems Win9x is a bit too long ago for me. I better not answer any
more questions that involve Win 9x
Jacco Schalkwijk
SQL Server MVP
"Gert E.R. Drapers" <GertD@.SQLDev.Net> wrote in message
news:eyuMfi09EHA.1544@.TK2MSFTNGP11.phx.gbl...
> That will never work on Windows 9x based OS's since there is no concept of
> a real service which gets started with NET START. Only Windows NT based
> OS's (and OS/2) have NET START.
> You can use SCM.EXE instead
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2004 All rights reserved.
> "Jacco Schalkwijk" <jacco.please.reply@.to.newsgroups.mvps.org.invalid >
> wrote in message news:eU1Ed3y9EHA.2876@.TK2MSFTNGP12.phx.gbl...
>
|||Hello,
Thank you for your answers, but I already try to start the agent with
scm, but it doesn't start. If I start it manually with SQL Server
Service Manager, then it is working.
Is there something to do an automatic backup without the agent?
Thank you
Marc Allard
Allcomp
Jacco Schalkwijk wrote:
> Right. Seems Win9x is a bit too long ago for me. I better not answer any
> more questions that involve Win 9x
>
AutoStart Failed When Rebooted
I have the SQL account services set to autostart via sql server properties.
Question, what would be the reason why it would not autostart when I reboote
d
the server? I noticed when they installed SQL server that the program file
s
was pointed to the D drive (SAN).
Thanks,
LDSQL Sever is trying to start before the os connects to the SAN
What type of SAN are you using?
--
paulz
"LITO" wrote:
> I have the SQL account services set to autostart via sql server properties
.
> Question, what would be the reason why it would not autostart when I reboo
ted
> the server? I noticed when they installed SQL server that the program fi
les
> was pointed to the D drive (SAN).
>
> Thanks,
> LD|||LITO
Here is more info about my last reply
For a windows 2003
Start Registry Editor.
Locate and then click the following subkey:
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services\MSSQLSERVER
On the Edit menu, point to New, and then click Multi-String Value.
Type DependOnService to name the new registry value, and then press ENTER.
Double-click DependOnService, type MSiSCSI in the Value data box, and then
click OK.
http://support.microsoft.com/Default.aspx?kbid=870964
--
Paul Zanbaka
"paulz" wrote:
[vbcol=seagreen]
> SQL Sever is trying to start before the os connects to the SAN
> What type of SAN are you using?
> --
> paulz
>
> "LITO" wrote:
>
Question, what would be the reason why it would not autostart when I reboote
d
the server? I noticed when they installed SQL server that the program file
s
was pointed to the D drive (SAN).
Thanks,
LDSQL Sever is trying to start before the os connects to the SAN
What type of SAN are you using?
--
paulz
"LITO" wrote:
> I have the SQL account services set to autostart via sql server properties
.
> Question, what would be the reason why it would not autostart when I reboo
ted
> the server? I noticed when they installed SQL server that the program fi
les
> was pointed to the D drive (SAN).
>
> Thanks,
> LD|||LITO
Here is more info about my last reply
For a windows 2003
Start Registry Editor.
Locate and then click the following subkey:
HKEY_LOCAL_MACHINE\System\CurrentControl
Set\Services\MSSQLSERVER
On the Edit menu, point to New, and then click Multi-String Value.
Type DependOnService to name the new registry value, and then press ENTER.
Double-click DependOnService, type MSiSCSI in the Value data box, and then
click OK.
http://support.microsoft.com/Default.aspx?kbid=870964
--
Paul Zanbaka
"paulz" wrote:
[vbcol=seagreen]
> SQL Sever is trying to start before the os connects to the SAN
> What type of SAN are you using?
> --
> paulz
>
> "LITO" wrote:
>
AutoStart Failed When Rebooted
I have the SQL account services set to autostart via sql server properties.
Question, what would be the reason why it would not autostart when I rebooted
the server? I noticed when they installed SQL server that the program files
was pointed to the D drive (SAN).
Thanks,
LD
SQL Sever is trying to start before the os connects to the SAN
What type of SAN are you using?
paulz
"LITO" wrote:
> I have the SQL account services set to autostart via sql server properties.
> Question, what would be the reason why it would not autostart when I rebooted
> the server? I noticed when they installed SQL server that the program files
> was pointed to the D drive (SAN).
>
> Thanks,
> LD
|||LITO
Here is more info about my last reply
For a windows 2003
Start Registry Editor.
Locate and then click the following subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSSQLSERVER
On the Edit menu, point to New, and then click Multi-String Value.
Type DependOnService to name the new registry value, and then press ENTER.
Double-click DependOnService, type MSiSCSI in the Value data box, and then
click OK.
http://support.microsoft.com/Default.aspx?kbid=870964
Paul Zanbaka
"paulz" wrote:
[vbcol=seagreen]
> SQL Sever is trying to start before the os connects to the SAN
> What type of SAN are you using?
> --
> paulz
>
> "LITO" wrote:
Question, what would be the reason why it would not autostart when I rebooted
the server? I noticed when they installed SQL server that the program files
was pointed to the D drive (SAN).
Thanks,
LD
SQL Sever is trying to start before the os connects to the SAN
What type of SAN are you using?
paulz
"LITO" wrote:
> I have the SQL account services set to autostart via sql server properties.
> Question, what would be the reason why it would not autostart when I rebooted
> the server? I noticed when they installed SQL server that the program files
> was pointed to the D drive (SAN).
>
> Thanks,
> LD
|||LITO
Here is more info about my last reply
For a windows 2003
Start Registry Editor.
Locate and then click the following subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSSQLSERVER
On the Edit menu, point to New, and then click Multi-String Value.
Type DependOnService to name the new registry value, and then press ENTER.
Double-click DependOnService, type MSiSCSI in the Value data box, and then
click OK.
http://support.microsoft.com/Default.aspx?kbid=870964
Paul Zanbaka
"paulz" wrote:
[vbcol=seagreen]
> SQL Sever is trying to start before the os connects to the SAN
> What type of SAN are you using?
> --
> paulz
>
> "LITO" wrote:
AutoStart Failed When Rebooted
I have the SQL account services set to autostart via sql server properties.
Question, what would be the reason why it would not autostart when I rebooted
the server? I noticed when they installed SQL server that the program files
was pointed to the D drive (SAN).
Thanks,
LDSQL Sever is trying to start before the os connects to the SAN
What type of SAN are you using?
--
paulz
"LITO" wrote:
> I have the SQL account services set to autostart via sql server properties.
> Question, what would be the reason why it would not autostart when I rebooted
> the server? I noticed when they installed SQL server that the program files
> was pointed to the D drive (SAN).
>
> Thanks,
> LD|||LITO
Here is more info about my last reply
For a windows 2003
Start Registry Editor.
Locate and then click the following subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSQLSERVER
On the Edit menu, point to New, and then click Multi-String Value.
Type DependOnService to name the new registry value, and then press ENTER.
Double-click DependOnService, type MSiSCSI in the Value data box, and then
click OK.
http://support.microsoft.com/Default.aspx?kbid=870964
--
Paul Zanbaka
"paulz" wrote:
> SQL Sever is trying to start before the os connects to the SAN
> What type of SAN are you using?
> --
> paulz
>
> "LITO" wrote:
> > I have the SQL account services set to autostart via sql server properties.
> > Question, what would be the reason why it would not autostart when I rebooted
> > the server? I noticed when they installed SQL server that the program files
> > was pointed to the D drive (SAN).
> >
> >
> > Thanks,
> > LD
Question, what would be the reason why it would not autostart when I rebooted
the server? I noticed when they installed SQL server that the program files
was pointed to the D drive (SAN).
Thanks,
LDSQL Sever is trying to start before the os connects to the SAN
What type of SAN are you using?
--
paulz
"LITO" wrote:
> I have the SQL account services set to autostart via sql server properties.
> Question, what would be the reason why it would not autostart when I rebooted
> the server? I noticed when they installed SQL server that the program files
> was pointed to the D drive (SAN).
>
> Thanks,
> LD|||LITO
Here is more info about my last reply
For a windows 2003
Start Registry Editor.
Locate and then click the following subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSQLSERVER
On the Edit menu, point to New, and then click Multi-String Value.
Type DependOnService to name the new registry value, and then press ENTER.
Double-click DependOnService, type MSiSCSI in the Value data box, and then
click OK.
http://support.microsoft.com/Default.aspx?kbid=870964
--
Paul Zanbaka
"paulz" wrote:
> SQL Sever is trying to start before the os connects to the SAN
> What type of SAN are you using?
> --
> paulz
>
> "LITO" wrote:
> > I have the SQL account services set to autostart via sql server properties.
> > Question, what would be the reason why it would not autostart when I rebooted
> > the server? I noticed when they installed SQL server that the program files
> > was pointed to the D drive (SAN).
> >
> >
> > Thanks,
> > LD
AutoStart
Hi,
Installed MSDE desktop (sp3) on XP, however the server does not autostart on
re-booting the machine. In the service manager the server/instance name is
missing after every re-boot. I enter it manually, check the autostart box
and it runs fine, but again after re-boot the server/instance name is lost
again.
I know our work machines are limited in allowing us to edit the registry,
but on a same build machine with full sql svr installed the problem does not
occur.
Any idea?
Cheers, Josh
Hi,
In Control Panel -- Admin tools -- Services -- Select the SQL Server
service.
Double click on the services and make it to automatic and click ok.
Thanks
Hari
SQL Server MVP
"Josh" <joshua.phillips@.notthisbit.blueyonder.co.uk> wrote in message
news:8CF778B9-DED3-48D2-912E-9EEFCC91BA80@.microsoft.com...
> Hi,
> Installed MSDE desktop (sp3) on XP, however the server does not autostart
> on
> re-booting the machine. In the service manager the server/instance name
> is
> missing after every re-boot. I enter it manually, check the autostart box
> and it runs fine, but again after re-boot the server/instance name is lost
> again.
> I know our work machines are limited in allowing us to edit the registry,
> but on a same build machine with full sql svr installed the problem does
> not
> occur.
> Any idea?
> Cheers, Josh
|||Hi,
It is alreday set to auto - the icon in the task bar tray does start, but
the white circle is empty. When I then click on the sql server service
manager, the server / instance name is blank - i.e. it is not remembering the
server / instance name from before the reboot.
Josh
"Hari Prasad" wrote:
> Hi,
> In Control Panel -- Admin tools -- Services -- Select the SQL Server
> service.
> Double click on the services and make it to automatic and click ok.
> Thanks
> Hari
> SQL Server MVP
>
> "Josh" <joshua.phillips@.notthisbit.blueyonder.co.uk> wrote in message
> news:8CF778B9-DED3-48D2-912E-9EEFCC91BA80@.microsoft.com...
>
>
|||hi Josh,
Josh wrote:
> Hi,
> Installed MSDE desktop (sp3) on XP, however the server does not
> autostart on re-booting the machine. In the service manager the
> server/instance name is missing after every re-boot. I enter it
> manually, check the autostart box and it runs fine, but again after
> re-boot the server/instance name is lost again.
> I know our work machines are limited in allowing us to edit the
> registry, but on a same build machine with full sql svr installed the
> problem does not occur.
please have a look at
http://support.microsoft.com/default...b;EN-US;814132
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Installed MSDE desktop (sp3) on XP, however the server does not autostart on
re-booting the machine. In the service manager the server/instance name is
missing after every re-boot. I enter it manually, check the autostart box
and it runs fine, but again after re-boot the server/instance name is lost
again.
I know our work machines are limited in allowing us to edit the registry,
but on a same build machine with full sql svr installed the problem does not
occur.
Any idea?
Cheers, Josh
Hi,
In Control Panel -- Admin tools -- Services -- Select the SQL Server
service.
Double click on the services and make it to automatic and click ok.
Thanks
Hari
SQL Server MVP
"Josh" <joshua.phillips@.notthisbit.blueyonder.co.uk> wrote in message
news:8CF778B9-DED3-48D2-912E-9EEFCC91BA80@.microsoft.com...
> Hi,
> Installed MSDE desktop (sp3) on XP, however the server does not autostart
> on
> re-booting the machine. In the service manager the server/instance name
> is
> missing after every re-boot. I enter it manually, check the autostart box
> and it runs fine, but again after re-boot the server/instance name is lost
> again.
> I know our work machines are limited in allowing us to edit the registry,
> but on a same build machine with full sql svr installed the problem does
> not
> occur.
> Any idea?
> Cheers, Josh
|||Hi,
It is alreday set to auto - the icon in the task bar tray does start, but
the white circle is empty. When I then click on the sql server service
manager, the server / instance name is blank - i.e. it is not remembering the
server / instance name from before the reboot.
Josh
"Hari Prasad" wrote:
> Hi,
> In Control Panel -- Admin tools -- Services -- Select the SQL Server
> service.
> Double click on the services and make it to automatic and click ok.
> Thanks
> Hari
> SQL Server MVP
>
> "Josh" <joshua.phillips@.notthisbit.blueyonder.co.uk> wrote in message
> news:8CF778B9-DED3-48D2-912E-9EEFCC91BA80@.microsoft.com...
>
>
|||hi Josh,
Josh wrote:
> Hi,
> Installed MSDE desktop (sp3) on XP, however the server does not
> autostart on re-booting the machine. In the service manager the
> server/instance name is missing after every re-boot. I enter it
> manually, check the autostart box and it runs fine, but again after
> re-boot the server/instance name is lost again.
> I know our work machines are limited in allowing us to edit the
> registry, but on a same build machine with full sql svr installed the
> problem does not occur.
please have a look at
http://support.microsoft.com/default...b;EN-US;814132
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Subscribe to:
Posts (Atom)