You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/sql/database-engine/install/windows/error-rpc-server-unavailable-provisioning-account.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ For more information, see [The system can't log you on with the following error:
77
77
78
78
### Eliminate the SQL Server setup process as the issue
79
79
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.
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.
81
81
82
82
#### Step 1: Build the ADLookup application
83
83
@@ -104,9 +104,9 @@ To determine whether the SQL Server setup process itself is the cause of failure
104
104
dotnet new console -n ADLookup
105
105
cd ADLookup
106
106
```
107
-
108
-
> [!NOTE]
109
-
> This step creates a basic console app structure.
107
+
108
+
> [!NOTE]
109
+
> This step creates a basic console app structure.
110
110
111
111
1. Use a text editor to replace the contents of `Program.cs` with the following code:
112
112
@@ -184,8 +184,8 @@ To determine whether the SQL Server setup process itself is the cause of failure
184
184
dotnet build --configuration Release
185
185
```
186
186
187
-
> [!NOTE]
188
-
> 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.
189
189
190
190
#### Step 2: Run the ADLookup application
191
191
@@ -211,15 +211,15 @@ To determine whether the SQL Server setup process itself is the cause of failure
211
211
Press any key to quit
212
212
```
213
213
214
-
1. Look up the account name that has the **user** parameter:
214
+
1. Look up the account name using the the **user** parameter:
215
215
216
216
```bash
217
217
adlookup CONTOSO/SQLSvcAcct user
218
218
```
219
219
220
220
You must use a forward slash, not a backslash, to separate the domain and account name.
221
221
222
-
For a service account that's experiencing issues, the output should resemble the following example:
222
+
For a service account that's experiencing RPC server issues, the output should resemble the following example:
0 commit comments