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.

"Installation of analytical accounting has failed as there are other users logged into the system." when attempting to activate Analytical Accounting (AA) in Microsoft Dynamics GP


View products that this article applies to.

SYMPTOM

Customer is getting error when attempting to activate Analytical Accounting(AA).

"Installation of analytical accounting has failed as there are other users logged into the system"

There are other users logged into DYNAMICS, but not that particular Company where you are adding AA. You are wondering if everyone has to be out of Dynamics GP to create default records as well as running the AA Activation Wizard itself. 

↑ Back to the top


CAUSE

Users logged into Dynamics GP while activating Analytical Accounting. 

All users do need to be out of the system (all companies in same Dynamics database) when going through the AA activation process.  This is mainly because Analytical Accounting uses the dynamics table (AAG00102) to populate the next record values in the AAG work, open, and history tables for all of the companies.  When you activate AA, those tables will have default records created so that you can go back and add dimensions (using the AA edit analysis window) to posted journal entries should you need to.  It will also update a flag setting in the dynamics AAG00104 table after the activation is completed.  Since the Dynamics tables are impacted, all users need to be out of all company databases.
 

↑ Back to the top


RESOLUTION

Run these scripts to see if anyone else is in the system and ask them to exit properly through the front-end. If all users are out, these tables should be empty, so provided ‘delete’ scripts below as well.

 

SELECT * FROM DYNAMICS..ACTIVITY

SELECT * FROM DYNAMICS..SY00800

SELECT * FROM DYNAMICS..SY00801

SELECT * FROM TEMPDB..DEX_LOCK

SELECT * FROM TEMPDB..DEX_SESSION

----------------------------------------

DELETE DYNAMICS..ACTIVITY

DELETE DYNAMICS..SY00800

DELETE DYNAMICS..SY00801

DELETE TEMPDB..DEX_LOCK

DELETE TEMPDB..DEX_SESSION

↑ Back to the top


Keywords: kb, kbmbsmigrate, kbmbspartner, kberrmsg

↑ Back to the top

Article Info
Article ID : 4099427
Revision : 2
Created on : 3/23/2018
Published on : 3/23/2018
Exists online : False
Views : 338