Backing up DPAPI keys in relation to SQL Server

Hi,

There alot of talk about Service Master and DB Master keys and the importance of backing them up seperately.

What about the DPAPI keys used to protect the Service Master keys. What procedures to I take to back those up during my database backup.

If I understand correctly, if I do a backup on one machine, and then try to restore in a different machine, I won't be able to decrypt data becuase the DPAPI keys don't "match".

This is assumming I don't use a password to protect my DB Master keys, I just rely on the service master to protect them.

Thanks for any help,

Database master keys(DbMK) are always protected by a password - you have no choice about that.

If you backup the service master key(SMK), there is no need to be concerned about DPAPI - those keys are managed by the OS and the database automatically uses them to encrypt a loaded SMK.

When you do a database backup, you actually don't need to backup anything else than the database - you just have to remember the database master key password. You don't need the SMK or the DPAPI keys to be able to restore the database.

Thanks

Laurentiu

|||

Thanks,

I understand that I can restore the database without the SMK or DPAPI keys, but I'm surprised that I will be able decrypt data without them. I thought this was the whole purpose of the encryption heirarchy.

If I can indeed restore a database, and see the decrypted data with just the DbMK, then why do I need the DPAPI and SMK?

I thought they were in place to add additional "seperation of duties" for keys - so if someone stole a database backup tape, they wouldn't be able to restore the tape on a 'bad guy' server, and see by encrypted data - because they didn't have the SMK and DPAPI key.

Thanks for your help!

Backing up DPAPI keys in relation to SQL Server

Hi,

There alot of talk about Service Master and DB Master keys and the importance of backing them up seperately.

What about the DPAPI keys used to protect the Service Master keys. What procedures to I take to back those up during my database backup.

If I understand correctly, if I do a backup on one machine, and then try to restore in a different machine, I won't be able to decrypt data becuase the DPAPI keys don't "match".

This is assumming I don't use a password to protect my DB Master keys, I just rely on the service master to protect them.

Thanks for any help,

Database master keys(DbMK) are always protected by a password - you have no choice about that.

If you backup the service master key(SMK), there is no need to be concerned about DPAPI - those keys are managed by the OS and the database automatically uses them to encrypt a loaded SMK.

When you do a database backup, you actually don't need to backup anything else than the database - you just have to remember the database master key password. You don't need the SMK or the DPAPI keys to be able to restore the database.

Thanks

Laurentiu

|||

Thanks,

I understand that I can restore the database without the SMK or DPAPI keys, but I'm surprised that I will be able decrypt data without them. I thought this was the whole purpose of the encryption heirarchy.

If I can indeed restore a database, and see the decrypted data with just the DbMK, then why do I need the DPAPI and SMK?

I thought they were in place to add additional "seperation of duties" for keys - so if someone stole a database backup tape, they wouldn't be able to restore the tape on a 'bad guy' server, and see by encrypted data - because they didn't have the SMK and DPAPI key.

Thanks for your help!

Backing up a database to a remote shared folder

We are using SQL 2K with sp4 on W2K servers but they are in windows workgroup
not domain. The SQL service is started by the local system account. I am
having a hard time trying to back up a database to a remote shared folder
located in another W2K server in the same windows workgroup. I believe it is
an authentication/permission issue. I am aware that SQL server looks at
network shared folder differently than the way Windows see but don't know
how to get around it under the workgroup setup. If it is under domain setup,
I have no problem.
Any help on this is very much appreciated.
Wingman
The account that SQL Server runs under must have permissions to that share.
Make sure you use UNC for the path and not a mapped drive.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> We are using SQL 2K with sp4 on W2K servers but they are in windows
> workgroup
> not domain. The SQL service is started by the local system account. I am
> having a hard time trying to back up a database to a remote shared folder
> located in another W2K server in the same windows workgroup. I believe it
> is
> an authentication/permission issue. I am aware that SQL server looks at
> network shared folder differently than the way Windows see but don't know
> how to get around it under the workgroup setup. If it is under domain
> setup,
> I have no problem.
> Any help on this is very much appreciated.
> Wingman
|||Yep, I know about the UNC part but how do I assign the local account that run
SQL server to that share under the WorkGroup envirnoment. I am not very
familar with the Windows Workgroup setup. From the computer that I have the
shared folder, I can't see any user account from other computers. I believe
it is because of the Workgroup setup but then again it may be just my
inexperience in this area. Please advise.
Wingman
"Andrew J. Kelly" wrote:

