Skip to content

Commit be906a7

Browse files
authored
Update error-rpc-server-unavailable-provisioning-account.md
Edit review per CI 7317
1 parent b58e67f commit be906a7

1 file changed

Lines changed: 35 additions & 34 deletions

File tree

support/sql/database-engine/install/windows/error-rpc-server-unavailable-provisioning-account.md

Lines changed: 35 additions & 34 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
11
---
2-
title: SQL Server Setup Fails With "The RPC server is unavailable" When Provisioning Service Accounts
3-
description: This article provides troubleshooting guidance for "The RPC server is unavailable" errors when provisioning service accounts during SQL Server setup.
2+
title: SQL Server Setup Fails With The RPC server is unavailable When Provisioning Service Accounts
3+
description: This article provides troubleshooting guidance for the "RPC server is unavailable" error when provisioning service accounts during SQL Server Setup.
44
ms.date: 08/26/2025
55
ms.custom: sap:Installation, Patching, Upgrade, Uninstall
66
ms.author: jopilov
77
ms.topic: troubleshooting-problem-resolution
88

9-
#customer intent: As a developer or IT administrator, I want to resolve "The RPC server is unavailable" errors during SQL setup so that I can successfully setup SQL Server.
9+
#customer intent: As a developer or IT administrator, I want to resolve the "RPC server is unavailable" error so that I can successfully set up SQL Server.
1010
---
1111

12-
# "The RPC server is unavailable" error when provisioning service accounts during SQL Server setup
12+
# "RPC server is unavailable" error when provisioning service accounts during SQL Server Setup
1313

14-
This article helps you troubleshoot "The RPC server is unavailable" errors when setting up SQL Server instances. This error can occur during the service account provisioning phase of the SQL Server setup.
14+
This article helps you troubleshoot an "RPC server is unavailable" error when you set up Microsoft SQL Server instances. This error can occur during the service account provisioning phase of SQL Server Setup.
1515

1616
## Symptoms
1717

18-
During the service account provisioning phase of the SQL Server install, installation fails with the error: `The RPC Server is unavailable`.
18+
During the service account provisioning phase of a SQL Server installation, the installation fails and generates an "RPC Server is unavailable" error message.
1919

20-
The following log shows an example of a failure during service account provisioning. In this example, the service account being provisioned is a domain account with the name `CONTOSO\SQLSvcAcct`:
20+
The following example log entry shows a failure that occurs during a service account provisioning. In this example, the service account is a domain account that's named `CONTOSO\SQLSvcAcct`.
2121

2222
```output
2323
(05) 2024-01-19 15:00:42 Slp: Sco.User.LookupADEntry - Attempting to find user account CONTOSO\SQLSvcAcct
@@ -48,9 +48,9 @@ The following log shows an example of a failure during service account provision
4848
(05) 2024-01-19 15:01:03 Slp: ----------------------------------------
4949
```
5050

51-
The log shows that the [System.DirectoryServices.DirectoryEntries.Find()](/dotnet/api/system.directoryservices.directoryentries.find) method is failing with the error: `The RPC server is unavailable`.
51+
This log entry shows that the [System.DirectoryServices.DirectoryEntries.Find()](/dotnet/api/system.directoryservices.directoryentries.find) method fails and returns the error message, `The RPC server is unavailable`.
5252

53-
You can look up the HResult error `0x800706ba` using the `certutil.exe` command line tool:
53+
You can look up the HResult error, `0x800706ba`, by using the `Certutil.exe` command line tool:
5454

5555
```cmd
5656
certutil /error 0x800706ba
@@ -66,30 +66,30 @@ CertUtil: -error command completed successfully.
6666

6767
## Cause
6868

69-
An underlying Windows issue is typically the cause of this error, such as:
69+
The cause of this error is typically an underlying Windows issue, such as:
7070

71-
- The "Remote Registry" service isn't running.
72-
- Incorrect DNS settings.
73-
- Incorrect Time and Time zone settings.
74-
- The "TCP/IP NetBIOS Helper" service isn't running.
71+
- The Remote Registry service isn't running.
72+
- DNS settings are incorrect.
73+
- Time and Time zone settings are incorrect.
74+
- The TCP/IP NetBIOS Helper service isn't running.
7575

7676
For more information, see [The system can't log you on with the following error: The RPC server is unavailable](~/windows-server/user-profiles-and-logon/not-log-on-error-rpc-server-unavailable.md#cause).
7777

78-
### Verify the SQL Server setup process isn't the issue
78+
### Eliminate the SQL Server setup process as the issue
7979

80-
Using the following steps, you can build and run a test application to reproduce the `The RPC Server is unavailable` error and verify that the SQL Server setup process isn't the cause of failure:
80+
To determine whether the SQL Server setup process itself is the cause of failure, use the following steps to build and run a test application that reproduces the `RPC Server is unavailable` error.
8181

82-
#### Build the ADLookup application
82+
#### Step 1: Build the ADLookup application
8383

84-
1. Open a Command Prompt or PowerShell terminal.
84+
1. Open a Command Prompt window or a PowerShell terminal.
8585

86-
1. Ensure the [.NET SDK](https://dotnet.microsoft.com/en-us/download) is installed on your machine:
86+
1. Make sure that the [.NET SDK](https://dotnet.microsoft.com/en-us/download) is installed on your computer:
8787

8888
```bash
8989
dotnet --version
9090
```
9191

92-
If the .NET SDK is correctly installed, this command should output the SDK's version number.
92+
If the .NET SDK is installed correctly, this command should output the SDK's version number.
9393

9494
1. Create a project folder:
9595

@@ -104,10 +104,11 @@ Using the following steps, you can build and run a test application to reproduce
104104
dotnet new console -n ADLookup
105105
cd ADLookup
106106
```
107+
108+
> [!NOTE]
109+
> This step creates a basic console app structure.
107110
108-
This step creates a basic console app structure.
109-
110-
1. Using a text editor, replace the contents of `Program.cs` with:
111+
1. Use a text editor to replace the contents of `Program.cs` with the following code:
111112

112113
```csharp
113114
using System;
@@ -183,23 +184,24 @@ Using the following steps, you can build and run a test application to reproduce
183184
dotnet build --configuration Release
184185
```
185186

186-
This step compiles the code and generates an `ADLookup.exe` in the `bin\Release\net<VersionNumber>\` folder.
187+
> [!NOTE]
188+
> This step compiles the code and generates an `ADLookup.exe` in the `bin\Release\net<VersionNumber>\` folder.
187189
188-
#### Run the ADLookup application
190+
#### Step 2: Run the ADLookup application
189191

190-
1. Navigate to the directory where the executable is built:
192+
1. Navigate to the directory in which the executable is built:
191193

192194
```bash
193195
cd bin\Release\net<VersionNumber>\
194196
```
195197

196-
1. Run `ADLookup.exe` with the **domain** parameter to look up the domain name first:
198+
1. Run `ADLookup.exe` by using the **domain** parameter to look up the domain name first:
197199

198200
```bash
199201
adlookup CONTOSO domain
200202
```
201203

202-
The output should be similar to the following example:
204+
The output should resemble the following example:
203205

204206
```output
205207
Checking CONTOSO for type domain
@@ -209,16 +211,15 @@ Using the following steps, you can build and run a test application to reproduce
209211
Press any key to quit
210212
```
211213

212-
1. Look up the account name with the **user** parameter:
214+
1. Look up the account name that has the **user** parameter:
213215

214216
```bash
215217
adlookup CONTOSO/SQLSvcAcct user
216218
```
217219

218-
> [!NOTE]
219-
> You must use a forward slash to separate the domain and account name, not a backslash.
220+
You must use a forward slash, not a backslash, to separate the domain and account name.
220221

221-
For a service account experiencing issues, the output should be similar to the following example:
222+
For a service account that's experiencing issues, the output should resemble the following example:
222223
223224
```output
224225
Checking CONTOSO/SQLSvcAcct for type user
@@ -228,6 +229,6 @@ Using the following steps, you can build and run a test application to reproduce
228229
Press any key to quit
229230
```
230231
231-
## Solution
232+
## More information
232233
233-
To troubleshoot underlying Windows issues causing the SQL Server setup to fail, see [The system can't log you on with the following error: The RPC server is unavailable](~/windows-server/user-profiles-and-logon/not-log-on-error-rpc-server-unavailable.md#resolution).
234+
To troubleshoot underlying Windows issues that cause SQL Server Setup to fail, see [The system can't log you on with the following error: The RPC server is unavailable](~/windows-server/user-profiles-and-logon/not-log-on-error-rpc-server-unavailable.md#resolution).

0 commit comments

Comments
 (0)