Always use the dedicated tools for SQL Server when making modifications on service accounts. This means using the SQL Server Configuration Manager for mostly all SQL Server related services, but perhaps specifically use the SQL Server Reporting Services Manager for modifications related to SSRS in particular. It is not advisable to use the regular Windows Services, as there may be additional steps covered when using the dedicated SQL Server tools which are NOT covered when using plain Windows Services. I don’t have any details, but it is a recommendation, just to be safe you don’t accidentally miss out when not using the tools.
The SSRS Service itself should run under the same account as the Dynamics AX Business Connector. This is part of the installation specification for Dynamics AX. I don’t know how you’ve set this up, but it sounds like you run everything under the same user account (AXadmin?), but just making sure you know it is vitally important the SSRS Service that hosts the AX Reports run under the Business Connector Account.
I have previously blogged about the setup of SSRS for multiple instances here:
The Technical person who installed used axadmin user for everything.
I deleted the dynamicsax report folder and redeployed the reports. It worked fine in the server.
But from client pc when I run the report it shows the following error :
Assembly containing type Microsoft.Dynamics.AX.Frameworks.Controls.ReportViewer.ReportAdapterFactory is not referenced.
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
Did you encountered this before .
The URL you shared, i think article has been moved.
This link opens. Thanks. Can u share your experience reg. my updated msg. the error msg. from client pcs. But in server its working. Will try to test Mr. srikanth solution