> The account that SQL Server runs under must have permissions to that share.
> Make sure you use UNC for the path and not a mapped drive.
> --
> Andrew J. Kelly SQL MVP
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>
>
|||You'd have to create an account with same name and password as the service account on that other
machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have the
> shared folder, I can't see any user account from other computers. I believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
|||I am not sure if you can use the local service account or not in a workgroup
for this. You could set the permissions on the share to allow everyone to
read and write to it but that would obviously allow anyone with access to
that workgroup to access that share. Maybe someone with more experience in
WorkGroups can pipe in.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that
> run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have
> the
> shared folder, I can't see any user account from other computers. I
> believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
|||Yep, this does it. Thanks!!!
"Tibor Karaszi" wrote:

> You'd have to create an account with same name and password as the service account on that other
> machine.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
>
sql

Backing up a database to a remote shared folder

We are using SQL 2K with sp4 on W2K servers but they are in windows workgrou
p
not domain. The SQL service is started by the local system account. I am
having a hard time trying to back up a database to a remote shared folder
located in another W2K server in the same windows workgroup. I believe it i
s
an authentication/permission issue. I am aware that SQL server looks at
network shared folder differently than the way Windows see but don't know
how to get around it under the workgroup setup. If it is under domain setup
,
I have no problem.
Any help on this is very much appreciated.
WingmanThe account that SQL Server runs under must have permissions to that share.
Make sure you use UNC for the path and not a mapped drive.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> We are using SQL 2K with sp4 on W2K servers but they are in windows
> workgroup
> not domain. The SQL service is started by the local system account. I am
> having a hard time trying to back up a database to a remote shared folder
> located in another W2K server in the same windows workgroup. I believe it
> is
> an authentication/permission issue. I am aware that SQL server looks at
> network shared folder differently than the way Windows see but don't know
> how to get around it under the workgroup setup. If it is under domain
> setup,
> I have no problem.
> Any help on this is very much appreciated.
> Wingman|||Yep, I know about the UNC part but how do I assign the local account that ru
n
SQL server to that share under the WorkGroup envirnoment. I am not very
familar with the Windows Workgroup setup. From the computer that I have the
shared folder, I can't see any user account from other computers. I believe
it is because of the Workgroup setup but then again it may be just my
inexperience in this area. Please advise.
Wingman
"Andrew J. Kelly" wrote:

> The account that SQL Server runs under must have permissions to that share
.
> Make sure you use UNC for the path and not a mapped drive.
> --
> Andrew J. Kelly SQL MVP
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>
>|||You'd have to create an account with same name and password as the service a
ccount on that other
machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that
run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have t
he
> shared folder, I can't see any user account from other computers. I belie
ve
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>|||I am not sure if you can use the local service account or not in a workgroup
for this. You could set the permissions on the share to allow everyone to
read and write to it but that would obviously allow anyone with access to
that workgroup to access that share. Maybe someone with more experience in
WorkGroups can pipe in.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...[vbcol=seagreen]
> Yep, I know about the UNC part but how do I assign the local account that
> run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have
> the
> shared folder, I can't see any user account from other computers. I
> believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>|||Yep, this does it. Thanks!!!
"Tibor Karaszi" wrote:

> You'd have to create an account with same name and password as the service
account on that other
> machine.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
>

Backing up a database to a remote shared folder

