Shulou(Shulou.com)05/31 Report--

This article is to share with you about the solutions that the SQL Server proxy service cannot start. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

The problem that the SQL Server proxy service cannot be started is really a headache for us. Here's how to deal with the failure to start the SQL Server proxy service. I hope it can be helpful to you.

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

1. According to the principle of minimum permissions, after installing the database and SP3 patches, establish the Users group user SqlStartUser.

two。 The TCP/IP protocol is enabled through the SQL Server configuration manager configuration, and the TCP port of IPALL is changed to 32959. The service startup account for SQL Server (MSSQLSERVER) and SQL Server Agent (MSSQLSERVER) is SqlStartUser.

3. Local Security Settings-> Local Policy-> user Rights assignment-> add SqlStartUser to locked pages in memory.

4. Check to use AWE to allocate memory. The minimum server memory (MB) is 5500, the maximum server memory (MB) is 7200, and the rest is left to the operating system.

Check the steps:

1. Check which groups the local account SqlStartUser belongs to: the Users group of the local Windows group; the SQLServer service account group SQLServer2005MSSQLUser$DBSRV1 $MSSQLSERVER; of the local Windows group; the SQLServer service account group SQLServer2005SQLAgentUser$DBSRV1 $MSSQLSERVER of the local Windows group.

two。 Check if the database login has DBSRV1\ SqlStartUser.

3. Check the event Viewer application for process information about service startup:

Type source description

① audit succeeded MSSQLSERVER user 'DBSRV1\ SqlStartUser' logged in successfully. Connection: trusted. [client:]

② Information MSSQLSERVER configuration option 'show advanced options' has been changed from 1 to 1. Please run the RECONFIGURE statement to install.

The ③ message MSSQLSERVERSQL Server blocks access to the component 'procedure of Agent XPs'' dbo.sp_sqlagent_has_server_access' because it has been shut down as part of the security configuration of this server. 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.

The ④ message MSSQLSERVERSQL Server blocks access to the component 'process of Agent XPs'' dbo.sp_sqlagent_get_startup_info'.

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

From the messages ③ and ④, we can see that the component 'Agent XPs' failed to start. Execute the statement through the system administrator login:

Sp_configure 'show advanced options', 1 / GORECONFIGURE / GOSPP configure' Agent XPs', 1 / GORECONFIGURE / go

The error does not have the permission to extend the physical address of memory. It is determined that the reason is the 32-bit machine, the AWE support is enabled, and the service startup account is changed, but this account is not added to the security management of the memory locking page, which leads to the failure of starting the SQL proxy service. Add the SqlStartUser account to the memory lock and start it.

Thank you for reading! This is the end of this article on "the solution to the failure of SQL Server Agent Service". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.