What if the SQL Server proxy service cannot be started?

What if the SQL Server proxy service cannot be started?

The problem of SQL Server proxy service being unable to start is indeed a headache for us. The following describes how to solve the problem that SQL Server proxy service cannot be started.

Configuration environment:
The server environment is 32-bit Intel®Xeon®CPU E54410 @ 2.33GHz dual-core dual-enable hyper-threading, 8.00GB memory, RAID10.

1. Based on the minimum permission principle, after installing the database and SP3 patch, create the Users Group user SqlStartUser.

2. Enable the TCP/IP protocol through the SQL Server Configuration Manager, and change the TCP port of IPALL to 32959. The Service Startup accounts of SQL Server (MSSQLSERVER) and SQL Server Agent (MSSQLSERVER) are SqlStartUser.

3. Choose Local Security Settings> Local Policies> User permission assignment> Memory Locking page to add SqlStartUser.

4. Select AWE to allocate memory. The Minimum Server Memory (MB) is 5500, and the maximum server memory (MB) is 7200.

Check Procedure:

1. check which groups the local account SqlStartUser belongs to: the Users Group in the local Windows Group; the SQL Server service account group SQLServer2005MSSQLUser $ DBSRV1 $ MSSQLSERVER in the local Windows Group; SQLServer2005SQLAgentUser $ DBSRV1 $ MSSQLSERVER in the SQL Server service account group of the local Windows Group.

2. Check whether the database login name has DBSRV1 \ SqlStartUser.

3. Check the Event Viewer application's Service Startup Process Information:

Type source description

① MSSQLSERVER user 'dbsrv1 \ sqlstartuser' is successfully reviewed. Connection: trusted. [client: <local machine>]

② The Information MSSQLSERVER configuration option 'show advanced options' has been changed from 1 to 1. Run the RECONFIGURE statement for installation.

③ MSSQLSERVERSQL Server blocks access to 'dbo. sp_sqlagent_has_server_access 'During the 'agent XPs' process of the component because the component has been disabled as part of the Server security configuration. The system administrator can enable 'agent XPs 'by using sp_configure '. For more information about enabling 'agent XPs ', see "peripheral application configurator" in SQL Server books online ".

④ MSSQLSERVERSQL Server blocks access to 'dbo. sp_sqlagent_get_startup_info 'during 'agent XPs ......

⑤ Error MSSQLSERVERSQLServerAgent cocould not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but "(unknown)" is not a member of the SysAdmin role ).

The component 'agent XPs 'cannot be started from information ③ and ④. Log on to the system administrator to execute the statement:

sp_configure 'show advanced options', 1;GORECONFIGURE;GOsp_configure 'Agent XPs', 1;GORECONFIGURE;GO

The error message shows that you do not have the permission to expand the memory physical address. The reason is 32-bit machine. AWE support is enabled and the Service Startup account is changed. However, this account is not added to the security management on the Memory Lock page, therefore, the SQL proxy service fails to be started. You can add the SqlStartUser account to the memory to lock it.

The above is all the content of this article. I hope it will be helpful for your learning and support for helping customers.