You’re offline. This is a read only version of the page.
We're having an issue where reportviewer controls in the Dynamics client do not populate. Reviewing logs, an attempt to contact our SSRS server doesn't even occur. Reviewing Wireshark, it shows the Dynamics client makes a "DCE/RPC" call to our SSRS server, which returns an access denied packet (I only know this thanks to Wireshark's decoding function). No attempt to contact the SSRS service (HTTP or HTTPS) is ever attempted.
Interestingly enough, if the user happens to be a local admin on the SSRS server (few of us IT guys), the report will appear and the Wireshark packets show DCE/RPC protocol success (followed by HTTP traffic to the SSRS report website).
All permissions in Dynamics and SSRS are setup correctly. The issue, as seen by Wireshark, lies with the local OS on the SSRS server denying non-admins access to something I'm unaware of, which occurs between the Dynamics AX client and SSRS server operating system (DCOM? COM+? MSRPC?) which I cannot find in documentation. The failure in this step makes the client never attempt to reach the SSRS server, thus no report is shown in the client. For example, if you go to Production Control and Start an order, the ProdReport never appears (the window housing it doesn't appear, either). Users can contact the SSRS server directly via browser and run the reports without an issue, however (not a SSRS permissions issue).
As per Wireshark findings, is anyone familiar with DCERPC/MSRPC and what the Dynamics client is doing with the SSRS server before actually sending the HTTP request to the report website?
Thank you in advance for any assistance helping us solve our headache. In the meantime, I will read more on MSRPC...
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
4
