It is recommended that the Application User and Application Administrative User accounts not be changed once they are setup. If an account needs to be changed in any way, whether it is simply renamed or an entirely new account is created, all references to the old account must be manually replaced. References in the following places must be updated:
All Agile Business Suite processes running with the identity of the changed account, as listed in The Application User and The Application Administrative User.
All COM+ roles referring to the changed account.
If the account is recreated, as opposed to renamed, the data files folder needs to have its permissions reset to allow Full Control to the changed account.
If the account name is recreated, as opposed to renamed, the SID of User account needs to be stored in flat files for Application User and Application Administrative User. They are created in the Data\Private directory. For example:
AB Suite 7.0\Data\Private\Security\Users\Application User AB Suite 7.0\Data\Private\Security\Users\Application Administrative User
The SID of the Application User is stored in the Application User file and the SID of the Application Administrative User is stored in the Application Administrative User file.
SQL Server Specific
The SQL Server login used by the Application User needs to be reconfigured to allow access to the changed account with the appropriate permissions.
The SQL Server databases used by Agile Business Suite needs to grant the changed account access as a user of the database, and if the changed account is for the Application Administrative User, include it in the db_owner role.
The SQL Server users utilized by Agile Business Suite in the databases need to have their passwords changed using the Change Database User Password tool. Refer to Change Database User Password.