Bendrinti naudojant

Event Viewer write access error for Management Reporter Dynamics AX 2009

  • Straipsnis

This article provides a resolution on how to solve the write access error for Management Reporter Dynamics AX 2009.

Applies to:   Microsoft Management Reporter 2012, Microsoft Dynamics AX 2009, Microsoft Dynamics AX 2009 Service Pack 1
Original KB number:   3077632

Symptoms

In Event Viewer on Management Reporter server:

System.ComponentModel.Win32Exception (0x80004005): Access is denied

Microsoft.Dynamics.Performance.DataProvider.Core.RequestException: The source system request did not complete successfully. ---> System.InvalidOperationException: Cannot open log for source 'Management Reporter 2012 Services'. You may not have write access. ---> System.ComponentModel.Win32Exception: Access is denied

In Report Designer report queue:

The source system provider was unable to complete the request.

An internal error occurred in the provider. Additional information is available in the event viewer on the Management Reporter server X. Please contact your administrator.

Cause

Management Reporter (Windows) users will need Write access to the Application Event Log on the Management Reporter server when certain warnings/errors are encountered during report generation.

Resolution

Grant Write access to Application Event log on Management Reporter server for the Authenticated Users group:

  1. On the Management Reporter Server, open a command prompt as Administrator.

  2. Run this command to get the details on the access currently granted to the Application Event log:

    C:\>wevtutil gl application

    Note

    The line that shows the access is channelAccess.

  3. Run this command to grant read/write Application Event log access to the Authenticated Users (AU) group:

    C:\>wevtutil sl Application /ca:O:BAG:SYD:(A;;0xf0007;;;SY)(A;;0x7;;;BA)(A;;0x7;;;SO)(A;;0x3;;;IU)(A;;0x3;;;SU)(A;;0x3;;;S-1-5-3)(A;;0x3;;;S-1-5-33)(A;;0x1;;;S-1-5-32-573)(A;;0x3;;;AU)

Note

You can rerun the command from step 2 to confirm the permissions were applied. You should see (A;;0x3;;;AU) now at the end of channelAccess.