We are using SQL 2K with sp4 on W2K servers but they are in windows workgroup
not domain. The SQL service is started by the local system account. I am
having a hard time trying to back up a database to a remote shared folder
located in another W2K server in the same windows workgroup. I believe it is
an authentication/permission issue. I am aware that SQL server looks at
network shared folder differently than the way Windows see but don't know
how to get around it under the workgroup setup. If it is under domain setup,
I have no problem.
Any help on this is very much appreciated.
WingmanThe account that SQL Server runs under must have permissions to that share.
Make sure you use UNC for the path and not a mapped drive.
--
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> We are using SQL 2K with sp4 on W2K servers but they are in windows
> workgroup
> not domain. The SQL service is started by the local system account. I am
> having a hard time trying to back up a database to a remote shared folder
> located in another W2K server in the same windows workgroup. I believe it
> is
> an authentication/permission issue. I am aware that SQL server looks at
> network shared folder differently than the way Windows see but don't know
> how to get around it under the workgroup setup. If it is under domain
> setup,
> I have no problem.
> Any help on this is very much appreciated.
> Wingman|||Yep, I know about the UNC part but how do I assign the local account that run
SQL server to that share under the WorkGroup envirnoment. I am not very
familar with the Windows Workgroup setup. From the computer that I have the
shared folder, I can't see any user account from other computers. I believe
it is because of the Workgroup setup but then again it may be just my
inexperience in this area. Please advise.
Wingman
"Andrew J. Kelly" wrote:
> The account that SQL Server runs under must have permissions to that share.
> Make sure you use UNC for the path and not a mapped drive.
> --
> Andrew J. Kelly SQL MVP
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> > We are using SQL 2K with sp4 on W2K servers but they are in windows
> > workgroup
> > not domain. The SQL service is started by the local system account. I am
> > having a hard time trying to back up a database to a remote shared folder
> > located in another W2K server in the same windows workgroup. I believe it
> > is
> > an authentication/permission issue. I am aware that SQL server looks at
> > network shared folder differently than the way Windows see but don't know
> > how to get around it under the workgroup setup. If it is under domain
> > setup,
> > I have no problem.
> >
> > Any help on this is very much appreciated.
> >
> > Wingman
>
>|||You'd have to create an account with same name and password as the service account on that other
machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
> Yep, I know about the UNC part but how do I assign the local account that run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have the
> shared folder, I can't see any user account from other computers. I believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>> The account that SQL Server runs under must have permissions to that share.
>> Make sure you use UNC for the path and not a mapped drive.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
>> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>> > We are using SQL 2K with sp4 on W2K servers but they are in windows
>> > workgroup
>> > not domain. The SQL service is started by the local system account. I am
>> > having a hard time trying to back up a database to a remote shared folder
>> > located in another W2K server in the same windows workgroup. I believe it
>> > is
>> > an authentication/permission issue. I am aware that SQL server looks at
>> > network shared folder differently than the way Windows see but don't know
>> > how to get around it under the workgroup setup. If it is under domain
>> > setup,
>> > I have no problem.
>> >
>> > Any help on this is very much appreciated.
>> >
>> > Wingman
>>|||I am not sure if you can use the local service account or not in a workgroup
for this. You could set the permissions on the share to allow everyone to
read and write to it but that would obviously allow anyone with access to
that workgroup to access that share. Maybe someone with more experience in
WorkGroups can pipe in.
Andrew J. Kelly SQL MVP
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
> Yep, I know about the UNC part but how do I assign the local account that
> run
> SQL server to that share under the WorkGroup envirnoment. I am not very
> familar with the Windows Workgroup setup. From the computer that I have
> the
> shared folder, I can't see any user account from other computers. I
> believe
> it is because of the Workgroup setup but then again it may be just my
> inexperience in this area. Please advise.
> Wingman
> "Andrew J. Kelly" wrote:
>> The account that SQL Server runs under must have permissions to that
>> share.
>> Make sure you use UNC for the path and not a mapped drive.
>> --
>> Andrew J. Kelly SQL MVP
>>
>> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
>> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
>> > We are using SQL 2K with sp4 on W2K servers but they are in windows
>> > workgroup
>> > not domain. The SQL service is started by the local system account. I
>> > am
>> > having a hard time trying to back up a database to a remote shared
>> > folder
>> > located in another W2K server in the same windows workgroup. I believe
>> > it
>> > is
>> > an authentication/permission issue. I am aware that SQL server looks
>> > at
>> > network shared folder differently than the way Windows see but don't
>> > know
>> > how to get around it under the workgroup setup. If it is under domain
>> > setup,
>> > I have no problem.
>> >
>> > Any help on this is very much appreciated.
>> >
>> > Wingman
>>|||Yep, this does it. Thanks!!!
"Tibor Karaszi" wrote:
> You'd have to create an account with same name and password as the service account on that other
> machine.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:6075EA91-4D10-4E03-A3D1-3BB693F750D6@.microsoft.com...
> > Yep, I know about the UNC part but how do I assign the local account that run
> > SQL server to that share under the WorkGroup envirnoment. I am not very
> > familar with the Windows Workgroup setup. From the computer that I have the
> > shared folder, I can't see any user account from other computers. I believe
> > it is because of the Workgroup setup but then again it may be just my
> > inexperience in this area. Please advise.
> >
> > Wingman
> >
> > "Andrew J. Kelly" wrote:
> >
> >> The account that SQL Server runs under must have permissions to that share.
> >> Make sure you use UNC for the path and not a mapped drive.
> >>
> >> --
> >> Andrew J. Kelly SQL MVP
> >>
> >>
> >> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> >> news:45312278-0845-433D-8F7D-2139BD2B0523@.microsoft.com...
> >> > We are using SQL 2K with sp4 on W2K servers but they are in windows
> >> > workgroup
> >> > not domain. The SQL service is started by the local system account. I am
> >> > having a hard time trying to back up a database to a remote shared folder
> >> > located in another W2K server in the same windows workgroup. I believe it
> >> > is
> >> > an authentication/permission issue. I am aware that SQL server looks at
> >> > network shared folder differently than the way Windows see but don't know
> >> > how to get around it under the workgroup setup. If it is under domain
> >> > setup,
> >> > I have no problem.
> >> >
> >> > Any help on this is very much appreciated.
> >> >
> >> > Wingman
> >>
> >>
> >>
>

Back up of Encryption Keys and changing Windows Service Identity

