I an trying to deploy reports from AOT (Dynamics AX 2012 Pre Release). The follwoing two errors challenging me. any help would be great.
1. An error occurred : The specified directory service attribute or value does not exist.
If User Account Control (UAC) is enabled on the machine, close the application, right-click the application, and then click Run as administrator.
I Have already disabled UAC and even run the AX as administrator mode. Nothing works.
-------------------------
2. The deployment was aborted. You do not have privileges to deploy to server: bwircadbridge. For deployment, you must have administrative rights to the SQL Server Reporting Services (SSRS) server. Contact your administrator to deploy.
I have checked the domain account; and it is already having admin group. but nothing works.
Any help would be great.
*This post is locked for comments
On SSRS Server, Go to Computer Managemant > Local Users and Group > Group > Administrator > Properties and add username here.
It works for me....
Hi Girard, Thanks a lot, your answer was precise and worked perfectly immediately.
After giving appropriate permissions and starting "RemoteRegistry" service, issue has been resolved.
Thanks.
Thanks Girard.
Remote Registry worked for me also
Dear all,
Recently I used one more solution for this issue and it is going for me.
Issue:
When I open the ax client run as administrator everything is fine.
But in my case, the developers are trying to open the AX client with CUS layer configurations (using newly created AXC file) getting the error.If they tried to open the newly created config file run as administrator, AX is opening in USR layer.
Solution: I have copied the newly created AXC file path location and pasted in a client shortcut and applied.
Now when I open the AX client shortcut file run as administrator, the ax is opening in CUS layer and able to deploy the reports as well without any errors.
How to modify the AXCLIENT shortcut file?
Select AX client shortcut file --> Right and properties --> click on the target (Add the newly created AXC file path after giving one space and apply.
Regards ,
Ravi Theja Madisetty
Dear FRANCISCO SILVA ,
Your solution worked for me. I am so exited to know around the route cause of the issue. If possible explain the same.
Regards
Ravi Theja Madisetty
Hi. thanks for this suggestion. This is exactly what I wish to implement (ie. by NOT giving developers local Admin perms on the SSRS server), but please can you explain more detail about what you mean by #2read access on the domain root" and where this needs to be applied?
I got the dev to try deploying report from axutil with the -SkipReportServerAdminCheck switch as per your link, but he still gets access denied error, so this is my last hope
Thanks
Darren
thanks for solution
After a lot of digging I finally found the answer to this. If you're using an updated version that adds the "-SkipReportServerAdminCheck" (as described by fsilva-jr above) parameter and that works but deploying from the AOT doesn't, your problem is probably that described here:
I contacted our AD Administrator and he was able to deploy from the AOT in a test environment. So, we knew it was a permissions thing as described in the link. Turns out AX wanted authenticated users to have read access on the domain root. See attached image. Once these permissions were checked for 'Everyone' I was able to deploy again.
Try to execute the command as following:
"Publish - AXReport -ReportName * -SkipReportServerAdminCheck"
Remember to change the report name as necessary!
Mohamed Amine Mahmoudi
100
Super User 2025 Season 1
Community Member
48
Zain Mehmood
6
Moderator