Skip to main content
Skip table of contents

Error: "Your login has not been given permission to use this application"

This support note applies to:

  • AE Practice Manager (AU)
  • AE Tax Series 6 & 8 (AU)
  • AE Accounts (AU)
Article ID: 28660

In MYOB Accountants Enterprise (AE) you may experience the error "Your login '<username>' has not been given permission to use this application" when launching the following applications from the Applications section of the Tasks Bar for databases with Compliance Integration:

  • Client Compliance;
  • AE Tax;
  • BAS; or
  • AE Accounts.

The error message occurs when your login for AE Practice Manager does not match your Windows login.

To be able to launch applications successfully from the Tasks panel, edit the user name for the employee to match their Windows login.

To edit an Employee's Username

In AE Practice Manager perform the following:

  1. Open the employee and click the Main tab. The employee details apppear.
  2. Type the Windows login into the U/Name field and click OK. The employees windows login will now be used when logging into AE Practice Manager.

    Ensure the employee exits AE PM and logs back in with their new User Name. This allows them to launch applications from within AE Practice Manager.


Internal Notes:

On CI sites, the old contacts main database 000000.pms is still used for centrally holding client information which is used to launch the compliance applications - AE Tax, AE Accounts, Corporate Compliance etc.

This means that it still utilizes the same technology that was used when the site was a Contacts only site before moving to AE Practice Manager, which means users attempting to access compliance applications need to be aligned with the network login. Contacts aligns the employee/user with the network login, so when you open contacts it automatically starts up without having to login.

The integrated AE Practice Manager/CI setup gets around this by aligning the Username field as per above. So the Username field has to match the network login of the user experiencing the error.
Note: If correcting the username does not rectify the issue review the 000000.pms file for duplicate or incorrect records. 

In these instances, Use DBed to edit the Employee table from Datasafe > Support tools > Other Utilities area. It would be advisable to dial in to the site to perform the details below.
To Dbed, edit and upload the edited the 000000.pms > Employees table:

1. Access Datasafe and run a regular backup.

2. From AE Practice Manager, take a note of the employee name, code, and also confirm the network login details for the affected employee.
Note: The network login details can be found by asking the user to CTRL+ALT+DEL on the workstation. This displays the details of the employee currently logged into the workstation.

3. Once the backup has completed successfully, from Datasafe, click the Support Tools button.
The Database Utilities window opens.

4. In the Other Utilities area, select the following and click Run Now:
Utility: DBED - Edit Database
Database: Profiles (PMS)
Client: No Client - Practice File
Copy: Home
Arguments: -t~
The Black DBED DOS window will appear.

5. Type s employee > C:\employees.txt and press ENTER.
The employee.txt file is created.

6. Open Windows Explorer or Computer and navigate to location specified in the command. Create a copy of the file exported file, for example employees1.txt as a backup copy, so the original contents of the table can be restored if required.

7. Open the original employees.txt file in Notepad, and from the Edit menu, select Find, and search for the affected employee name. Use the Direction Up/Down options to navigate to find items that match your search text. Check there is not more than one record for the employee you are searching for.
Each row listed in the file is an employee record, and the tilde symbol (~) separates each field in the record.
The format is as follows for each record:
Employee id~Employee Code~Employee Name~flags~User Login Code~Title~Surname~Given Names~etc..
Note: The full details of the table can be found in the XLON Support Manual, but the information above is enough for the purpose of fixing this issue.

8. The 2 fields that will cause the error will be the Employee Code and/or User Login Code fields. These must match the User Code and Username/Network Login in AE Practice Manager for the affected user.
If there are blanks in either of these fields, or the code or login is incorrect, you will need to edit the text file to the correct details.
There should only be ONE listing of the affected employee in the employees table. Duplicate records of an employee with blank or incorrect Employee Codes or User Login Codes need to be deleted from the file.
If a record is deleted, then you need to remove the blank line from the file where that record was.

Note: If you delete records, make sure you only delete the one record (line) affected. Partially missing information can cause corruptions in the database.

9. Once the Employee Code and User Login Code details are correct, and there are no duplicate employee records, and there are no blank lines in the file, save your changes.

10. Type s employee and press ENTER.
This should display the current contents of the employee table in the DOS screen.

11. Type d employee and press ENTER.
This deletes the contents of the current employee table.
Note: you have to delete the contents of this table first. Simply updating the table does not work.
To test this has worked, repeat the command:
s employee and enter.
You should get a blank line come up at a new curly bracket with the cursor flashing. This means the contents of the table are blank.

12. Type u employee <c:\employees.txt and press ENTER.
This uploads the contents of the modified employees.txt file into the 000000.pms > employees table.

13. Type s employee and press ENTER, to confirm that the contents of the employee table have been updated.

14. Have the affected user test the process.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.