After MSDE SP4 installation SQL Agent is set to manual

I have over 500 PC's with a named instance of MSDE installed that I need to
install SP4 on. These PC's have the SQL Agent set to automatic. After
installing SP4 on a test box, this service was changed to manual by the
service pack. replication will not work if this service is not running.
Is there a way to have the service pack set this service to be set to
automatic? Is there a way to set it to automatic with a batch program or VB
script?
I can not manually change this service on over 500 PC's.
hi,
andersos wrote:
> I have over 500 PC's with a named instance of MSDE installed that I
> need to install SP4 on. These PC's have the SQL Agent set to
> automatic. After installing SP4 on a test box, this service was
> changed to manual by the service pack. replication will not work if
> this service is not running.
> Is there a way to have the service pack set this service to be set to
> automatic? Is there a way to set it to automatic with a batch
> program or VB script?
> I can not manually change this service on over 500 PC's.
I do think via WMI, but never tried it... perhaps you have to ask in some
dev's newsgroup
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Check out this article.
http://groups-beta.google.com/group/...e67c802edd178a
There is a registry key for this service. If you change the 'start'
property of this key, you can change the service from manual to automatic.
There are a number of ways to do this through code. These are the values for
this property.
Boot = 0,
System = 1,
Automatic = 2,
Manual = 3,
Disabled = 4
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent
|||It is cool that you even got msde upgraded on 500 users. I can't get one
installed to upgrade my default instance sp3a to sp4. You are a hero.
In BOL look up - scm Utility
If you can find the -StartupOptions for autostart, it looks like you can do
it with a bat file or xp_cmdshell.
We replicate a table with a trigger to dynamically execute sql on insert to
propagate fixes and procs.
My test install of sp4 ran well, then the status bar backed up and it
finished like all is well but .760 still shows in the version. Did you have
anything similar ? Care to share your command line secret? I have 150 users
to push to.
andersos wrote:
>Check out this article.
>http://groups-beta.google.com/group/...e67c802edd178a
>There is a registry key for this service. If you change the 'start'
>property of this key, you can change the service from manual to automatic.
>There are a number of ways to do this through code. These are the values for
>this property.
> Boot = 0,
> System = 1,
> Automatic = 2,
> Manual = 3,
> Disabled = 4
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\SQLAgent
|||C:\Program Files\Microsoft SQL Server\80\Tools\Binn>scm -Action 7 -Service
sqlserveragent -SvcStartT
ype 2
This does the job. Note this path may differ
andersos wrote:
>I have over 500 PC's with a named instance of MSDE installed that I need to
>install SP4 on. These PC's have the SQL Agent set to automatic. After
>installing SP4 on a test box, this service was changed to manual by the
>service pack. replication will not work if this service is not running.
>Is there a way to have the service pack set this service to be set to
>automatic? Is there a way to set it to automatic with a batch program or VB
>script?
>I can not manually change this service on over 500 PC's.
Mike Street
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...-msde/200507/1

After MDAC 2.8 - SQL with Named Pipes misbehaves

After installing MDAC 2.8 some stored procedures and some backup/restore stopped working and generates:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
If you register and/or use TCP/IP sockets, everything works fine.
Has anyone experienced this problem?
It sounds like you maybe running into the following problem:
FIX: General Network Error When You Try to Back up or Restore a SQL Server
Database on a Computer That Is Running Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;[LN];827452
You can contact Microsoft Product support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank you.

After MDAC 2.8 - SQL with Named Pipes misbehaves

After installing MDAC 2.8 some stored procedures and some backup/restore sto
pped working and generates:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (Wra
pperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
If you register and/or use TCP/IP sockets, everything works fine.
Has anyone experienced this problem?It sounds like you maybe running into the following problem:
FIX: General Network Error When You Try to Back up or Restore a SQL Server
Database on a Computer That Is Running Windows Server 2003
http://support.microsoft.com/defaul...scid=kb;[LN];827452
You can contact Microsoft Product support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank you.

After MDAC 2.8 - SQL with Named Pipes misbehaves

After installing MDAC 2.8 some stored procedures and some backup/restore stopped working and generates
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead())
Server: Msg 11, Level 16, State 1, Line
General network error. Check your network documentation
If you register and/or use TCP/IP sockets, everything works fine.
Has anyone experienced this problem?It sounds like you maybe running into the following problem:
FIX: General Network Error When You Try to Back up or Restore a SQL Server
Database on a Computer That Is Running Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;[LN];827452
You can contact Microsoft Product support to get the fix.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank you.

After enabling named pipes and disabling again, not able to start engine

I enabled then disabled named pipes. Now when I try to start the SQL Engine, I get this error:

TITLE: Connect to Server

Cannot connect to ****** (replaced my servername with stars here for privacy).

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK

found it, I had also enabled IP1 and IP2 which prevented me from connecting it apears|||It also seems that there's a bug in ASP.NET that prevents the Named Pipes protocol from being able to be used in default setup configuration. Perhaps this isn't experienced by many people as TCP/IP connections are also enabled by default and they work. Have a look here:

BUG: Named pipes do not work when worker process runs under ASPNET account
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315159

I've found this really annoying (at least now I've found that it's really a bug, and not something I had misconfigured), as I had disabled TCP/IP for security reasons.

After enabling named pipes and disabling again, not able to start engine

I enabled then disabled named pipes. Now when I try to start the SQL Engine, I get this error:

TITLE: Connect to Server

Cannot connect to ****** (replaced my servername with stars here for privacy).

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476

BUTTONS:

OK

found it, I had also enabled IP1 and IP2 which prevented me from connecting it apears|||It also seems that there's a bug in ASP.NET that prevents the Named Pipes protocol from being able to be used in default setup configuration. Perhaps this isn't experienced by many people as TCP/IP connections are also enabled by default and they work. Have a look here:

BUG: Named pipes do not work when worker process runs under ASPNET account
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q315159

I've found this really annoying (at least now I've found that it's really a bug, and not something I had misconfigured), as I had disabled TCP/IP for security reasons.