Remote Procedure Call (RPC) Locator (System Services for the Windows Server 2003 Family and Windows XP Operating Systems)
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Service Name: RpcLocator
Executable Name: Locator.exe
Log On As: NetworkService
Description: The Remote Procedure Call (RPC) Locator service enables RPC clients using the RpcNs family of APIs to locate RPC servers, and manages the RPC name service database.
The RPC Locator service (also known as RPC Named Service) can locate other services on the network. The instance of the RPC Locator service that runs on a domain controller acts as repository for information about other RPC services that are active on the network. If you run the RPC Locator service in Windows 2000 or Windows Server 2003, backup storage for information about other services on the network is Active Directory. The instances of the RPC Locator service that run on individual computers act as computer-wide caches for information about other services on the network. Those services that need to be located through the RPC Locator service register with the RPC Locator service. The RPC APIs that start with the prefix RpcNs are used to register services with the RPC Locator service and query the RPC Locator service about previously registered services.
For more information about the RpcNs family of APIs, see the Software Development Kit (SDK) information in the MSDN Library link on the Web Resources page (http://go.microsoft.com/fwlink/?linkid=291)
If this service is stopped or disabled, RPC clients that use RpcNs APIs might be unable to locate servers or fail to start. RPC clients that rely on RpcNs APIs from the same computer might not be able to find RPC servers that support a given interface. If this service is stopped or disabled on a domain controller, RPC clients that use the RpcNs APIs and the domain controller might experience interruption of service while trying to locate clients.
RpcNs APIs are not used internally in Windows; you need to start this service only if third-party applications require it.
Available on: Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition and Windows Server 2003, Web Edition.
Installed through: Default operating system installation
Startup type: Manual (Automatic on a domain controller)
Service status: Stopped (Started on a domain controller)
This service depends on the following system components:
The following system components depend on this service: