March 4, 2009 at 2:12 am
What could be the reason ?
SQLServerAgent could not be started (reason: This installation of SQL Server Agent is disabled. The edition of SQL Server that installed this service does not support SQL Server Agent.).
It was hen i try to start SQL Server Agent of 2008. Account is localsystem.
thanks,
CH&HU.
March 4, 2009 at 2:30 am
Hi,
Is it Express Edition which you have installed?
Regards,
Sakthi
My Blog -> http://www.sqlserverdba.co.cc
March 4, 2009 at 2:40 am
Which edition of SQL Server 2008 are you using?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
March 4, 2009 at 10:01 pm
it is Express edition.
Think it is disabled for Express Edition.
April 3, 2009 at 3:17 am
You mean to say that SQL Server Agent does nt work in SQL Express 2008 ? or is there any work around for to make Agent running?
April 3, 2009 at 6:57 am
CH&HU (3/4/2009)
it is Express edition.Think it is disabled for Express Edition.
No Express editions doesn,t add SQL Agent, you wouldn't be able to run it. If you want to schedule the option yo have got is to schedule Windows task scheduler or any third party scheduler
April 3, 2009 at 7:35 am
I think you are dealing with an exppress edition
[font="Comic Sans MS"]+++BLADE+++[/font]:cool:
April 4, 2009 at 12:26 am
Thanks Dude...
April 29, 2011 at 6:07 am
1. Is there any Microsoft Doc for this...that express edition doesnot not support sql server Agent
2. If express edition not supported sqlserveragent why it has given it in this edition...
3. I am getting thuis problem when I am starting Sqlserver Agent:
----------------------------------------------------------------
SQLServerAgent could not be started (reason: This installation of SQL Server Agent is disabled. The edition of SQL Server that installed this service does not support SQL Server Agent.).
------------------------------------------------------------------
4. The SQL SERVER Log Regarding this.
2011-04-29 17:11:47.11 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Express Edition with Advanced Services (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (Hypervisor)
2011-04-29 17:11:47.11 Server (c) Microsoft Corporation.
2011-04-29 17:11:47.11 Server All rights reserved.
2011-04-29 17:11:47.11 Server Server process ID is 2432.
2011-04-29 17:11:47.11 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2011-04-29 17:11:47.11 Server Authentication mode is MIXED.
2011-04-29 17:11:47.11 Server Logging SQL Server messages in file 'E:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2011-04-29 17:11:47.11 Server This instance of SQL Server last reported using a process ID of 3336 at 4/29/2011 5:10:59 PM (local) 4/29/2011 11:40:59 AM (UTC). This is an informational message only; no user action is required.
2011-04-29 17:11:47.11 Server Registry startup parameters:
-d E:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\master.mdf
-e E:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l E:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2011-04-29 17:11:47.11 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-04-29 17:11:47.11 Server Detected 1 CPUs. This is an informational message; no user action is required.
2011-04-29 17:11:47.14 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2011-04-29 17:11:47.17 Server Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-04-29 17:11:47.21 spid7s Starting up database 'master'.
2011-04-29 17:11:47.25 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-04-29 17:11:47.27 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:11:47.28 spid7s SQL Trace ID 1 was started by login "sa".
2011-04-29 17:11:47.28 spid7s Starting up database 'mssqlsystemresource'.
2011-04-29 17:11:47.28 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-04-29 17:11:47.58 spid7s Server name is 'PS01TC4VMAP321\SQLEXPRESS'. This is an informational message only. No user action is required.
2011-04-29 17:11:47.58 spid10s Starting up database 'model'.
2011-04-29 17:11:47.67 Server A self-generated certificate was successfully loaded for encryption.
2011-04-29 17:11:47.69 Server Server is listening on [ 'any' <ipv6> 1433].
2011-04-29 17:11:47.69 Server Server is listening on [ 'any' <ipv4> 1433].
2011-04-29 17:11:47.69 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2011-04-29 17:11:47.69 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2011-04-29 17:11:47.72 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2011-04-29 17:11:47.75 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/PS01TC4VMAP321.sbigen.in:SQLEXPRESS ] for the SQL Server service.
2011-04-29 17:11:47.75 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/PS01TC4VMAP321.sbigen.in:1433 ] for the SQL Server service.
2011-04-29 17:11:47.75 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-04-29 17:11:47.75 spid10s Clearing tempdb database.
2011-04-29 17:11:47.85 spid13s A new instance of the full-text filter daemon host process has been successfully started.
2011-04-29 17:11:47.85 spid10s Starting up database 'tempdb'.
2011-04-29 17:11:47.88 spid7s Starting up database 'msdb'.
2011-04-29 17:11:47.92 spid13s The Service Broker protocol transport is disabled or not configured.
2011-04-29 17:11:47.92 spid13s The Database Mirroring protocol transport is disabled or not configured.
2011-04-29 17:11:47.92 spid13s Service Broker manager has started.
2011-04-29 17:11:47.94 spid7s Recovery is complete. This is an informational message only. No user action is required.
2011-04-29 17:11:54.19 spid52 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:11:54.19 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:11:54.21 spid52 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:11:54.21 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:11:54.21 spid52 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:11:54.21 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:11:54.39 spid52 Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
2011-04-29 17:11:54.39 spid52 Using 'xpsqlbot.dll' version '2009.100.1600' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
2011-04-29 17:11:54.42 spid52 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:11:54.42 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:11:54.42 spid52 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:11:54.42 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:11:54.42 spid52 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:11:54.42 spid52 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:13:25.78 spid53 Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2011-04-29 17:13:25.80 spid53 Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2011-04-29 17:16:44.32 spid55 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:16:44.32 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:16:44.32 spid55 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:16:44.32 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:16:44.32 spid55 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:16:44.32 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:16:44.35 spid55 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:16:44.35 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:16:44.35 spid55 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:16:44.35 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:16:44.35 spid55 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:16:44.35 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:18:02.80 spid55 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:18:02.80 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:18:02.80 spid55 Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:18:02.80 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:18:02.80 spid55 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:18:02.80 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:18:02.84 spid55 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-04-29 17:18:02.84 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:18:02.84 spid55 Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:18:02.84 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:18:02.84 spid55 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2011-04-29 17:18:02.84 spid55 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2011-04-29 17:29:08.44 spid57 Starting up database 'ReportServer$SQLEXPRESS'.
2011-04-29 17:29:08.72 spid57 Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2011-04-29 17:29:08.85 spid57 Starting up database 'ReportServer$SQLEXPRESS'.
2011-04-29 17:29:09.04 spid57 Starting up database 'ReportServer$SQLEXPRESS'.
2011-04-29 17:29:09.12 spid57 Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2011-04-29 17:29:09.30 spid57 Starting up database 'ReportServer$SQLEXPRESS'.
2011-04-29 17:29:09.33 spid57 Starting up database 'ReportServer$SQLEXPRESSTempDB'.
2011-04-29 17:29:15.74 spid55 Attempting to cycle error log. This is an informational message only; no user action is required.
Thanks
April 29, 2011 at 11:56 pm
if you still want to use jobs to schedule scripts then use SQLCMD and Operating System schedule,make your script on SQLCMD and save as a batch file then schedule on operating system scheduler
Regards,
Syed Jahanzaib Bin Hassan
MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
May 1, 2011 at 9:25 pm
forsqlserver (4/29/2011)
1. Is there any Microsoft Doc for this...that express edition doesnot not support sql server Agent
Yes, it is documented that sql server Express Edition does not support Sql Agent.
Also read Features Not Present in SQL Server Express on this click for more details on features which are not present.
http://msdn.microsoft.com/en-us/library/ms345154(v=sql.90).aspx
Regards,
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply