Skip to content

Commit 9c97a56

Browse files
committed
minor cleanup
1 parent e52bd4a commit 9c97a56

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ For more information, see [The system can't log you on with the following error:
7777

7878
### Eliminate the SQL Server setup process as the issue
7979

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.
8181

8282
#### Step 1: Build the ADLookup application
8383

@@ -104,9 +104,9 @@ To determine whether the SQL Server setup process itself is the cause of failure
104104
dotnet new console -n ADLookup
105105
cd ADLookup
106106
```
107-
108-
> [!NOTE]
109-
> This step creates a basic console app structure.
107+
108+
> [!NOTE]
109+
> This step creates a basic console app structure.
110110
111111
1. Use a text editor to replace the contents of `Program.cs` with the following code:
112112

@@ -184,8 +184,8 @@ To determine whether the SQL Server setup process itself is the cause of failure
184184
dotnet build --configuration Release
185185
```
186186

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.
189189
190190
#### Step 2: Run the ADLookup application
191191

@@ -211,15 +211,15 @@ To determine whether the SQL Server setup process itself is the cause of failure
211211
Press any key to quit
212212
```
213213

214-
1. Look up the account name that has the **user** parameter:
214+
1. Look up the account name using the the **user** parameter:
215215

216216
```bash
217217
adlookup CONTOSO/SQLSvcAcct user
218218
```
219219

220220
You must use a forward slash, not a backslash, to separate the domain and account name.
221221

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:
223223
224224
```output
225225
Checking CONTOSO/SQLSvcAcct for type user

0 commit comments

Comments
 (0)