We had a new issue here. One of our pre-production AOS needed to be rebuilt. After our first deployment to the new environment, we found that SSRS reports were generating errors. We were getting a pattern of 2 warnings, an error and 2 more warnings.
1) This warning was received twice:
Unable to get version information using existing WCF configuration from local storage.
Exception details:
Microsoft.Dynamics.AX.Framework.Services.Client.MetadataServiceException: Exception occurred on the metadata service on client or server. See exception details below:
2) The error was:
AXRDCE The AXRDCE extension caught an unexpected exception for report MWW_PYGByLocation.pdPYGByLocation.
The error message was:
Exception occurred on the metadata service on client or server. See exception details below:
>Unable to log on to Microsoft Dynamics AX.
at Microsoft.Dynamics.AX.Framework.Services.Client.ServiceClientHelper.InvokeChannelOperation[TResult,TChannel](IServiceClient`1 client, Func`2 operationInvoker, Func`2 exceptionWrapper)
Then the warnings above repeated themselves twice.
Also, when I tried running any report from the SSRS server, I kept getting an error about not being able to set or retrieve the default value for parameter "CompanyName".
After researching the normal list of solutions, such as: restarting the AOS, clean the caches, doing a full CIL compile and refreshing the client side services; I decided to research the issue around the company name. This finally led me to the following Tech Net article: https://technet.microsoft.com/en-us/library/hh389774.aspx.
It turns out that the Business Connector information and authentication methods are not stored in SSRS reports as I had previously thought. Rather, they are held in a designated configuration file (it must be named Microsoft.Dynamics.AX.ReportConfiguration.axc) that must be placed <SSRS Server path>\Reporting Services\ReportServer\bin directory.
After restarting SSRS, everything was working as norma.
