SQL Agent wont start

I have recently bought a new a laptop running Windows 8 Pro and have tried to install SQL server 2008 and 2012 but all to the same effect the SQL agent wont start so I cant therefore connect to my database, I have tried everything on the forums but to no
avail I currently have 2012 version installed from this source: https://www.microsoft.com/en-gb/download/details.aspx?id=29062 first installing ENU\x64\SQLManagementStudio_x64_ENU.exe
then ENU\x64\SQLEXPR_x64_ENU.exe
The SQL agent wont start and currently returns with did not respond in a timely manner, the error logs dont present any useful information but can provide these if needed.
Please help I really need this to work if there is anything I have have missed please let me know and also if the is anymore information I can provide that will help thank you.

Hello,
As mentioned by jmcmullen, SQL Server Agent is a feature not available on SQL Server Express Edition.
Try the following workaround.
https://pianaro.wordpress.com/2012/12/05/how-to-schedule-jobs-in-sql-server-express/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

SQL Agent wont start after a SQL 2012 install

Ive been trying for several days to install an instance of SQL 2012 on a server, but im having this problem where when the instance is created, the SQL Agent shows 'Agent XPs disabled'.
I have enabled this using sp_configure 'Agent XPs',1
But when I turn on the agent it stays on for about 30 seconds and then turns off again. (It is 2012 enterprise i am using)
The agent service account is an administrator on the Server. I have installed SP1, but the agent keeps failing. I have installed 7 or 8 times.
Please help!
Thanks,
Zoe

That gives:
Microsoft
SQL
Server 2012
- 11.0.2100.60
(X64)
Feb 10 2012 19:39:15
Copyright
(c)
Microsoft
Corporation
Enterprise
Edition
(64-bit)
on
Windows
NT 6.1
<X64>
(Build
7601:
Service
Pack 1)
(Hypervisor)
My account is a member of the admin group yes.

Log Reader Agent and Snapshot Agent wont start

Hi There,
I've two SQL 2012 servers with multiple instances installed.
I've started replicating the databases in these instances using transactional replication and thus far they've worked without a hitch.
One of my instances, annoyingly, has an issue where the Log Reader Agent and Snapshot Agent refuse to start, and I've followed exactly the same process as with the other instances\databases.
The Agents are configured to make use of a domain user account with sysadmin permissions to the instances on both servers.
I get the following two error when I View Log Reader Agent Status:
The job failed. The Job was invoked by User sa. The last step to run was step 2 (Run agent.).
I've asked the agent to run as my DOMAIN\sqlservice account, so I've no idea why it's moaning about sa?!!?
I get the following error when I View Snapshot Agent Status:
The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Di
If I try to start either agent I'm told that the request to run job was refused because the job has been suspended, "Changed database context"?? Error 22022.
Can anyone help?

This is because your job owner is sa. Right click on your job and notice the owner - but is should be sa.
You likely have another issue. You may need to run the job and configure it for logging to see what the error is.
http://support.microsoft.com/kb/312292/en-us
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

SQL developer wont start on Mac OSX Lion

Hi there,
hoping someone can help me with this one, I've been running SQL Developer 3 on the macbook no problems for about a year, I recently upgraded to Mac OSX Lion and now when I try to start SQL Developer it will not run.
I have downloaded and installed the latest version of java as directed on the SQL Developer download page.
When I start SQL developer and view the Activity Monitor the "bash" process starts to use 100% CPU very quickly and SQL developer does not even get to the splash screen.
Can anyone point me in the right direction in terms of diagnosing this issue? Is there a log file I can review or way of starting SQL developer with specific arguments?
Kind regards,
stu

Irian wrote:
Usually the SetJavaHome points to the root directory for the JVM installation, this directory in your case appears to be
/Library/Java/JavaVirtualMachines/1.6.0_26-b03-383.jdk/Contents/Home
so try setting this in the SetJavaHome command for your SQL Developer (the bin folder will be added internally)
I'm not completely sure as i do not use macs, but it's worth a try.
Just had this same problem with Mountain Lion/SQL Developer 3.2.2, right after my upgrade to Mountain Lion. The path shown in Irian's response is what did the trick for me. The /System/Library/.... path shown by some others doesn't even exist on my machine. Interesting....
Earl

Automatically start SQL Agent service after SQL Server service fails and starts.