I need to change windows server identity for the report service but I get
following error for this operation
ReportServicesConfigUI.WMIProvider.WMIProviderException: Key not valid for
use in specified state. (Exception from HRESULT: 0x8009000B)
at
ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject
mo)
at
ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]&
encryptedBytes, String password)
What is a solution for this?
Thanks,
ShimonOn Dec 10, 8:11 pm, "Shimon Sim" <shimonsim...@.community.nospam>
wrote:
> I need to change windows server identity for the report service but I get
> following error for this operation
> ReportServicesConfigUI.WMIProvider.WMIProviderException: Key not valid for
> use in specified state. (Exception from HRESULT: 0x8009000B)
> at
> ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject
> mo)
> at
> ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]&
> encryptedBytes, String password)
> What is a solution for this?
> Thanks,
> Shimon
This link might be helpful.
http://www.developmentnow.com/g/115_2007_5_0_0_973220/Report-Server-Windows-Service-MSSQLSERVER.htm
Regards,
Enrique Martinez
Sr. Software Consultant

Avoiding the usage of DTC

Hello

I am running an script and the following sentence throws and error because the DTC service is not running in the Remote Server:

insert into MyLocalTable
execute synonym_MyRemoteProcedure @.SomeParameter

Since a transaction is not declared within the script, why is the DTC required?
How can I avoid the usage of the DTC? Is there a way to say "this code is not within a distributed transaction"?

Thanks a lot.You are still in an explicit transaction. As far as I know, the requirement that the DTC service be running can not be bypassed. You can try using just a select statement to get the data from the remote server, as the "black box" nature of the stored procedure may be causing this.

Avoid windows login prompt while accessing report server.

Hi,

We are using Microsoft Reporting Service 2005 to develop reports and we are accessing these reports through a J2EE application.
The front end is implemented using Tapestry and we using JBoss as our applicaiton server.
We are using Shared Data Sources for the reports and we set its data source type to SQL Server Analysis Services.
In the credential tab, by default "Use Windows authentication" is selected. All other options are disabled.

When I access my reportserver through my web application, I am always prompted for a windows login and password.
How can I avoid being shown the windows login prompt, since our web application will be used by several users and we do not want the users to type in a username/password everytime they want to access our reports.

Please suggest me solution for this scenario.

Thanks in advance!

Hi,

i think the core problem is, that you use windows integrated authentication. In this case the current login user on the client is used to authenticat the access to the database, if this user dont have access rights to the database, you get the login prompt.

Perhapse it is possible for you to set fixed credentials in the shared datasource?

Tibor Csizmadia

|||

How do I give the users access rights to the database? and there may be so many users invoking the reports through our web application.

As I mentioned in my earlier post when I create a new shared data source in my report project, in the Credentials tab "Use Windows Authentication (Integrated Security)" is selected by default. All other options are disabled so I cannot set any other credentials.

Why is it that I can select credential only as "Windows Authentication" is it because the data source type is selected as SQL Server Analysis Services?

Also one thing I forgot to mention is that we are using SQL Server 2005 Standard Edition

|||

Hi,

if you want to use the integrated security, i would create a security-group the the users who have access to the database. Then asign in the SQL-Server-Management Studio this security group to the database (Security/Logins, Add new User, choose the security-group from the AD, assign the Database to access throu this group).

I doent know why you can only use the windows Authentication for "Microsoft SQL-Server Analyse Services" in VS.NET, but if you define the share datasource in the reporting-managment website (http://localhost/Reports) you can set outher authentications...Perhaps MS have for this an explanation.

I hope this help you.

Tibor Csizmadia

Average of average in SP2

Does anyone know if we are expecting this to be included in Service Pack 2
at all?
Cheers
GavinNot that I am aware of (and I doubt it will be due to this being an
enhancement). The only enhancements I am aware of are printing support and
web parts for sharepoint. Everything else is bug fixes.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Gavin Pollock" <gpollock@.challow.removethis.net> wrote in message
news:uZAVaGl8EHA.2156@.TK2MSFTNGP10.phx.gbl...
> Does anyone know if we are expecting this to be included in Service Pack 2
> at all?
> Cheers
> Gavin
>|||Ah well, pity. Thanks, Bruce.
Is there a road map for enhancements planned out, or not really? I guess not
at this stage...
Cheers
Gavin
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23QbAsmm8EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Not that I am aware of (and I doubt it will be due to this being an
> enhancement). The only enhancements I am aware of are printing support and
> web parts for sharepoint. Everything else is bug fixes.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Gavin Pollock" <gpollock@.challow.removethis.net> wrote in message
> news:uZAVaGl8EHA.2156@.TK2MSFTNGP10.phx.gbl...
>> Does anyone know if we are expecting this to be included in Service Pack
>> 2
>> at all?
>> Cheers
>> Gavin
>>
>

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

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
>

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