This is a weird one. I went into users computer and tried to log in as different user (Shift + Right click) and I was able to run the report as me in AX. When I had her put her credentials, it does not recognize her login. She is able to log into AX client and log into AX if she clicks on the “PROD” arc link, but not when she explicitly logs in as a different user (as her). She is able to ping and log into SSRS report server. Has anyone seen this before? I cleared her .auc files once already, but did not clear usage data yet. She has also tried completely logging out of AX and client.
Any help would be appreciated.
*This post is locked for comments
Resetting the windows password had solved this issue.
The problem was fixed by having the user reset her network password again. Weird!
Hi,
Please have a look at the following link which has series of troubleshooting steps.
daxdude.blogspot.com/.../ax-ssrs-error-request-failed-with-http.html
(AX SSRS Error: The request failed with HTTP status 401: Unauthorized.)
Also if the user password has been updated recently, try to log off and log back into the server.
Thanks,
Chaitanya Golla
She is getting the error trying to run any SSRS reports in AX.
yes the user access to the report and was able to run the reports in the past.
Your explanation is somewhat unclear. Can you confirm if the user was ever able to run reports and it just stopped working, or if they were never able to use reporting before at all?
You might be missing the setting on the reporting server folder for the user accounts. Typically you should have added "yourdomain\Domain Users" to make reporting generally available to all user accounts for which you have given permission for within AX through security roles:
technet.microsoft.com/.../hh271484.aspx
If that is not the problem, I can see you are talking about shortcuts and using run as.
Please note that AX is storing the configuration files for connectivity within the registry, unless you export it as an AXC file from the configuration tool. If that is the case, you need to put the AXC files' location within the AX executable's shortcut to always connect to the correct AX AOS instance, no matter what the default registry entry is for a user on the PC. Maybe you are missing that, and that is why you get different results.
If the above points are not helping, please explain your situation better.
André Arnaud de Cal...
292,031
Super User 2025 Season 1
Martin Dráb
230,868
Most Valuable Professional
nmaenpaa
101,156