Hi!
I have SQL Server 2008 R2 with two main services - SQL Server and SQL Agent.
I'll try to describe my situation. It happens very occasionally, but sometimes SQL Server service terminates unexpectedly. It's my log:
09/13/2013 10:46:21,Service Control Manager,Error,The SQL Server (MSSQLSERVER) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service.
09/13/2013 10:46:21,,Error,[359] The local host server is not running,,,,
09/13/2013 10:46:22,MSSQLSERVER,Error,The MSSQLSERVER service terminated unexpectedly.,Server,1073760843,,
09/13/2013 10:46:22,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #1)...,,,,
09/13/2013 10:46:27,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #2)...,,,,
09/13/2013 10:46:32,,Warning,[139] AutoRestart: Attempting to restart the MSSQLSERVER service (attempt #3)...,,,,
09/13/2013 10:46:32,,Error,[140] AutoRestart: The MSSQLSERVER service could not be restarted after 3 attempts,,,,
09/13/2013 10:46:32,,Warning,[360] SQLServerAgent initiating shutdown following MSSQLSERVER shutdown,,,,
As you can see, SQL Server service terminates unexpectedly. Then SQL Agent service tries to start SQL Server service. After unsuccessfully attempts to start SQL Server service, SQL Agent service stops itself. I have the option setting in SQL Server
service to start itself after unexpectedly stop within 2 minutes and it is works well. But I have to start my SQL Agent service after this manually. Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly and in this case I just want
to make the settings to start both of my services SQL Server and SQL Agent automatically after this. How can I set up this? How can I make my SQL Agent service starts after SQL Server service?

Hello,
SQL server agent service depends on SQL server service so unless SQL server service comes online agent will not come online so agent is depended on SQL server not the other wise.
Now is your server 2008 R2 patched to latest service pack (SP2).If not please upgrade it to latest SP.Some fixes are there in Sp which will subside this issue.Can you paste output of
select @@version
>>Then SQL Agent service tries to start SQL Server service.No this is not the case
>>Unfortunately, I can't investigate the reason of my SQL Server stops unexpectedly
Did you checked sql server errorlog and windows event log completely.Please do so and paste if you find some more info
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

(SOLVED) My SQL wont start

So im in the process of setting up cherokee, ,PHP and MYSQL and i think i have the first 2 working but as for my sql it wont start. i run /etc/rc.d/mysqld start and it sits for a while and then fails. I followed the wiki article to set it up but it doest work. Im sure there is a log somewhere if it needs to be uploaded let me know. i did uncomment the lines for php.ini.
Last edited by Mazdaspeed6 (2011-12-18 00:47:45)

actually i was looking in the wrong path, here is the log entry that is repeated several times:
111212 16:01:11 mysqld_safe mysqld from pid file /var/lib/mysql/.pid ended
111212 16:58:42 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
111212 16:58:42 InnoDB: The InnoDB memory heap is disabled
111212 16:58:43 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111212 16:58:43 InnoDB: Compressed tables use zlib 1.2.5
111212 16:58:43 InnoDB: Initializing buffer pool, size = 128.0M
InnoDB: mmap(135987200 bytes) failed; errno 12
111212 16:58:43 InnoDB: Completed initialization of buffer pool
111212 16:58:43 InnoDB: Fatal error: cannot allocate memory for the buffer pool
111212 16:58:43 [ERROR] Plugin 'InnoDB' init function returned error.
111212 16:58:43 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
111212 16:58:43 [ERROR] Unknown/unsupported storage engine: InnoDB
111212 16:58:43 [ERROR] Aborting

Sql 2012 server for SCCM 2012 - Agent not starting

Hi ,
In our environment we have a Sql 2012, and it was working fine till now. but after installation of RDP role and subsequent installation of certificates for remote desktop in the SCCM server ( SQL 2012 is
installed in it)
we are facing the issue - Sql server management studio not connecting ( windows authenticaltion)
1) A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)A
2) I tried starting the sql agent service in services.msc and the below error came
The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped.
Some services stop automatically if they are not in use by other services or programs.
3) In the Sql Server configuration manager also tried starting the sql agent but
The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details.
The widows event logs show this error
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection.
The TLS protocol defined fatal error code is 20. The Windows SChannel error state is 960.
We have removed the certificate and the RDP role in that .
Can anyone please help on this
Anand M

I would check for error messages in the SQL Server ERROLOG file and also Agent's SQLAGENT.OUT file.
Tibor Karaszi, SQL Server MVP |
web | blog

