Источник:
http://blogs.msdn.com/emeadaxsupport...-web-part.aspx
==============
When you are setting up Dynamics AX 2009 Role Center and Enterprise Portal in a
multi server environment where each component is running on
Windows Server 2008 you can get confronted with an authentication issue.
The base requirement for a multi server scenario to work is to use
Kerberos authentication and configuring
Service Principle Names (SPNs) for the Service Accounts in use (like the
Business Connector Proxy Account) otherwise the whole scenario will not work at all.
However even if Kerberos and SPNs are configured correctly you can run into an
authentication issue, if you have the following components running on their own server with
Windows Server 2008 as operating system:
- Microsoft SQL Server (including Database Engine, Reporting Services and Analysis Services)
- Microsoft Office SharePoint Server (or Microsoft Windows SharePoint Services)
- Microsoft Dynamics AX Application Object Server (AOS)
When users are browsing at Role Center or Enterprise Portal pages they will get errors for the KPI web parts, but Reporting Services reports are shown also those reports that are based on Analysis Services data. The fact that only KPI web parts are affected makes this issue special from regular Kerberos authentication issues, as here also Analysis Services reports would be affected.
Although the KPI web part and the Reporting Services reports (based on Analysis Services data) are accessing the same Analysis Server Database,
the way how the Analysis Services are accessed is different:
KPI web part: SharePoint Analysis Services
Reporting Services web part: SharePoint Reporting Services Analysis Services
Microsoft SQL Server Analysis Services has an issue when running on an
"Advanced Encryption Standard (AES)" aware operation system (like Windows Server 2008) and using
Kerberos for authentication. If the Microsoft SQL Server Reporting Services and Microsoft SQL Server Analysis Services would be installed on different servers (with Windows Server 2008 as operating system) Microsoft SQL Server Reporting Services would also run into similar issues!
The following BLOG post is discussing this in greater detail and shows also workarounds how to get the scenario to work:
Источник:
http://blogs.msdn.com/emeadaxsupport...-web-part.aspx