Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
I'm have been working with AX 2012 for a couple months now.
Last week, I started a fresh AX installation on my company server.
System specification: Windows Server 2008 R2, SQL server 2012, SSRS, AX 2012 R2
There was no error in installation of 1 AOS and 1 SSRS. I could configure and deploy reports to Report Server. I created a new company which named "ABC".
But, on the company "ABC", when I try to run a report (ex: System Administration > Reports > Database > Size of company data), the error message "Failed to logon to Dynamics AX." showed up. I checked the security settings on database, AD etc. and everything seems OK.
The strange thing is, when I changed to "DAT" company, and the same report run successfully. After that, I changed back to "ABC" company then run the report. The error message "The company ABC does not exits." showed up.
Below is the details from Event Viewer.
At the first time when I ran report on "ABC" company:
Object Server 01: An error has occurred in the services framework. Method: AifMessageInspector::AfterReceiveRequest. Error: System.ServiceModel.FaultException: Failed to logon to Microsoft Dynamics AX.
at Microsoft.Dynamics.Ax.Services.AxServiceOperationContext.Attach(OperationContext owner)
at System.ServiceModel.ExtensionCollection`1.InsertItem(Int32 index, IExtension`1 item)
at System.Collections.Generic.SynchronizedCollection`1.Add(T item)
at Microsoft.Dynamics.Ax.Services.AifMessageInspector.AfterReceiveRequest(Message& request, IClientChannel channel, InstanceContext instanceContext)
At the second time:
Object Server 01: An error has occurred in the services framework. Method: AifMessageInspector::AfterReceiveRequest. Error: System.ServiceModel.FaultException: The company ABC does not exist.
at Microsoft.Dynamics.Ax.Services.AifHelper.ValidateCompany(SesPblk_t* blk, String company, String partitionKey)
at Microsoft.Dynamics.Ax.Services.AxSessionInitBehavior.GetUserSessionForCallerImpl(String logonUserSid, String callerIdentitySid, String company, String language, Boolean isILSession, Boolean isRunAs, String partitionKey)
at Microsoft.Dynamics.Ax.Services.AxSessionInitBehavior.GetUserSessionForCaller(String logonUserSid, String callerIdentitySid, String company, String language, Boolean isILSession, Boolean isRunAs, String partitionKey)
at Microsoft.Dynamics.Ax.Services.AxSessionInitBehavior.GetUserSessionForCaller(String logonUserSid, String callerIdentitySid, String company, String language, Boolean isILSession, String partitionKey)
At 1st time, it seems like the system was stuck at InitializeSession. At the 2nd time, somehow the system passed InitializeSession but was stuck at ValidateCompany.
So far, I have been struggling with this error for over a week. I have tried many work around like delete .auc files / refresh WCF / Register services..., that I found on the Internet but no luck. I even tried installing AOS + SSRS again, applied a hotfix from MS, but the error keeps showing up. It is very frustrated.
If you guys saw an error like this before, and know a work around for this, please show me. Thanks in advance.
Please verify that the Data Source is using Windows Integrated Authentication.
@Tommy Skaue: Thank you for your help.
I checked the Data Source, and it is using Window intergrated security. The error showed up when I tried running any report on "ABC" company. On "DAT" company, all reports run OK. Currently, I'm trying to re-install SSRS again...
I'm havings same problem. How did you finally fix your problem?
Has the same error a few weeks ago. In my scenario the business connector was connected to the wrong instance of ax. Corrected the ax config and everything worked fine.
At the beginning, I tried to install 2 SSRS for 2 AOS as instructed in the below article:
After installation, I ran the report and the error showed up.
So, I uninstalled 2 AOS + 2 SSRS, then tried re-installing 1 AOS + 1 SSRS many times but the error persisted. But, after the re-installation of SQL server + 1 SSRS + 1 AOS, it's OK.
So, I think, at last time, somehow I messed up the settings and it affected SQL server settings (!?)
By the way, while fixing the problem, I also asked for support from MS partner network. Although they couldn't reproduce the error at their lab, they provided me some ways to confirm the error:
1. What's the version of your SSRS? 2012 or 2008R2 or any others?
2. Are your BC proxy account, SSRS service account, SSRS execution account and AOS account the same? Please have a try to make them a same account to see if it helps.
3. Check what can be found in the SSRS logs:msdn.microsoft.com/.../ms157403.aspx and msdn.microsoft.com/.../ms157403(v=sql.105).aspx.
Sorry for the late update, currently I'm kind of busy.
Hope this help. And, thanks for your answers and suggestions.