Sql Server Agent not starting automatically in failover in a clustered environment.

Hi,
We are running Sql Server 2008 R2 as a 2 node cluster in Windows 2008 R2
server. In the Sql Server Configuration manager we find that service of
the Sql Server(database engine) as got a start mode as manual being
an instance in the 2 node cluster. When the node in which the service is
running fails the the Sql Server service gets started in the other node. However
we find that the Sql Server Agent service(whose start mode is also in manual)
does not get started automatically in the other node along with the Sql Server
service.Why does the cluster service do not start Sql Server agent service as well.
Should we make the Sql Server agent service start mode to be automatic
instead of being manual as it is now? Thanking you in advance
Binny Mathew

Folks - the startup type of all clustered services should be set to manual - when you virtualize SQL Services, they are put in manual startup mode and this should not be changed. It is the cluster manager which starts the SQL and SQLAgent when a
failover happens (SQL does not start SQLAgent). If your SQLAgent doesn't start after a cluster failover, check the SQLAgent logs to see what the root cause of the problem is and rectify it. You should not change the startup type to "Automatic" -
leave it as manual
Satish Kartan www.sqlfood.com
I suspect that your clustered SQLAgent resource is currently NOT dependent on SQL resource. If not, make SQLAgent dependent on SQL resource, which will coerce SQLAgent to wait for the SQL resource to come online before it brings itselft (SQLAgent) resource
online, when a failover happens.
Satish Kartan www.sqlfood.com

Starting sql agent manually - operating rules

Hi We run std 2008 r2. Today after overriding the 1st step's behavior in a sql agent job to end and report success after completing successfully, I
1) rt clicked "start at step..." (saw the turning green arrow on rt pop up immediately)
2) highlighted 1st step on left pop up and then clicked ok, that made left pop up go away
3) perhaps incorrectly clicked ok on rt pop up where green arrow shows
I don't see anything in view history for that job.
But yesterday when it failed same smoke test I saw (and continue to see) that failure entry in history.
Before clicking ok on rt pop up I saw "success" in step 1 on that pop up which was way too fast for the pkg it calls.
I see evidence in the pkg's flat log file that it at least started but I don't see any evidence that the log is growing which makes me think I shouldn't have clicked ok on the rt sql agent pop up.
I did what I could to look for evidence in running pkgs on the IS server that the pkg is still running but cant come to a definitive conclusion.
What are the rules and behavior when it comes to that rt popup where the green arrow revolves and someone is starting a sql agent job manually? Is it synchronous or asynchronous with its spawned ssis pkg? If its synchronous and I'm not supposed
to touch it while its running, how do I know when its done if it shows success in the status column right away?

Is it possible the Job is still running? Run the command below to see if it is still exectuting
EXEC msdb.dbo.sp_help_job
@Job_name = 'Your Job Name'
https://msdn.microsoft.com/en-gb/library/ms186722.aspx
Please click "Mark As Answer" if my post helped. Tony C.

SQL 2005 Server Agent not starting job

Apologies if this question has been asked elsewhere on these forums, I've had a search around and have not been able to find something with the same issues.
Last year I took over management of a SQL server (SQL2005 on a Server 2003 R2 O/S), as part of the expansion of operation the DB server is being used for an agent job was created to take customer information from our web site and, where the customer has
selected to be contacted, pass those details to our dialler system, so we can rech our customer ideally within 20 minutes of them interacting with the website.
This job runs daily Monday to Friday from 8am to 4:30pm at 15 minute intervals and once a day at 5pm on Saturday and Sunday(same job with muliple schedules), 3 week ago the Saturday job failed to start, then following week the Sunday job failed to start
then last weekend the job failed to start on both Saturday and Sunday. There have been no updates or changes made to the job or the server and the job has run for 6 months with this multiple scehduling without any issues at all.
I have checked through the server event/system/application logs and the SQL logs (that I know of) and can find no evidence of errors that would have an effect on the SQL or SQL Agent operation, I can also find no evidence that the server made an attempt
to start the job at all, the application log will normally show an event 12288 and 12289 with the source of SQLISPackage for the start and stop of the job. There is no event start notice shown in the application event log on weekend days the job has failed
to start. I've check the Agent service status, as well as all the other SQL services and they are all running as they should be.
Does anyone have any ideas where I should be looking next for the cause of this issue or has anyone ever experienced this before and found a cause?
Many thanks
Stuart.

