minor changes

Author: lucciz01

support/dynamics/gp/error-message-start-microsoft-dynamics-gp.md

@@ -1,12 +1,12 @@
 ---
-title: Error message when you start Microsoft Dynamics GP
+title: Your attempt to log into the server failed because of an unknown error
 description: This article provides a resolution for the problem that occurs when you start Microsoft Dynamics GP.
 ms.reviewer: theley, kyouells
 ms.topic: troubleshooting
-ms.date: 04/15/2025
+ms.date: 04/17/2025
 ms.custom: sap:System and Security Setup, Installation, Upgrade, and Migrations
 ---
-# Error message when you start Microsoft Dynamics GP (Your attempt to log into the server failed because of an unknown error. Attempt to log in again.)
+# "Your attempt to log into the server failed because of an unknown error" when you start Microsoft Dynamics GP
 
 This article helps you resolve the problem that occurs when you start Microsoft Dynamics GP.
 
@@ -21,46 +21,39 @@ When you start Microsoft Dynamics GP, you receive the following error message:
 
 ## Cause
 
-This problem occurs when the `DEX_LOCK` and `DEX_SESSION` tables do not exist in the database TEMPDB Database in the SQL Server that is being used for Microsoft Dynamics GP.
+This problem occurs when the `DEX_LOCK` and `DEX_SESSION` tables don't exist in the `TEMPDB` database in the SQL Server that's being used for Microsoft Dynamics GP.
 
-## Resolution
+## Resolution 1
 
-- Method 1
+Restart the instance for SQL Server that's being used with Microsoft Dynamics GP. To do this, follow these steps:
 
-  Restart the instance for SQL Server that is being used with Microsoft Dynamics GP. To do this, follow these steps depending on the SQL Server version you are using.
+1. Select **Start**, point to **All Programs** > **Microsoft SQL Server**, and then select **SQL Server Management Studio**.
 
-    - Microsoft SQL Server 
+2. In the **Connect to Server** window, follow these steps:
 
-    1. Click **Start**, point to **All Programs**, point to **Microsoft SQL Server**, and then click **SQL Server Management Studio**.
+    1. In the **Server name** box, type the name of the server that is running SQL Server.
+    2. In the **Authentication** box, select **SQL Authentication**.
+    3. In the **login** box, type _sa_.
+    4. In the **Password** box, type the password for the sa user, and then select **Connect**.
 
-    2. In the **Connect to Server** window, follow these steps:
+3. Right-click the instance name of the SQL Server, and then select **Restart**.
 
-       1. In the **Server name** box, type the name of the server that is running SQL Server.
+## Resolution 2
 
-       2. In the **Authentication** box, click **SQL Authentication**.
+Start Microsoft Dynamics GP or Microsoft Dynamics GP Utilities as the sa user. To do this, follow these steps:
 
-       3. In the **login** box, type sa .
+1. On a computer that's running Microsoft Dynamics GP, point to **All Programs** > **Microsoft Dynamics**, and then select **GP** or **Utilities**.
 
-       4. In the Password box, type the password for the sa user, and then click **Connect**.
+2. In the login box, type _sa_.
 
-    3. Right-click the instance name of the SQL Server, and then click **Restart**.
+3. In the **Password** box, type the password for the sa user, and then select **OK**.
 
-- Method 2
+## Resolution 3
 
-  To resolve this issue, start Microsoft Dynamics GP or Microsoft Dynamics GP Utilities as the sa user. To do this, follow these steps:
+Re-create the tables by using the **dex_req.sql** script. To do this, follow these steps:
 
-  1. On a computer that is running Microsoft Dynamics GP, point to **All Programs**, point to **Microsoft Dynamics**, and then click **GP** OR click **Utilities**.
+1. Locate the **dex_req.sql** file in the installation folder.
 
-  2. In the login box, type *sa*.
+   - If you're running Microsoft Dynamics GP, the default location is **C:\Program Files\Microsoft Dynamics\GP\SQL\Utililty\0**.
 
-  3. In the **Password** box, type the password for the sa user, and then click **OK**.
-
-- Method 3
-
-  To resolve this issue, re-create the tables by using the dex_req.sql script. To do this, follow these steps:
-
-  1. Locate the dex_req.sql file that is located in the installation folder.
-
-     - If you are running Microsoft Dynamics GP, the default location is `C:\Program Files\Microsoft Dynamics\GP\SQL\Utililty\0`.
-
-  2. Open the dex_req.sql file in SQL Server Management Studio, and then click **Execute** to run the script.
+2. Open the **dex_req.sql** file in SQL Server Management Studio, and then select **Execute** to run the script.