Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you start Microsoft Dynamics GP: "Your login has been removed from the user activity file and you cannot be in the accounting system"


View products that this article applies to.

Symptoms

When you start Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 9.0, you receive the following error message:

Your login has been removed from the user activity file and you cannot be in the accounting system.

↑ Back to the top


Cause

This problem occurs when an automatic client update is published. Additionally, the path of the Microsoft Windows Installer file (.msp file) is incorrect, or the .msp file is missing.

↑ Back to the top


Resolution

To resolve this problem, use one of the following methods.

Method 1

If the client update is already installed on all clients, delete the client update that is published. To do this, follow these steps:
  1. Log on to Microsoft Dynamics GP by using a system administrator (sa) user account.
  2. Use the appropriate step:
    • In Microsoft Dynamics GP, point to Tools on the Microsoft Dynamics GP menu, point to Setup, point to System, and then click Client Updates.
    • In Microsoft Dynamics GP 9.0, point to Setup on the Tools menu, point to System, and then click Client Updates.
  3. In the Manage Automated Client Updates window, click the icon next to the Update Name box.
  4. In the Updates window, click the update that you installed, and then click Select.
  5. In the Manage Automated Client Updates window, click Delete.

Method 2

If you want to keep the client update, verify that the .msp file exists and that the path of the .msp file is correct. To do this, follow these steps:
  1. Log on to Microsoft Dynamics GP by using an sa user account.
  2. On the Tools menu, point to Setup, point to System, and then click Client Updates.
  3. In the Manage Automated Client Updates window, click the icon next to the Update Name box.
  4. In the Updates window, verify that the path of the .msp file is correct. Correct the path if it is incorrect.
  5. Verify that the .msp file is in the directory at the end of the path.

Method 3

If no user can log on to the system, remove the automatic client update from the automatic client update table in the DYNAMICS database. To do this, follow these steps:
  1. Confirm that you have a backup of the DYNAMICS database.
  2. Open SQL Query Analyzer or SQL Server Management Studio.
  3. To display all automatic client updates, run the following SQL statement.
    select * from DYNAMICS..SYUPDATE
  4. Remove the automatic client update that does not have a valid UNCPath. To do this, run the following script.
    delete DYNAMICS..SYUPDATE where UPDATENAME = 'XXXX'
    Note Replace 'XXXX' with the correct update name.
  5. Log on to Microsoft Dynamics GP.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem is not scheduled to be fixed.

↑ Back to the top


Keywords: kbmbsgp10,, kbfreshness2007, kbentirenet, kbtshoot, kbmbspartner, kberrmsg, kbmbsmigrate, kbbug, kb

↑ Back to the top

Article Info
Article ID : 916679
Revision : 3
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 311