Hi all,
thank you for your replies, I will try to address the issues/questions you have raised.
@Satish - The job takes on average 40 seconds to complete, so there would no chance of the previous job run still being active and stopping a new attempt. Also on the days that the job has failed it is the only time that day that the job is run.
@Sofiya Li - There are no errors to report, the job simply fails to start at all, this is bourne out
by the 'Job Step Execution History For The Last 7 Days' this shows no that the job ran sucessfully with no fails or retrys, so there are no error messages to post or invesitgate. Running the job manually results in a success (but the job runs every 15 minutes
anyway during the day without fails), the job uses the same credentials during the daily 15 minutes runs on weekdays as it does on the weekends, also if the website had any issues capturing customer information the missing information would not be in the table
that the dialling information is drawn from and the job should still start and run even if the website capture is not working(these are seperate jobs), it would just return no information.
@Shanky_621 There is normal scheduled maintenance that runs on the DB but this occurs at midnight. The
logs show that all services were running and nothing was in a wait/held state.
Thanks again for your suggesions
Stuart

Sql server agent not starting

I installed sql server 2008 r2 sp2
sql server agent is not allowing me to start it.
I run SSCM right click agent but start,stop menus are disabled

i have only one sql instance named SQLEXPRESS
The SQL Server Agent is installed with the Express Edition of SQL Server, but it's not a Feature of the Express Edition, therefore you can't start the Agent.
See
Features Supported by the Editions of SQL Server 2014
Olaf Helper
[ Blog] [ Xing] [ MVP]

SQL 2012 SqlAgent wont start

Hi,
I'm testing a new install of SQL server2012, and the SQLAgent will no longer start.
Build = Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
The SQL Agent log contains the following messages
2014-03-18 10:05:13 - ? [100] Microsoft SQLServerAgent version 11.0.3000.0 (X64 unicode retail build) : Process ID 6860
2014-03-18 10:05:13 - ? [495] The SQL Server Agent startup service account is WCM-LONDON\SQLControlservice.
2014-03-18 10:05:13 - ? [393] Waiting for SQL Server to recover database 'msdb'...
2014-03-18 10:05:13 - ? [000]
2014-03-18 10:05:13 - ? [101] SQL Server ????????? version 11.00.3000 (0 connection limit)
2014-03-18 10:05:13 - ? [102] SQL Server ODBC driver version 11.00.3000
2014-03-18 10:05:13 - ? [103] NetLib being used by driver is DBNETLIB; Local host server is ??????????????
2014-03-18 10:05:13 - ? [310] 1 processor(s) and 4096 MB RAM detected
2014-03-18 10:05:13 - ? [339] Local computer is ????????? running Windows NT 6.2 (9200)
2014-03-18 10:05:13 - ! [298] SQLServer Error: 17750, Could not load the DLL xpstar.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.). [SQLSTATE 42000] (ConnCacheSubsystems)
2014-03-18 10:05:13 - ! [449] Failed to enumerate subsystems (reason: Could not load the DLL xpstar.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.). [SQLSTATE 42000] (Error 17750))
2014-03-18 10:05:13 - ? [432] There are 0 subsystems in the subsystems cache
2014-03-18 10:05:13 - ! [000] Failed to load any subsystems. Check errorlog for details.
2014-03-18 10:05:13 - ? [000] Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install. [SQLSTATE 01000] (Message 15457)
2014-03-18 10:05:13 - ? [098] SQLServerAgent terminated (normally)
I've run dependency walker on the xpstarr and get the following list of dlls it can't find
API-MS-WIN-CORE-KERNEL32-PRIVATE-L1-1-1.DLL
API-MS-WIN-CORE-PRIVATEPROFILE-L1-1-1.DLL
API-MS-WIN-SERVICE-PRIVATE-L1-1-1.DLL
API-MS-WIN-CORE-SHUTDOWN-L1-1-1.DLL
EXT-MS-WIN-NTUSER-UICONTEXT-EXT-L1-1-0.DLL
IESHIMS.DLL
INSTAPI110.DLL
MFPLAT.DLL
SETTINGSYNCPOLICY.DLL
WLANAPI.DLL
Any advice on how to resolve this problem would be appreciated.
Sean

From the SQLAGENT Log
2014-03-18 10:05:13 - ! [298] SQLServer Error: 17750, Could not load the DLL xpstar.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.). [SQLSTATE 42000] (ConnCacheSubsystems)
2014-03-18 10:05:13 - ! [449] Failed to enumerate subsystems (reason: Could not load the DLL xpstar.dll, or one of the DLLs it references. Reason: 126(The specified module could not be found.). [SQLSTATE 42000] (Error 17750))
Looks like xpstar.dll could not be loaded. Follow the troubleshooting steps mentioned in
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/03/31/unable-to-connect-to-sql-server-2008-instance-after-applying-sp1.aspx and check if it resolves your issue.
- Feroz
Mark as Answer if it helps. This posting is provided "AS IS" with no warranties and confers no rights.

Error 17058 Unable to start a service account on MSSQLServer and SQL Agent

hi
I am intalling SQL 2008 standard with SP1 on a Windows Server 2003 R2 SP2.
I installed as "local service account" for MSSQLServer (SQL database engine) and SQL agent.
But I want to change to "service account" as [domain\svc_XXX] for MSSQLserver and SQL agent.
I add the [domain\svc_XXX] in local security policy - "Log as a service"
and also add in SSMS - Security - New Login (windows authentication.
When I started the MSSQLserver and SQL agent using the [domain\svc_XXX], I got an error 17058. Initerrlog: could not open error log file." Operating system error=3 (The system cannot find the path specified).
I don't know where else to look at..
Also, how do I find the cumulative service pack for SQL server 2008 standard?
thanks
Irene

Hi Irene:
By seeing your error message "When I started the MSSQLserver and SQL agent using the [domain\svc_XXX],
I got an error 17058. Initerrlog: could not open error log file." Operating system error=3 (The system cannot find the path specified)."
Please provide access to domain\svc_XXX on
log file directory.
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

After change port for TCPIP PORT for default SQL Server instance (MSSQLSERVER), sql service and sql agent service did not started again

Hi
-when i install default instance MSSQLSERVER i added a domain account as a service account,
- when i change port for TCPIP PORT , and after sql service and sql agent service did not started again.
it thrown error
The SQL Server (MSSQLSERVER) service failed to start due to the following error:
The service did not start due to a logon failure.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
but when i add domain\sqservice account in administrators group these services started,
1) here why this change behavior happened
2i changed the port 1500
adil

HI
the sql instance service is running with domain/sqlservice account ,
- i stopped the sql service service
- when i start it not started again and i found below error message
Domain and account: MOJPORTAL\spsqlservice
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this.
If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed,
check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7041</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2015-04-24T17:12:58.326973300Z" />
<EventRecordID>2177</EventRecordID>
<Correlation />
<Execution ProcessID="520" ThreadID="4044" />
<Channel>System</Channel>
<Computer>PORTALSQL1.mojportal.com</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">MSSQL$xSQL</Data>
<Data Name="param2">xxxL\spsqlservice</Data>
</EventData>
</Event>
adil

SQL Agent won't start

Hi,
I tried to start the SQL Agent on my SQL 2008 Server but got this error:
TITLE: Microsoft SQL Server Management Studio
Unable to start service SQLSERVERAGENT on server ACHSQL12. (mscorlib)
ADDITIONAL INFORMATION:
The SQLSERVERAGENT service on ACHSQL12 started and then stopped. (ObjectExplorer)
BUTTONS:
OK
Is there anything I should check?
Regards
Paul

You see the article for getting update :
Before you can start to use FILESTREAM, you must enable FILESTREAM on the instance of the SQL Server Database Engine. Enabling/configuring FILESTREAM is a bit different from configuring other SQL features because it involves making machine wide changes
and not only SQL instance changes. Also, FILESTREAM configuration has been changed for the February CTP to properly separate the Windows Built-in administrator and SQL administrator roles. In the November CTP, enabling/disabling FILESTREAM required Built-in
Admin privilege. Enabling FILESTREAM is now made up of 2 admin layers:
1-
The Windows configuration layer handles Windows related setup changes required for FILESTREAM. This requires built in administrator privilege. FILESTREAM settings in the SQL Configuration Manager (SQL-CM) represent this admin layer.
2-
The SQL configuration layer handles the setup changes required within the boundaries of the SQL instance. The SQL Admin can now use sp_configure/RECONFIGURE to handle this FILESTREAM configuration.
http://blogs.msdn.com/b/sqlserverstorageengine/archive/2008/03/03/filestream-configuration-and-setup-changes-in-sql-server-2008-february-ctp.aspx
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

SQL Agent wont start

Similar Messages

Maybe you are looking for