SQL Server 2008 :: Unable To Start Agent Due To Blocked Access
Jun 28, 2015
Had some big problems with my SQL Server 2008 R2 SP1 during the last maintenance running on Windows Server 2008 R2 Enterprise ( upgraded from Standard). I'm getting the following error,
"SQL Server blocked access to procedure 'dbo.sp_sqlagent_has_server_access' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online."
I did a google search and found others with the problem but the resolution isn't working for me. I ran the following commands, heck I ran them multiple times. No errors come back running these commands. But the same error keeps happening, I even restart the service and then the server again.
sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'Agent XPs', 1;
GO
RECONFIGURE
GO
The msdb got too big for the disk it was on. I had maintenance plans to clear out the all of histories but I didn't think of the mail items. When I finally saw this problem I tried clearing them out using the stored procedures only with it finally failing because the transaction log got full. Since we didn't have a lot of jobs scheduled I decided to just recreate the msdb. So I scheduled a maintenance window, download SQL Server Service Pack 3.
my steps are as follows:
->diff backup of msdb
->stopped the service and started it again with: NET START MSSQLSERVER /T3608
->detached msdb with: SQLCMD -E -SP-SRVR-SQL-01 -dmaster -Q"EXEC sp_detach_db msdb"
->moved it off the drive
->restarted the service without any startup flags
->recreated msdb with: SQLCMD -E -SP-SRVR-SQL-01 -i"D:Microsoft SQL ->ServerMSSQL10_50.MSSQLSERVERMSSQLInstallinstmsdb.sql" -o"D:Microsoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLInstallinstmsdb62715.out"
I looked at the log file and there were no actual error messages so I applied service pack 3 and restarted server after it installed, was actually prompted to restart. In my tests I was never prompted to restart the server.Now I never started the agent service after recreating the msdb database since I knew it wasn't on the same version. I just went directly to the latest SP. Our applications are running fine but now I cant do scheduled backups.
I need to start SQL Server Agent so that I can run scheduled jobs. I am running SQL Server 7.0 with windows NT 4.0 service pack 4. When I try to start the agent I get the following error
Error 22003: StartService() returned error 5,'Access is denied'
Does anyone have an idea as to why this is happening? Any help with this problem would be appreciated. Thanks
As my sql agent is not starting due to XP's are disabled . when I ran the sp_configure with override and changed to 0 to 1 when I am starting the agent the configured value will be back to again 0 and in logs.Waiting for SQL Server to recover database 'msdb'...ODBC Error: 0, Invalid character value for cast specification [SQLSTATE 22018]
I have changed SQL Server from default port to another port number. All appears fine. If SQL Server is restarted it is all fine, however, when the server is restarted SQL Server fails to start. If you then log into the server and manually start the services they start just fine. So, it appears that something blocks the port or uses the port upon server startup for a few seconds. The AV folks say that they are not blocking ports and that it AV service actually starts 15 seconds after the SQL start failure.So, the question becomes is how can I track down what is blocking or using that port?
This is Win2012/SQL2014 CU3
Server failed to listen on xxxxx::xxxxxxxxxx <ipv6> xxxxx. Error: 0x2741. To proceed, notify your system administrator.
Server failed to listen on fe80::5efe:10.255.196.25%18 <ipv6> 14001. Error: 0x2741. To proceed, notify your system administrator.
TDSSNIClient initialization failed with error 0x2741, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The requested address is not valid in its context.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
I'm trying to connect to a database using a service account that we got created. The ID is an AD account and was added to the db as such. When I try to connect to the database using the account with the password I get [login failed for domainid]. The DBA mentioned that its setup to use windows auth, however, I can't connect with this service account using windows Auth, due to I'm using to connect via code.
How can I connect to the database from my code using this ID?
I have the ID and pwd in my code to connect with, does the ID have to be setup differently in the Database?
I have installed sqlserver 2005 using the standard msdn universal installation discs on my laptop running vista business.
The mssqlserver service will not start automatically as the setup configures it and I cannot start the service manually because I get the 'Access Denied' error message
I am logged on the the computer with adminstration privileges
We are having problems w/ our agent. When we try to start it in computer management, it will say the agent started then stopped because it has nothing to do. In surface area config, when we try to start it it times out. Does anyone have experience with this? We are desperate. Thanks!
I cannot run SQl Server Agent service. Each time I try I get these 2 errors
Event Type:Error Event Source:SQLAgent$MY_INSTANCE Event Category:(2) Event ID:17310 Date:18/06/2007 Time:09:27:49 User:N/A Computer:MY SERVER Description: A user request from the session with SPID 53 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data:
Event Type:Error Event Source:SQLAgent$MY_INSTANCE Event Category:Service Control Event ID:103 Date:18/06/2007 Time:09:27:49 User:N/A Computer:MY SERVER Description:
SQLServerAgent could not be started (reason: SQLServerAgent cannot start because the msdb database is not set to a compatibility level of 70 or higher).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I am on SQL Server 2005. Do you have any ideas what might cause it and how to fix it?
I cannot run SQl Server Agent service. Each time I try I get these 2 errors
Event Type: Error Event Source: SQLAgent$MY_INSTANCE Event Category: (2) Event ID: 17310 Date: 18/06/2007 Time: 09:27:49 User: N/A Computer: MY SERVER Description: A user request from the session with SPID 53 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data:
Event Type: Error Event Source: SQLAgent$MY_INSTANCE Event Category: Service Control Event ID: 103 Date: 18/06/2007 Time: 09:27:49 User: N/A Computer: MY SERVER Description:
SQLServerAgent could not be started (reason: SQLServerAgent cannot start because the msdb database is not set to a compatibility level of 70 or higher).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I am on SQL Server 2005. Do you have any ideas what might cause it and how to fix it?
hi guys i keep getting this error when trying to start the sql server agent service.
"The SQLSERVERAGENT service on Local Computer started and then stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service".
the SQL server service starts fine and i tryied starting the agent with the same user but it fails still.
Hello everyone! We had an issue this week where SQL Server Agent did not restart automatically. Weekly maintenance runs on the server each Sunday in which a reboot of the server occurs. Both SQL Server and SQL Server Agent are set to auto-start when OS starts. SQL started fine, but SQL Server Agent didn't.
Anyone know of a reason why SQL Server Agent wouldn't have restarted? Also, does anyone know of a way to set something up that would alert me (through email) if this service hasn't restarted?
I have 2 servers that are members of the same AD Domain.
I need an account that can login to either one, but needs to be able to start a service, which my network admin says a local domain administrator cannot do.
So, I just decided to create an account with the same name, properties and password on both machines.
This I did. The account is a member of local Windows Administrator group on each server. Additionally, it is an SQL account on the SQL Server local instance, and a member of the SysAdmin group.
I can assign this account to SQL Server as the startup account (Log in with this account). That works fine. However, when I assign this account to SQL Server, then SQL Server Agent quits running. So I try to assign this same account to this service and I get an error that the account 'Unknown' cannot login and needs to be a member of the SysAdmin group!??
This is a completely confusing error message since the account is a Windows Admin, SQL Server SysAdmin account and can start SQL Server fine without a hitch.
We just moved source server to newer, bigger box ... Windows 2003 and Active Directory ... Snapshot agent worked but distribution failed ... Same login as on older machine, login is sysadm, used DCOMCNFG to allow ability to launch process ... What are we missing?
My Server service will not start, i get a message saing consult the logs, in the error logs it says error in the model db .ldf file. However, i can not connect to the server to restore from my back ups. I get the error msg, your server may not be configured to accept remote connection. No, i dont know what im doing and my only though is to start from scratch reinstalling the server. Any help is apreciated.
I am not successful in getting SQL Server Agent to startup when SQL server starts up.
I believe the problem has to do with a lack of permissions or rights. I will list the steps below which seem to me to be all that are needed to install SQL Server Agent. I used Enterprise Manager to get this information.
If anyone can shoot any holes in the process, please do, that may be where my problem lies.
a. Created NT accounts called MSSQLSERVER for the server and MSSQLSERVERAGENT for SQL Agent.
b. Each of these accounts has the "right" to logon as a service.
c. Each of these accounts has "admin" rights.
d. Each of these accounts has been added to SQL SERVER under Security and Logins.
e. The properties assigned to each of the accounts are: (1) on the general tab -- Windows NT authentication is in effect, database is master and language is English (2) on the server roles tab -- System Administrators is checked (3) on the database access tab -- the master database is checked
f. Under SQL Server Agent, properties, selecting the General Tab, in the frame titled "service startup account": (1) the circle labelled "this account" is clicked (2) the account is filled in using domain namemssqlserveragent (3) the correct password is filled in taking case into consideration
g. Under SQL Server Agent, properties, selecting the Connection Tab, in the frame titled "sql server connection": (1) the circle labelled "use windows NT authentication" is clicked
h. Right clicking the server and selecting properties show a multi-tab window (1) the general tab shows that all three autostart boxes are checked (2) the security tabs shows SQL Server and Windows authentication are in effect (3) the startup service account shows "this account" selected and the account is filled in with domain namemssqlserver and the password is filled in (taking case into consideration)
In all cases above, the domain name is not the domain in which the server resides, but is in a "trusted" domain.
Two NT accounts have been created on the server. MSSQLSERVER MSSQLSERVERAGENT
These accounts have been given: a. logon rights b. unchangeable passwords c. passwords which never expire d. NT admin rights
Questions:
a. Do I have to create a login account within SQL Server 7 itself for these accounts? b. Must the properties for "this account' box on the general tab include the domain name? c. If the answer to (b) is yes, then can I use ".MSSQLSERVERAGENT" in the "this account" box on the general tab? d. Does the SQL Server Agent function require the "BUILTINadministrators" login in order to work?
Any help in figuring out why I can't get my SQL Server Agent to startup will be appreciated!!
I have a job in SQL Server agent with 199 SSIS steps and growing. In the job log only 99 steps are shown, which is a problem if a step higher than 99 fails to run. I need the steps to run in sequence and preferable would like to split the job into several jobs each containing no more than 99 steps. The only thing I don't know is if it is possible to have the next job in sequence start only when the previous job has finished.
Does anyone know if this is possible, and if so how it is done?
When i started the service, i am getting the following message Starting up database 'master'. Error: 9003, Severity: 20, State: 1. Cannot recover the master database. Exiting.
i tried starting using -f -m paramters,but could not succeed i don't have any backups for master database is there any way i can restore it from .mdf, .ldf files..
I have a client server application and it is running in the following configuration: SERVER A: MS Server2003 with MS SQL2000, Our ERP application software is installed on this server as is MS SQL200.
Server B: is our e-commerce server and it is running MS Windows2000 server OS and no MS SQL. The e-commerce application is pointed to the active SQL server on server A. I am trying to run a software version upgrade on on software application (which was successfully run on server A) When we try to run this upgrade on server B we get a message: " Setup is unable to start MS SQL Server Services, please start and try again"
I do not understand what is going on with this. SQL & SQL Service Agent is running on Server A. Any suggestions as to what I need to do?
I would appreciate any help here at all. I am pulling my hair out!
I am unable to start the snapshot agent or log reader agent from within SQL management studio. it fails on executing step 2 with unknown username or bad password.
I have checked all account details and they are correctly using my domain admin account. I can connect to SQL using teh same account and it also has sysadmin permissions.
If i copy the step 2 paramters and start from the cmd prompt (again logged in using the same domain account) they both start fine.
I am testing peer to peer replication in our environment. I simulated a three node peer to peer topology and a local distributor.
For some wierd reason I cannot get the Log Reader Agent and snapshot agent to start. The domain account under which SQL Server Agent runs has administrator previlage on the box. I also use a domain account for SQL Server Service. (none of the passwords changed).
This is the error I am getting - "Executed as user: abc. A required privilege is not held by the client. The step failed"
Hello, I've configured SQL Server 2000 for merge replication and am trying to start the snapshot agent for the publication and after about 20 minutes of it trying to start, it gives up with this error.
Server execution failed
There is no more information in the event viewer. I've tried it with a bunch of different subscriptions. SQL Server and SQL Agent are running under a local account which has access to the replcation data directory. SQL Agent is running.
Ran the SP2 locally on a Windows Server 2003 SP1 box that had SQL Server 2005 SP1 install on it. Problem was I ran out of C: drive and it failed in the middle of upgrading the server.
I'm unable to start the SQL Server at all now. Is there any way to back this out? Don't think I can reapply any patches since the service is dead.
Eventlog now shows: One or more files do not match the primary file of the database. If you are attempting to attach a database, retry the operation with the correct files. If this is an existing database, the file may be corrupted and should be restored from a backup.
The log shows it's unable to start SQL (blames it on permisions but it's because SQL can no longer start)
Product : Database Services (MSSQLSERVER) Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29538 Error Description : MSP Error: 29538 SQL Server Setup did not have the administrator permissions required to rename a file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmssqlsystemresource1.mdf. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.
I'm guessing its reinstall time but not sure how the attached databases will like that idea.
Please help! I cannot debug CLR procs remotely. Whenever I try to start debugging in VS2005 I get the error: Unable to start T-SQL Debugging. Could not attach to SQL Server process on .... I have clr enabled set to 1 and I have Allow SQLCLR Debugging set on. But I continue to get this error. Any help would be greatly appreciated.
I have installed the November CTP of SQL Server Express 2008 but the service will not start. The error log displays the following error which implies that it is trying to open a file on by CD/DVD drive. I have checked the service properties and all the parameters point to c:
Any idea why it is looking at e:? Where do I change this?
Starting up database 'mssqlsystemresource'. 2007-12-16 09:46:43.82 spid7s Error: 17204, Severity: 16, State: 1. 2007-12-16 09:46:43.82 spid7s FCB:pen failed: Could not open file e:sql10_main_tsqlmkmastrobjfrei386mssqlsystemresource.mdf for file number 1. OS error: 21(error not found). 2007-12-16 09:46:43.85 spid7s Error: 5120, Severity: 16, State: 101.
Hi can someone help me please? I browsed through the SP2 install feedback below, but it doesn't quite seem to fit what happened to my install. My .MDF and .LDF files for the system databases are in C:Program FilesMicrosoft SQL ServerMSQL.1MSQLData (I presume this is the correct location.)
I am the local administrator on this box.
I uploaded the .CAB file with all the logs onto www.sendspace.com if it gives you something to go on.
The only other thing of note is that it said there were two machines on the network and that I needed to change my machine name in the control panel when I installed. This doesn't seem right, as far as I understand the computer name is unique.
The SQL Server runs under the local system account, if that is of any use.
I attempted uninstalling and reinstalling the SQL native client MSI package in the hope it would be a simple fix similar to that chap further down the page, but that didn't help at all either.
.CAB file of installation logfiles is here: http://www.sendspace.com/file/7ihoet
kind regards Jason
ERRORLOG starting SQL Server post failed SP2 install
2007-06-12 19:55:21.94 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-06-12 19:55:21.96 Server (c) 2005 Microsoft Corporation. 2007-06-12 19:55:21.96 Server All rights reserved. 2007-06-12 19:55:21.97 Server Server process ID is 5468. 2007-06-12 19:55:21.97 Server Authentication mode is MIXED. 2007-06-12 19:55:21.97 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-06-12 19:55:21.97 Server This instance of SQL Server last reported using a process ID of 5756 at 12/06/2007 19:36:35 (local) 12/06/2007 18:36:35 (UTC). This is an informational message only; no user action is required. 2007-06-12 19:55:21.97 Server Registry startup parameters: 2007-06-12 19:55:21.99 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2007-06-12 19:55:21.99 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-06-12 19:55:21.99 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2007-06-12 19:55:22.00 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-06-12 19:55:22.00 Server Detected 4 CPUs. This is an informational message; no user action is required. 2007-06-12 19:55:22.17 Server Address Windowing Extensions is enabled. This is an informational message only; no user action is required. 2007-06-12 19:55:22.33 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. 2007-06-12 19:55:22.57 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-06-12 19:55:23.60 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-06-12 19:55:23.63 Server Database mirroring has been enabled on this instance of SQL Server. 2007-06-12 19:55:23.72 spid5s Starting up database 'master'. 2007-06-12 19:55:24.07 spid5s SQL Trace ID 1 was started by login "sa". 2007-06-12 19:55:24.11 spid5s Starting up database 'mssqlsystemresource'. 2007-06-12 19:55:24.13 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-06-12 19:55:24.29 spid5s Server name is 'GBLOND088SQ8MSQL_CREDS_DEV1'. This is an informational message only. No user action is required. 2007-06-12 19:55:24.29 spid9s Starting up database 'model'. 2007-06-12 19:55:24.30 Server Error: 17182, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server TDSSNIClient initialization failed with error 0x34, status code 0x1e. 2007-06-12 19:55:24.30 Server Error: 17182, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server TDSSNIClient initialization failed with error 0x34, status code 0x1. 2007-06-12 19:55:24.30 Server Error: 17826, Severity: 18, State: 3. 2007-06-12 19:55:24.30 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 2007-06-12 19:55:24.30 Server Error: 17120, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Hi again! I would like to thank the 2 persons which I had an answer from my previous question first. Thanks a lot !
But, it didn't quite answer my question so I'll give a bit more info. I would like to know if I can make a batch file, that excutes or starts an active script in SQL Server Agent (that is in SQL Enterprise Manager). If I can, can you give me more info on how to do it (command line, parameters), a web site, anything that can help me to that.
If I cannot do that, let me know please. Thanks a lot!
