Microsoft SQL Server 2022 - Audit Logs not working

Waleed Dilawar Chughtai 0 Reputation points
2024-08-07T11:11:04.8466667+00:00

Hello,

I am trying to enable SQL Server Audit logs which is a fairly standard process and have got it working on our other database servers except this one, we are running Microsoft SQL Server 2022 with version 18 on it so the latest update, and have both the audit specification and audit log enabled with appropriate specifications. The error received is as follows:


Item has already been added. Key in dictionary: 'MNDO' Key being added: 'MNDO'


This is shown when attempting to view audit logs using the Log File View within SSMS.

Any advice / guidance requested please.

Many Thanks.

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
3,061 questions
SQL Server Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. MikeyQiaoMSFT-0444 3,300 Reputation points
    2024-08-08T03:16:05.9733333+00:00

    Hi,Waleed Dilawar Chughtai

    Here are a few suggestions you can try:

    1. Update SQL Server to the latest version.

    https://www.microsoft.com/en-us/download/details.aspx?id=105013

    1. Update SSMS to the latest version.

    https://aka.ms/ssmsfullsetup

    1. Ensure that there are no log files from other instances in the audit folder.
    2. Additionally, you can use sys.fn_get_audit_file to view the audit logs.

    Best Regards,

    Mikey Qiao


    If you're satisfied with the answer, don't forget to "Accept it," as this will help others who have similar questions to yours.


  2. Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator
    2024-08-08T21:28:07.18+00:00

    It seems that you are hitting a bug in SSMS that is related to the action id MNDO. If you run sys.fn_get_audit_file, you can probably find such events. I find that MNDO corresponds to DATABASE_OBJECT_CHANGE_GROUP.

    If you find this to be a blocking issue for you, I would recommend you to open a support case. For Microsoft to be able to address this bug, they need a reproducible scenario, and a support case would be a good way to convey this information to Microsoft.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.