One of my clients has installed a new instance of SQL Server and then wanted to create maintenance plan. They were complaining about getting some error and we’re looking forward for my help to solve the same. As soon as he did right click on a Maintenance Plan under “Management” node and selected “New Maintenance Plan Wizard” using SQL Server Management Studio as shown below. Let us learn how to fix Agent XPs Component is Turned Off as Part of the Security Configuration for this Server error.
It gave below error.
Here is the text of the message.
TITLE: Microsoft SQL Server Management Studio
Cannot show requested dialog.
Unable to execute requested command.
‘Agent XPs’ 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. (Microsoft.SqlServer.Management.MaintenancePlanWizard)
There are two ways to fix the problem.
- Start SQL Server Agent Service.
You can also start SQL Server Agent service by using the SQL Server Configuration Manager on start>run>services.msc applet.
- Enable Agent XPs under sp_configure using below command in SQL Server Management Studio query window.
SP_CONFIGURE 'SHOW ADVANCE',1 GO RECONFIGURE WITH OVERRIDE GO SP_CONFIGURE 'AGENT XPs',1 GO RECONFIGURE WITH OVERRIDE GO
Here is the output
Configuration option ‘show advanced options’ changed from 0 to 1. Run the RECONFIGURE statement to install.
Configuration option ‘Agent XPs’ changed from 0 to 1. Run the RECONFIGURE statement to install.
Once any of the above is followed, you should be able to create maintenance plan. You might ask, why someone would need use # 2 instead of # 1. It is important to remember that if you want to create maintenance plan without starting SQL Agent service (as it might cause jobs to run which are scheduled) then you would choose option 2. A very uncommon but possible scenario.
If you are not able to start SQL Server Agent service, then you may want to look at below blog
There might be some other error but SQLAgent.out and event log is a good place to start troubleshooting the issue. Do let me know if you encountered this error ever in your environments. Do leave a comment.
Reference: Pinal Dave (https://blog.sqlauthority.com)