Walkthrough: Defining KPIs for a Cube [AX 2012]

Prerequisites

---

To complete this walkthrough, you will need:

• Microsoft Dynamics AX with sample data
• The MyCustomers cube from  Creating Cubes [AX 2012] Post.
• SQL Server Business Intelligence Development Studio (BIDS) or SQL Server Data Tools
• Configure Analysis Services by running the Microsoft Dynamics AX Setup wizard

Defining a KPI for Inventory Quantity

---

To display your KPI in a Business Overview web part on a role center, you must define value, goal, status, and trend expressions for the KPI. If you exclude one of the expressions, the KPI will not display properly.

To create a KPI for Inventory Quantity

1. In BIDS, open the Analysis Services project that contains the Sales analysis cube, and then double-click MyCustomers .cube.
2. Click the KPIs tab.
3. On the toolbar for the KPIs tab, click New KPI. A form displays that allows you to define the KPI.
4. For the Name field, type Customer sales.
5. For the Value Expression field, type the following expression.

[Measures].[Total customer sales Count]

This expression retrieves the quantity in inventory units.

Note

You can drag measures from the Metadata tab of the Calculation Tools pane to help you create expressions.

6. For the Goal Expression field, type the following expression.

7500

This expression identifies the goal for the inventory quantity.

7. For the Status indicator field, select Gauge from the drop-down list.
8. For the Status expression field, type the following expression.

Case
    When
        [Measures].[Total customer sales Count] >= 7500
    Then 1
    When
        [Measures].[Total customer sales Count] < 7500
    AND
        [Measures].[Total customer sales Count] > 6500
    Then 0
    Else-1
End

 

This expression provides a basis to evaluate progress toward meeting the goal. The graphic that displays for status of the KPI depends on what value this expression evaluates to.

9. For the Trend indicator field, select Standard arrow from the drop-down list.
   
10. For the Trend expression field, type the following expression.

Case
    When
        [Measures].[Total customer sales Count] >= 3000
    Then 1
    When
        [Measures].[Total customer sales Count] < 3000
    
    Then -1
End

This expression provides a basis to evaluate the status in some historical context. The graphic that displays for the trend of the KPI depends on what value this expression evaluates to. Typically, the trend expression would evaluate the current status relative to a previous status.

To view the KPI

1. On the Build menu, click Deploy Dynamics AX MyCustomers .

Note: The name of the database may vary.

2. On the toolbar for the KPIs tab, click Browser View. The KPI displays in the list.

Creating Cubes [AX 2012]

This section discusses how to create new cubes and reports by using tools built into Microsoft
Dynamics AX 2012, Figure below shows the four-step process for creating a new cube

Identify requirements

Often, when a user asks for additional information, you get a request for a new report (or two or
three). For example, you might get a requirement request for a report like the one shown in
Figure below from someone in the Sales department.

Microsoft Dynamics AX Demo -- Business Intelligence Video

Microsoft Dynamics AX Demo -- Business Intelligence Features (Part 1 of 3)

Microsoft Dynamics AX Demo -- Business Intelligence Features (Part 2 of 3)

Microsoft Dynamics AX Demo -- Business Intelligence Features (Part 3 of 3)

Build a KPI Dashboard in 5 minutes

 

Integrate Microsoft Dynamics AX analytic components with external data sources

Data warehouses are a popular solution for providing analytic capabilities to users. Until recently, data warehouses were the only reasonable solution for building robust analytic capability. However, as applications become easily interoperable and as technologies such as in-memory databases and OLAP become cost-effective and simpler to use, building a data warehouse is not the only solution to meet analytic requirements.
Table below presents several architecture options for integrating external data with the prebuilt
analytic solution; a data warehouse is just one of the options. The columns represent architecture options, whereas the rows represent the benefits and cost implications of each option.

When most data is in Microsoft Dynamics AX (assuming that Microsoft Dynamics AX is the
predominant  source of data in the organization), you have two options.

The data mash-up option is best suited to an environment where capable users author and publish analyses for the use of others. This option relies on client tools such as Excel PowerPivot. Microsoft Dynamics AX 2012 enables Microsoft Dynamics AX queries to be published to data mash-up tools through OData feeds, or as data exports to Excel.

You can bring external data into Microsoft Dynamics AX either through services (data services consumed by means of inbound ports) or as batch jobs that are executed periodically to import data into tables. With this approach, external data is represented as read-only data within Microsoft Dynamics AX. The benefit to this approach is that external data appears as native Microsoft Dynamics AX data to Microsoft Dynamics AX tools. You can create analytics, reports, and inquiry forms that use the combined data.

A more complex approach involves integrating external data directly into the prebuilt BI solution.
With this option, a BI developer adds another data source to the prebuilt BI solution by using Business Intelligence Development Studio. Additional data tables are brought into the DSV by using the new data connection. It is possible to create dimensions and measures by using the new tables in the DSV.

The traditional ETL-based data warehouse option is suited to scenarios that require complex
transformations or large volumes of data. Although this option is more flexible in terms of capabilities, it is also the most expensive to implement and manage.

You might want to build a data warehouse to implement the following scenarios:

■ Integrate external data sources with Microsoft Dynamics AX data In this approach, the Microsoft Dynamics AX implementation serves as one of many corporate applications.
Although Microsoft Dynamics AX contains some of the corporate data, other systems contain
a considerable portion of the data. To make decisions, data must be combined across systems, and the data warehouse serves that need.
■ Incorporate legacy data into Microsoft Dynamics AX analytics Most organizations
migrate recent data when implementing Microsoft Dynamics AX. Legacy data is still
maintained in read-only instances of legacy applications. Although legacy data is no longer
used for operational purposes, it is required for historical trend analysis. A data warehouse
serves as the repository where legacy data is combined with current data.

Although Microsoft Dynamics AX 2012 does not directly support the creation of a data warehouse schema, the following artifacts generated in Microsoft Dynamics AX 2012 can be used to build a data warehouse:

■ The DSV generated as part of the prebuilt analytic solution can be used within SQL Server
Integration Services when an ETL package is developed to extract data from Microsoft
Dynamics AX.
■ Microsoft Dynamics AX document services can be consumed as data sources based on Simple Object Access Protocol (SOAP).
■ Microsoft Dynamics AX queries can be exposed as OData feeds.

Extend cubes [AX 2012]

you can customize the prebuilt analysis project relatively easily by using the SQL Server Analysis Services Project Wizard. But in some cases, you may want to make
deeper customizations. For example, you might want to:
■ Create a rich hierarchy, such as a parent/child hierarchy to model organizational units.
■ Add new KPIs.
■ Bring external data into the analysis project and create a custom dimension.
You can use Business Intelligence Development Studio to make these types of changes.

Because the prebuilt BI components are included in the AOT as an SSAS project, you can modify the project. To modify the prebuilt Analysis Services project, do the following:
1. In the AOT, expand the Visual Studio\Analysis Services Projects node.
2. Right-click the project that you want to modify, and then click Edit.
An Infolog message appears, stating that a copy of the SSAS project has been created and saved, as shown in Figure below

 

If SQL Server Business Intelligence Studio is installed, it will start and open the copy of the project.
Changes that you make to the project are not automatically saved to the AOT. You need to save the project and import it back into the AOT.

DSV
The DSV contains the table and view definitions that are used by analytic artifacts. Notice that the OLAP framework has implemented several query definition patterns in the DSV:
■ Financial dimensions that the wizard has added appear as custom query definitions in the DSV.
■ The OLAP framework has created query definitions corresponding to Microsoft Dynamics AX views.
■ The OLAP framework has added a reference relationship to resolve virtual companies, if your Microsoft Dynamics AX installation has virtual company definitions.
■ The OLAP framework has created views that make Microsoft Dynamics AX enumerations accessible

in all of the languages that have been added to the project.
Avoid modifying any of the framework-generated objects in the DSV. Any changes that you make to these objects are overwritten without warning the next time you update the project.
You may add your own objects to the DSV (for example, new query definitions. The Project Update  option will preserve these objects.
In Microsoft Dynamics AX 2012 R2, do not implement any partition-specific logic in any of the query definitions. Otherwise, when the project is deployed to multiple partitions, the system may
generate processing errors. (Because the framework adds partition-specific logic to the DSV at deployment time, it may not apply the changes accurately to your query definitions.)

Data source
A data source has been created that points to the Microsoft Dynamics AX OLTP database.

Dimensions, measures, and measure groups

In Figure below , notice the dimensions that are included with the Microsoft Dynamics AX 2012 prebuilt BI solution, as well as the measures and measure groups.
For a list of measures and dimensions, see “Cube and KPI reference for Microsoft Dynamics AX 2012” at http://msdn.microsoft.com/en-us/library/hh781074.aspx.

KPIs and calculations
The SSAS project contains prebuilt KPIs and calculations. Microsoft Dynamics AX 2012 does not provide the capability to model KPIs and calculations in the AOT. You can modify these definitions or
add new ones directly in Business Intelligence Development Studio.

Customize cubes [AX 2012]

This post related to this post [Customizing the prebuilt BI solution]
Figure below shows the process for updating a cube. This post walk through each step in detail.

Choose the project to update
The first step is selecting the project to modify. You can select an SSAS project in the AOT or a project maintained on disk. The wizard performs basic validation of the selected project before you can proceed.
The update process is designed to ensure that you end up with a project that you can
deploy and process without any errors. If the selected project does not build (the most basic measure of validity), the wizard will not let you proceed to the next step.

Customizing the prebuilt BI solution

As you have seen in the previous post, it’s relatively easy to implement the prebuilt BI solution in Microsoft Dynamics AX 2012. But regardless of how good the prebuilt BI solution is, you may want to change the functionality to suit your needs.
These changes can be divided into three broad categories:■ Configuration Although the prebuilt BI solution is designed to cover all of the functionality in Microsoft Dynamics AX 2012, you may have implemented only certain modules. Even within those modules, you may have chosen to disable certain functionality. In Microsoft Dynamics AX, license codes and configuration keys govern the availability of modules and functionality, respectively. (For more information, see Chapter 11, “Security, licensing, and configuration.”) Configuration keys correspond to functionality within modules. They can be enabled or
disabled.
If you do not activate certain license codes or if you disable certain configuration keys, the Microsoft Dynamics AX user interface configures itself by removing content that is associated with those elements. In this case, you may need to remove the corresponding analytic content. (However, because the prebuilt BI solution draws data from across Microsoft Dynamics AX, this content will not be hydrated with data in any case.) You can use the SQL
Server Analysis Services Project Wizard to remove the corresponding content from the prebuilt cubes, so that you do not have to remove the irrelevant content manually yourself.
■ Customization You might want to add additional calendars and financial dimensions, and also new attributes and measures, to the prebuilt cubes. The SQL Server Analysis Services Project Wizard lets you perform the most frequent customizations with a step-by-step approach, without requiring BI development skills.
■ Extension At some point, you may want to develop extensions to prebuilt cubes by using the SQL Server BI development tools. Table below lists categories of customizations, summarizes the types of changes that you can make, and lists the skill level, time, and tools required to make those types of changes.

Configure analytic contentAs previously explained, you can configure the predefined analytic content to reflect configuration changes in Microsoft Dynamics AX in a matter of minutes by using the SQL Server Analysis Services Project Wizard. In Microsoft Dynamics AX 2009, this process had to be performed manually. This process required BI development skills and a day or two of spare time. Microsoft Dynamics AX 2012 dramatically simplifies this process by introducing the following three improvements:
■ Static schema Historically, Microsoft Dynamics AX has had a schema whose shape changed depending on licenses and configuration keys. That is, when a configuration key was turned off, the database synchronization process dropped tables and data that were deemed invalid.
This caused prebuilt cubes (that rely on a static schema in the underlying database) to break at processing time. Unlike its predecessor, Microsoft Dynamics AX 2012 has a static schema.
So, when configuration keys are disabled, the database schema no longer changes. This means that prebuilt cubes can continue to be processed without generating errors. (They will, for example, contain empty measures, because the corresponding tables have no data).
■ Improved modeling capabilities in the AOT The Microsoft Dynamics AX 2009 OLAP framework did not allow advanced modeling of constructs in the AOT. As a result, developers had to implement any functionality that was lacking directly in an SSAS project. In Microsoft Dynamics AX 2012, a larger portion of analytic content is modeled in the AOT. Therefore, configuring the content can be done much more easily by the framework.
■ Wizard-driven user interface The six different forms that were necessary in Microsoft Dynamics
AX 2009 have been replaced by a single step-by-step wizard that guides you through various activities.
To configure the prebuilt BI project, you must have developer privileges in Microsoft Dynamics AX.
This step modifies the project so that irrelevant measures, dimensions, and entire cubes are removed
after the process is completed. The modified project will be saved in the AOT in your own layer.
To configure the project, start the SQL Server Analysis Services Project Wizard, and then select the Configure option. You then need to select the project to configure. Select the Dynamics AX project to configure the prebuilt project, and step through the wizard. For step-by-step instructions, see the “How to: Configure an Existing SQL Server Analysis Services Project” at http://msdn.microsoft.com/en-us/library/gg724140.aspx.
If you also deploy and process the project, you should notice the following changes:
■ Cube content (such as measures and dimension attributes that source data from tables that are affected by disabled configuration keys) is deleted from the project. You may see that entire cubes have been removed if the corresponding content has become invalid.
■ KPIs and calculated measures have been removed in cubes that depend on disabled measures and dimension attributes.
■ OLAP reports in Role Centers that source data from cubes that have been removed no longer appear on the Role Center page. If a user intentionally adds such a report to the Role Center, the report displays a warning message and will execute.
■ KPIs and measures that were removed no longer appear in the Business Overview web part.

Implementing the prebuilt BI solution

Traditionally, BI solutions are implemented during the second or third phase of an Enterprise Resource Planning (ERP) implementation project. Needless to say, project fatigue sets in (and the budget gets exhausted), and subsequent phases are postponed or delayed. BI implementation is complex and involves the integration of many components. Also, the skill set required to implement a BI solution is distinctly different from the skill set required to implement an ERP system. Often, implementation of the BI solution involves engaging a different partner or consultants. All of these factors contribute to postponing the BI implementation.

Microsoft Dynamics AX 2012 simplifies the implementation of a BI solution, so that all Microsoft Dynamics AX 2012 partners and customers (regardless of whether they have access to BI specialists) can implement the prebuilt BI solution when they implement the ERP functionality.

In Microsoft Dynamics AX 2012, the default SQL Server Analysis Services (SSAS) project is a
first- class citizen of the Application Object Tree (AOT), as are other SSAS projects that you create in the AOT. This means that SSAS projects derive all of the benefits of being residents of AOT.
■ SSAS projects respect the layering concept. This means that an independent software vendor (ISV) or partner can distribute a customized version of an SSAS project that adds additional analytic components to the solution that is included in the SYS layer.
■ You can import and export SSAS projects to and from different environments as part of a model (by using models or .xpo files).
■ SSAS projects respect the version control capabilities offered by AOT-based artifacts.

When you deploy a project by using the SQL Server Analysis Services Project Wizard, which is new in Microsoft Dynamics AX 2012, the wizard selects the project in the highest layer for deployment.

If you examine the Visual Studio Projects node in the AOT, will see the default SSAS project that is included with Microsoft Dynamics AX 2012, as shown in Figure below. If you have any customizations at higher levels, they are also displayed.

Implementing the prebuilt BI solution consists of the following steps:
1. Implement the prerequisites.
2. Configure an SSAS server.
3. Deploy the cubes.
4. Process the cubes.
5. Provision users so that they can access the analytic data.

The following sections describe each step in further detail.

1- Implement the prerequisites
Before you implement the analytic components in the prebuilt BI solution, the following Microsoft Dynamics AX core components should be in place:
■ At least one AOS instance must be implemented.
■ The Microsoft Dynamics AX Windows client must be implemented, and the initialization checklist must be completed.
■ The Enterprise Portal web client must be configured.

If you are implementing the analytic components on a development or test instance, you might not implement a scale-out architecture. However, if you are implementing these components in a
production system, you may want to implement a redundancy or load balancing infrastructure. You need to configure the clustering or Network Load Balancing (NLB) solution before you implement the
analytic components.

2- Configure an SSAS server
This step configures a given SSAS server for the Microsoft Dynamics AX 2012 analytic components.

To do so, run the Configure Analysis Extensions step in the Microsoft Dynamics AX Setup wizard on the SSAS server that hosts Microsoft Dynamics AX 2012 cubes.
Running the configuration step should take you a few minutes. This function does the following:
■ Ensures that the SSAS server has all of the necessary prerequisites to host Microsoft Dynamics AX 2012 cubes.
■ Adds the Business Connector (BC) proxy user as an administrator of the SSAS server. This step is required to enable AXADOMD data extensions to operate without the use of Kerberos
constrained delegation.
■ Allows you to add a read-only user account to the Microsoft Dynamics AX 2012 database for processing cubes (you should specify a domain account whose password does not expire).

 

3- Deploy cubes
When you deploy cubes, Microsoft Dynamics AX generates and processes an OLAP database by using the metadata definition contained within the Analysis Services
project that is included with Microsoft Dynamics AX 2012. The result is an OLAP database that contains
Microsoft Dynamics AX cubes that are referenced by analytic reports and Role Centers.
In a Microsoft Dynamics AX 2012 R2 environment where there is only a single partition, the deployment step generates a single OLAP database that sources data from the Microsoft Dynamics
AX OLTP database. In a multiple-partition environment, the deployment step generates multiple OLAP databases that correspond to each partition. Figure below shows the deployment process both
in a single-partition and multiple-partition environment.

You use the SQL Server Analysis Services Project Wizard in the Microsoft Dynamics AX 2012 client to deploy, process, and in some instances, update cubes. To deploy the cubes, you must have the
right to deploy projects to the SSAS server. If you are also processing the cubes, you must have the right to read the Microsoft Dynamics AX 2012 OLTP database.

To start the SQL Server Analysis Services Project Wizard and deploy cubes, do the following:
1. In the Development Workspace, on the Tools menu, click Business Intelligence (BI) Tools > SQL Server Analysis Services Project Wizard.
2. On the Welcome page, click Next, and then select the Deploy option on the next page, as shown in Figure below

3. On the next page, you select an SSAS project to deploy—in this case the Dynamics AX project.
You can select a project in the AOT, as shown in Figure below, or you can select a project that is saved on a disk.

4. Next, you specify the SSAS server to deploy the project to, the SSAS database you want to use, and whether you want the project to be processed after deployment .
By default, the wizard uses the SSAS server that you configured earlier, but you can select any server to deploy the project to.

Deploy cubes in an environment with multiple partitions
As mentioned earlier, in a Microsoft Dynamics AX 2012 R2 environment with multiple partitions, the SQL Server Analysis Services Project Wizard generates an OLAP database for each partition. You can
use the wizard to select the partitions for which OLAP databases are created, as shown in Figure below

In this case, the SQL Server Analysis Services Project Wizard deploys the SSAS project to multiple OLAP databases. In each database, <partitionkey> is added as a suffix to the name of the OLAP
database.
Also, within each OLAP database, the data source view (DSV) is modified so that a partition filter is applied to all queries. Figure 10-8 shows the architecture of an environment with multiple partitions.
In all cases, the SSAS project in the AOT is partition-unaware, whereas the OLAP databases that are deployed are partition-specific. The SQL Server Analysis Services Project Wizard handles the step of
making sure that each OLAP database is wired to read data only from the corresponding partition in Microsoft Dynamics AX. This is a departure from the behavior of Microsoft Dynamics AX 2012. You
need to be aware of the following implications:
■ If you deploy Microsoft Dynamics AX SSAS projects by using Analysis Services tools, such as the Deployment Wizard or Business Intelligence Development Studio, the resulting OLAP
database is not partition-aware. In other words, cubes will aggregate data across partitions.
■ If you want to extend an SSAS project, always check out and modify the project in the AOT.
Do not customize a project associated with a specific partition by importing the project directly in Business Intelligence Development Studio. The Deploy function in the wizard will overwrite any partition-specific customizations that you have made directly on the server.
■ If you add custom query definitions in the DSV, the wizard adds where clauses to each select statement that restrict rows from other partitions.

4- Process cubes
The SQL Server Analysis Services Project Wizard lets you process deployed cubes directly. However, before processing, the wizard also runs through several prerequisite checks to ensure that cube
processing will not fail later. If you are using demo data, you can ignore these preprocessing warnings and have the wizard process the cubes.

While the project is being processed, the wizard displays a progress page. When processing is complete, click Next, and the wizard will show the completion screen.

 

5- Provision users in Microsoft Dynamics AX
After you deploy and process Microsoft Dynamics AX cubes, you must grant users permissions to access them. Provisioning users involves two activities:
■ Associate an appropriate user profile with each Microsoft Dynamics AX user.
■ Provide Microsoft Dynamics AX users with access to the OLAP database.

Reporting service deployment error for Dynamics ax 2009

 

Error: “THE FOLLOWING COMPONENTS HAVE NOT BEEN INSTALLED OR ARE NOT CONFIGURED CORRECTLY: AL.EXE, MICROSOFT DOMAIN – SPECIFIC LANGUAGE TOOLS”
This error message indicates that the following software components are not installed:

• Windows SDK for Windows Server 2008 and .NET Framework 3.5
• Microsoft Visual Studio 2008 Shell (isolated mode)

 

Error: “THE MICROSOFT.DYNAMICS.CLRBRIDGE.DLL FILE IS NOT LOADED”

1. Close the Microsoft Dynamics AX Reporting Project Deployment form.
2. click Start Menu ---> Dynamics ax folder ---> right click on “Dynamics Ax 2009 reports Deployment then “ then run as Administrator

Walkthrough: Displaying KPIs in a Role Center [AX 2012]

You can display the KPIs that you created in a web part on your role center page in Microsoft Dynamics AX or Enterprise Portal.

The following procedure explains how to add the Sales Analysis KPI to a web part in the CEO Role Center page.

To display the KPIs in a Business Overview Web part

1. Navigate to the CEO role center that is located at http://<server>/sites/DynamicsAx/Enterprise%20Portal/RoleCenterCEO.aspx.

2. On the Site Actions menu, click Edit Page. Locate the Middle Column section, and then click Add Web Part

3. In the Categories list, click Microsoft Dynamics AX. In the Web Parts list, select Business overview, and then click Add.

4. On the drop-down menu for the web part, click Edit Web Part. The properties for the web part are displayed.

5. For the Select mode property, select KPI List.

6. Expand the Business Overview Setup node.

   Note

   The Business Overview web part points to the default Dynamics AX Analysis Services database. You can use any KPIs that ship with Microsoft Dynamics AX and any KPIs that you add to that database. If you create another database, you must create an Office Data Connection (ODC) file that points to that database. You then must specify the location of the ODC file in Data Connection.

7. For the Title property, type Sales KPIs. Click OK to save the changes.

8. In the Sales KPIs web part, click Add KPIs.

9. In the Business Overview - Add KPI dialog box, select the Sales Analysis cube, select the Customer sales KPI, select Amount for the Display value as field, and then click OK.

   Note

   If you created a new Analysis Services database that has only the SalesAnalysis cube, you do not need to select a cube in the Business Overview - Add KPI dialog box.

10. Click Stop Editing to save the changes made to the page.

Resource Page for Enterprise Portal and Role Centers in Microsoft Dynamics AX 2009

This link below is intended to provide a consolidated view of relevant documentation, videos, solutions to known issues, links to related resources, as well as community sites for implementing Enterprise Portal and Role Centers for Microsoft Dynamics AX 2009.

http://community.dynamics.com/ax/b/axresources/archive/2012/02/13/resource-page-for-enterprise-portal-and-role-centers-in-microsoft-dynamics-ax-2009.aspx#.UUSBhypXtls

Inside Microsoft Dynamics AX 2012 - Enterprise Portal

How to automatically process SQL Server Analysis Services Cubes

In order to have the latest data presented in the Dynamics AX 2009 OLAP Reports, such as the ones contained in Role Centers, the SQL Server Analysis Services cubes
must be processed regularly. Typically, processing the cubes once a day is sufficient for most basic business needs. However, for companies that utilize business
intelligence more than average, this may not be sufficient. The more frequently cubes are processed, the more up-to-date that data in the OLAP reports is.
Many common automated procedures for SQL Server, such as backing up a database, can be performed by using SQL Maintenance Jobs. Unfortunately, you
cannot automatically process SQL Server Analysis Cubes the same way. In order to automatically process cubes, a SQL Server Integration Services package must be
created and scheduled to run as an SQL job.
The following steps outline the process of automating the cubes:
1. Load SQL Server Business Intelligence Developer Studio (BIDS).

2. Create a new Integration Services Project.

3. Add a new connection to the Integration Services Project by right-clicking on the Control Flow tab and click on New Connection… and select
MSOLAP100 for an Analysis Services connection.

4. Provide the appropriate connection information. If the Analysis Server is on a separate server than the Database Engine and Kerberos Authentication
are setup, append ;SSPI=Kerberos to the end of the connection string. To specify additional connection options and to test the connection, click on the
Edit button.

5. In the Connection Manager window, specify the Initial Catalog to the Analysis Extension's OLAP database. Test the connection to verify that it
works. Once complete, click on the OK button to save. Then, click on OK in the Add Analysis Services Connection Manager window to finally save and
create the connection manager.

6. Now that the connection is set up, drag over an Analysis Services Processing Task from the Toolbox.

7. Right-click on the task and Edit the task.

8. In the Analysis Services Processing Task Editor, select Processing Settings and click on the Add button to select which cubes you want to
have processed.

9. After you have selected the appropriate cubes to be processed and they are added to the Analysis Services Processing Task Editor, click on OK to save.

10. In Visual Studio, build the project by going to Build | Build Process Cubes.

11. Once the project builds successfully, the next step would be to create a SQL job that runs the SSIS package on a specific schedule. To create a job, open the
SQL Server Management Studio and log in to the Database Engine server and select the SQL Server Agent node.

1. In the SQL Server Agent, right-click on the Jobs folder and click on New Job... to create a new job that will automatically process the cubes.4

2. In the New Job window, in the General page, provide a Name for the job.

3. Select the Steps page and click on the New button to create a new job step that will run the SSIS package to process the cubes.

4. In the New Job Step window, specify a name for the step, change the type to SQL Server Integration Services Package, select Package source to be File
system, and browse for the dtsx file that was built in Visual Studio from step.
When the appropriate fields are specified, click on the OK button to create the step.

5. Now that we are back in the New Job screen, go to the Schedules page and click on the New button to specify a recurring date and time to process
the cubes.

6. In the New Job Schedule window, provide a name, date, and time information which the job should run automatically on. Click on the OK
button when complete to create the schedule.

7. There are additional pages in the New Job window, such as providing an e-mail to contact, which can be used when a job errors or completes. To
finally create the job, click on the OK button.

Now that the SQL Job has been created, to process cubes, the job will run the SSIS package that was created to process cubes automatically at the specified date and time.

Resource Page for SSRS and SSAS Integration in Microsoft Dynamics AX 2009

Imparted from here

This page is intended to provide a consolidated list of published documentation, known issues, solutions as well as tips and tricks for SSRS and SSAS integration in Microsoft Dynamics AX 2009.
Important Note: Many of the links on this page go to CustomerSource. Learn more about CustomerSource and how to sign in
The default OLAP cubes that are provided with Microsoft Dynamics AX were designed with full license and configuration keys. When using License and Configuration Keys where all modules are not present, OLAP cubes will be need to be configured. If any license or configuration key is turned off, you must complete the procedures in the Microsoft Dynamics AX 2009 White Paper: Configuring the Default OLAP Cubes.
The Enterprise Portal Role center pages contain SSRS reports and SSAS default cubes. If you have not implemented the SSRS or have not completed your Dynamics® AX customizations you may want to consider removing the SSRS web parts from Enterprise Portal or selecting the Default Role Center which does not have BI content. Implementing the reporting features can be done at a later time after the main implementation is complete.
When setting up SSRS, SSAS, and WSS or MOSS on multiple severs you will need to be aware of how to set up and configure Kerberos Authentication. See the Microsoft Dynamics AX 2009 White Paper: Configuring Kerberos Authentication with Role Centers and the common problems section below.

On this page:

• Top Downloads
• Prerequisites - Installation and Setup
• Featured Videos
• Related Resources
• Common Problems & Solutions
• Troubleshooting Tips
• Still having trouble...
• Acronyms used in this article

---

Top Downloads

• System Requirements for Microsoft Dynamics AX 2009
• Hot Fixes Released for Microsoft Dynamics AX 2009
• Microsoft Dynamics AX 2009 Installation Guide
• Microsoft Dynamics AX 2009 Client Help Update
• Microsoft Dynamics AX 2009 SP1 Client Help Update
  • Note: The System and Application Setup Guide can be found in AxSASetup.chm that is included in the updated client help files.
• Microsoft Dynamics AX 2009 Known Issues
• Steps to setup AOS, client, workflow, and .NET BC for debugging Workflow

Top

Prerequisites - Installation and Setup

A number of the common issues can be resolved by ensuring that the prerequisites have been properly installed on the correct servers and by carefully reviewing the installation and troubleshooting documentation before attempting the actual installation.

• Microsoft Dynamics AX 2009 Installation Guide
• SSRS and SSAS for SQL Server:
  • SQLServer 2005 with SP2 OR SP3
    Note: Only installs if registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Reporting Services" exists and Version key value = 9.00.3042.00
  • SQL Server 2008 with latest service pack
    Note: If running SQL Server 2008, install 1 of the following:
    • KB957312 for Microsoft Dynamics AX 2009 RTM and SQL Server 2008
    • KB960158 for Microsoft Dynamics AX 2009 SP1 and SQL Server 2008
• Visual Studio 2008 RTM with KB947173 fix installed OR Microsoft Visual Studio 2008 Service Pack 1 installed
• IIS 6.0 OR IIS 7.0
• Windows SDK for Windows Server 2008 and .NET Framework 3.5
  Note: The SDK needs to be a single package as provided by this link.
  Note: Install regardless of operating system, Windows Server 2003 or Windows Server 2008
• Microsoft Visual Studio 2008 Shell (isolated mode) Redistributable Package
• Domain accounts will need to be assigned as noted in the Installation Guide.

Top

Featured Videos

• "How Do I" Videos – Microsoft Dynamics AX on MSDN
• AX 2009 SSRS Integration and Deployment Tips and Tricks Part 1
• AX 2009 SSRS Integration and Deployment Tips and Tricks Part 2
• AX 2009 SSRS Integration and Deployment Tips and Tricks Part 3

Top

Related Resources

• System Requirements for Microsoft Dynamics AX 2009 available on the Using Microsoft Dynamics® AX 2009 site.
• Microsoft Dynamics AX Installation Guide is included on the Microsoft Dynamics® AX 2009 DVD or you can download the most recent guide from the Microsoft Download Center.
• System and Application Setup Guide within the Microsoft Dynamics® AX 2009 client help. Updated help files are available for download:
  • Microsoft Dynamics AX 2009 Client Help Update
  • Microsoft Dynamics AX 2009 SP1 Client Help Update
    Note: The System and Application Setup Guide can be found in AxSASetup.chm that is included in the updated client help files.
• Creating Reports for Microsoft Dynamics AX in Visual Studio available on the Microsoft Dynamics AX Development Center
• Expression Examples (Reporting Services) available on the SQL Server Development Center
• Configuring Enterprise Portal and Role Centers with SQL Server Reporting
• Configuring Kerberos Authentication with Role Centers
• Configure the Default OLAP Cubes
• Microsoft Dynamics AX 2009 Business Intelligence Cube Reference Guide
• Role Center reference for Microsoft Dynamics AX
• Microsoft Dynamics AX 2009 Known Issues
• Fixing Microsoft Dynamics AX Cube Processing Errors Caused by EDT Field Changes
• How to make an existing Enterprise Portal site SSL enabled
• Default Cube Advisor Tool - Generates a list of cube elements and Role Center elements that are not valid for the specific license and configuration keys you are using.
• Extending Default Cubes for Virtual Companies
• Microsoft Dynamics AX Business Intelligence Blog site

Top

Common Problems & Solutions

This section lists the most common issues encountered when building the integration between Microsoft Dynamics® AX, SSRS and OLAP and the solution recommended by the Microsoft Dynamics® AX Support team.
Issue
Error trying to deploy reports:
Microsoft Dynamics AX Reporting Project Deployment: The following components have not been installed or are not configured correctly: AL.exe
Solution
Download and install the Windows SDK for Windows Server 2008 and .NET Framework 3.5 Ensure it is fully installed.
Note: Install regardless of operating system
Issue
Error trying to deploy reports
System.InvalidOperationException: The following components have not been installed or are not configured correctly: Microsoft Domain-Specific Language Tools
Solution
Download and install these required components. Microsoft Visual Studio 2008 Shell (isolated mode) Redistributable Package

1. Save the download locally .
2. Extract the package.
3. Run the vs_appenvredist.msi
   Note: Install regardless of operating system

Issue
Error trying to deploy reports
Microsoft Dynamics AX Reporting Project Deployment: ClrBridgeLoader: fatal error :
Microsoft.Dynamics.ClrBridge.dll cannot be loaded. Fatal error: ClrBridge is note loaded.
Solution
Ensure you are trying to deploy reports from the SSRS server and that you can validate the SSRS server name in the Reporting Servers from within Microsoft Dynamics AX 2009. If this error appears right after installing the reporting extensions, launch the report deployment tool again.
Issue
Enterprise Portal (EP) or SSRS Reports don’t run or stop working
An attempt has been made to use a data extension 'AXDATAMETHOD' that is not registered for this report server. (rsDataExtensionNotFound)
or
data extension 'AXQUERY' and 'AXADOMD'
Solution
Installing or Reinstalling Reporting Extensions will resolve this issue. As a precaution make a Backup of:
Program Files\Microsoft SQL Server\MSSQL.<Instance>\Reporting Services\ReportServer folder

Note: SSRS updates or Service Packs may remove entries from rsreportserver.config file.
Issue
Enterprise Portal (EP) Reports don’t run or stop working
A ProgressTemplate must be specified on UpdateProgress control with ID 'AxProgressControl'
Solution
You can resolve the issue by using one of the three methods below:

1. Apply the hotfix from KB957312 to the RTM version.
2. Upgrade to Microsoft Dynamics AX 2009 SP1.
3. Un-install Microsoft .NET 3.5 SP1 and reinstall Microsoft .NET 3.5 without SP1

Issue
Report deployment tool crashes
Attempted to read or write protected memory. This is often an indication that the memory is corrupt
Solution
If multiple versions of Dynamics AX are installed on the same server you will need to change your AX 2009 Path in your environment variables ahead of your AX 4.0 path to avoid running the wrong version of DLL’s
Issue
Error running reports
Error during processing of 'AX_CompanyName' report parameter. (rsReportParameterProcessingError).
Solution
Process OLAP the cubes to supply data to the reports
or
An incorrect Execution account has been specified in the Reporting Services Configuration Manager
Note: For SSRS 2008 the Business Connector proxy account is required to be the SSRS service account and for SSRS 2005 the Business Connector Proxy account should be running as the SSRS application pool in IIS. Also look at application event log for details on other issues.
Issue
Enterprise Portal (EP) web site runs but not the reports in the EP web parts:
Dynamics Adapter LogonAs failed
or
Microsoft.Dynamics.BusinessConnectorNet.LogonFailedException
Solution
Leave the Execution account blank on SSRS 2005 or set to BC Proxy account on SSRS 2008 (Microsoft Dynamics AX 2009 SP1 only)
Note: SSRS Execution account is set to an account other than BC Proxy Account
Issue
EP or SSRS Reports don’t run or stop workingDynamics Adapter LogonAsGuest failed
or
FatalSessionException...
Solution
The issue is caused by the Reporting Services web site set to anonymous Authentication. Changing the SSRS website to Integrated and/or un-marking Anonymous Authentication will resolve this issue.
Issue
Double Hop \ Kerberos Authentication
An Error has occurred while establishing as connection to the Analysis Server
or
Reports don’t display in the EP website from a Client Browser not local to the IIS server
Cannot read information from SQL Server Reporting Services. Validate that the Report Manager URL is correct
Solution
Setup Service Principle names (SPN) and Delegation to allow the passing of Kerberos certificate
References:

• White Paper: Configuring Kerberos Authentication with Role Centers
• KB917409: How to configure SQL Server 2005 Analysis Services to use Kerberos authentication
• MSDN blog: Enterprise Portal Kerberos Delegation for connecting to Reporting/Analysis Services on a different box
• TechNet blog: Understanding Kerberos Double Hop

Issue
Office Data Connection (ODC) file deployment fails with SQL Server 2008
Microsoft Dynamics AX is searching for the SQL Server 2005 Microsoft.AnalysisServices.dll (v9.0.242.0)
Solution
Apply one of the following hotfixes:

• For Microsoft Dynamics AX 2009 RTM: Apply the fix from KB957312
• For Microsoft Dynamics AX 2009 SP1: Apply the fix from KB960158

If the hotfix does not resolve the issue, make sure you are running a Dynamics AX 2009 client on the EP web server when deploying the ODC files. As a workaround you can manually deploy the ODC files by following these steps:

1. Click here to download a new ODC file (Dynamics_AX.odc).
2. Save the ODC on the SSAS server.
3. Open the ODC file with Notepad or any other text editor.
4. Edit the odc file with the following changes:
   Data Source=OLAPServerName
   Initial Catalog=OLAPDbName
   Add SSPI=Kerberos after Initial Catalog if using Kerbersos (in red only required for Kerberos authentication)
   …
   ….
   <odc:Connection odc:Type="OLEDB">
   <odc:ConnectionString>Provider=MSOLAP.3;Integrated Security=SSPI;Persist Security Info=True;
   DataSource=<Server1>;Initial Catalog=Dynamics AX;SSPI=Kerberos
   </odc:ConnectionString>
   …
5. Save the changed ODC file.
6. Go to EP main site.
7. Click Site Actions, and then click Site Settings.
8. Under Galleries, click Master pages.
9. Click View all site content (top left).
10. Click Data Connections folder.
11. Import the edited ODC file.

Issue
DataSet panel is missing in Report Designer when creating reports in Visual Studio Server 2008
Solution
For Visual Studio 2008, apply the fix in KB947173
OR
apply Microsoft Visual Studio 2008 Service Pack 1.
Issue
"Connection forcibly closed by remote host" in Dynamics setup log when trying to create an EP site in Microsoft Dynamics AX 2009
Solution
Download and install the Microsoft Analysis Management Objects:

• for SQL Server 2005: Microsoft SQL Server 2005 Management Objects Collection package
• for SQL Server 2008: Microsoft Analysis Management Objects package

Issue
"Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'"
Solution
Ensure SSRS service is running and are able to connect to instance via SQL Server Management Studio.
Note: Additional information can be found in SSRS error log.
Issue
Exception from HRESULT: 0X80041FFF
Solution
Change Visual Studio project location to local drive if using a network share
Issue
The Analysis extension is not seeing the SQL cluster name for Analysis Services when Analysis services is setup on a SQL cluster.
You will get an error similar to this when trying to install Analysis Extension in this environment:
Connecting to SQL Server 2005 Analysis Services on server 'SQL02' and instance 'MSOLAP$ANALYSIS'.
A connection cannot be made. Ensure that the server is running.
No connection could be made because the target machine actively refused it 127.0.0.1:2383
An error occurred while Setup was connecting to SQL Server Analysis Services instance 'MSOLAP$ANALYSIS' on server 'SQL02'.
An error occurred while Setup was connecting to SQL Server Analysis Services instance 'MSOLAP$ANALYSIS' on server 'SQL02'.
Solution
The workaround is to manually run the script to create the Dynamics AX OLAP db from the AX 2009 CD.
Navigate to this folder: \support\Analysis Services\Scripts on the Microsoft Dynamics AX 2009 installation CD.
Then run the dynamicsax.xmla script from within SQL Management Studio (connected to the SSAS instance).
This script will create the Dynamics AX OLAP database.
Issue
BC Proxy account fails to start for the SSRS reports in Enterprise Portal with RPC exception 5
When Enterprise Portal starts for the first time and displays SSRS reports, normally two Business Connectors are started. After a period of time or if the impersonated web user logs out for the SSRS Proxy account you may experience an RPC error 5 access denied and the SSRS reports will no longer display in Enterprise Portal.
Example Event Type: Error
Error:
Event Source: Dynamics .NET Business Connector 5.0
Event Category: None
Event ID: 180
Date: 10/7/2008
Time: 6:21:04 PM
User: N/A
Computer: AX2009
Description:
Microsoft Dynamics AX Business Connector Session 18.
RPC error: RPC exception 5 in Ping occurred in session 36
Solution
RPC error 5 can occur if the SSRS Execution account is set in the Reporting Services Configuration Manager. If the account used is the Business Connector proxy account the first startup of the Business Connector will work, but not any subsequent startups unless the IIS application pool if recycled or an IIS reset is done.
SSRS 2005
Remove the SSRS execution account through Reporting Services Configuration Manager and ensure the Business Connector account is running the IIS Application Pool for the SSRS web site.
SSRS 2008
Change the SSRS service to start as the Business Connector Proxy account and remove the SSRS execution account through Reporting Services Configuration Manager.
Note: Changing the SSRS account would require a change in the registered SPN’s if you are using Kerberos authentication
Top

Troubleshooting Tips

• Windows SDK for Windows Server 2008 and .NET Framework 3.5 – only Developer Tools / Windows Development Tools / .NET Development Tools needs to be installed.
• Enable remote errors for SSRS - http://technet.microsoft.com/en-us/library/aa337165(SQL.90).aspx

Top

Still having trouble...

If you are experiencing issues downloading the install file or documentation on CustomerSource/PartnerSource, please contact ITMBSSUP@microsoft.com

1. Ask the community of users like yourself through the Microsoft Dynamics AX Community here.
2. For Technical support questions, contact your partner, or if enrolled in a support plan directly with Microsoft, you can enter a new support request to Microsoft Dynamics Technical Support from CustomerSource or PartnerSource under Support >> New Support Request
   3. You can also contact Microsoft Dynamics Technical Support by phone using these links for country specific phone numbers:
3. Partners – Global Support Contacts (requires PartnerSource login)
   Customers – Global Support Contacts (requires CustomerSource login)

Top

Acronyms used in this article

• SSRS - SQL Server Reporting Services
• SSAS - SQL Server Analysis Services (sometimes referred as OLAP)
• OLAP - On-Line Analytical Processing
• WSS - Windows SharePoint Services
• MOSS - Microsoft Office SharePoint Server
• BI - Business Intelligence
• EP - Enterprise Portal
• AMO - Analysis Management Objects (part of Microsoft SQL Server)

Imparted from here

Dynamics ax BI installation Trouble Shouting

(1) Installation of Enterprise portal component, gives the following
error:Error executing code: SysDevelopmentProxy (object) has no valid runable
code in method 'generate'.

a. Go to Ax Client ( on a machine where Business Connector is installed)

b. Open the AOT\Classes node

c. Right click on the SysDevelopmentProxy class node and select compile

and make sure it compiles correctly. Then run the EP deployment.

(2) I have successfully created the EP Site and I can view the site.
But other users are not able to view it.

a. Make sure the user is added to Ax and to the right AX user groups.

b. Make sure the user is configured as Employee or Customer or Vendor in User
Relations form in Ax k

c. Make sure the user is added in EP site using Site Settings

   i. Click on the “Site Actions” tab, and select “Site Settings”
from the drop down list

   ii. Click the “People and groups” link

   iii. Click the “New” button, in the “Add Users” page click the
“Add all authenticated users” and check all the permissions boxes to give all
configured users full rights

   iv. Click “OK”

(3) Role Centers are working fine in EP , but are not coming up in
Ax Client

a. Make Sure the "Web site used to dispaly Role Center in the Ax
Client " setting in Administration -> Setup -> Internet -> Web
Sites form at the bottom right is set to the right EP site

b. Navigate to the EP site mentioned in the above setting and verify none of
the web parts are throwing any error. If any web part is not rendering
correctly , either fix the source of the problem for that web part or remove
that web part

(4) After I added “Business Overview WebPart”, I tried to add some
indicators. It gave the error message “An error has occurred while
processing the business overview indicator. Check the web server application
event log for more information.” From Event Viewer:“An unexpected
error has occurred.The period is not valid......"

Did you initialize the profiles? You need to "Initialize Role
Center Profiles" from Basic->Setup->Role Center or Import Time Periods
from Administration -> Setup -> Business Analysis -> OlAP -> Time
Periods

(5) In Enterprise Portal setup BC Proxy
Account cannot be set if the FQDN is not a superset of the short domain name

In Enterprise Portal setup BC Proxy Account cannot be set if the
FQDN is not a superset of the short domain name

if the FQDN is different from the short domain name , for example

If the FQDN = XYZ.microsoft.com

and the short dominname = XYZCORP

then setting the BCProxy user during EP setup fails.

To workaround,

(1) change the app pool in IIS used by the EP Site to  to be run by the bc
proxy account with the FQDN specified.

(2) Also blank out the business connector proxy account in Ax.

(3) Then run EP setup and n the BC proxy user dialog , use the FQDN of the bc proxy.

(6)Manage Deployments dialog in Ax Client for Enterprise Portal may
not function correctly on 64 bit machine

Manage Deployments dialog in Ax Client for Enterprise Portal may not
function correctly on 64 bit machine

Administration->Setup -> Internet -> Enterprise Portal -> Manage
deployments on 64 bit machine may give

"Manage Deployment can not run because Enterprise Portal is not deployed
on this computer" even though Enterprise Portal is deployed and working
fine. Manage Deployment is used to update the Enterprise Portal web server with
the changed made in AOT web files and resources. To workaround this probelm,
use the alternate way of publishing these changes to the web server, which is
running Ax Setup and deploy EP without recreating the site.

(7) KPIs and Business Overviw keeps loading all the time and never
ends.

if all the Role Center content in enterprise portal are coming up except the
Business Overview webpart and it keeps displaying loading progress image
for long time with no error msg in the event log, it may be because IE
security setting is preventing the webpart from asynchronously getting the
data. To resolve this issue add the EP site to the intranet site zone in
IE or disable IE Enhanced Security Configuration from Add / Remove programs
-> Add / Remove Widnows Components.

 (8)
Report Deployment is giving below error

"The following components have not been installed or are not configured
correctly.

AL.exe

Microsoft Domain-specific Langugage Tools..."



You need to install VS 2008 or the VS 2008 Shell.

If you install VS 2008 that should be good enough. If you want to install the
minimal component required, then You can get VS Shell at

VS Shell - http://www.microsoft.com/downloads/d...displaylang=en

Windows SDK (contains AL.exe) - http://www.microsoft.com/downloads/d...displaylang=en





(9) Report Deployment gives CLRBridge Loader error.



The workaround for this problem is to copy the AxReports.exe from C:\Program
Files\Microsoft Dynamics AX\50\Reporting Services to C:\Program Files\Microsoft
Dynamics AX\50\Client\Bin

And run it from C:\Program Files\Microsoft Dynamics AX\50\Client\Bin





(10) "Home" button (Role Center) in Ax Client gives "An error
has occurred. Contact your administrator for further assistance."

·   
Check if Role Center site is set correctly at Administration ->
Setup -> Internet -> Enterprise Portal -> Web Sites at the bottom
dropdown.

·   
Check if the Role Center page comes up correctly in Enterprise
Portal in browser. If any of the webparts are throwing error, the page will
still come up in Enterprise Portal , but in AxClient it will give error for the
entire page. If there are any errors in the webpart, then either fix it or
remove it so that the page will render without any error. Once the page appears
without any error, then check it in AxClient.

(11) "Home" button (Role Center) in Ax Client is not appearing

·   
Check if Enterprise Portal is installed .

·   
Check if Role Center site is set correctly at Administration ->
Setup -> Internet -> Enterprise Portal -> Web Sites at the bottom
dropdown.

·   
Chekc if default Role Center page is set corectly at
Adminsitration -> Setup -> User Profiels at the bottom dropdown

(12) EP installation fails with below error msg



"Entering function Remove40WPPackage

Entering function Is40WPPackageInstalled

Microsoft Dynamics AX 4.0 Web Part package axwebparts.cab installation status
False

Leaving function Is40WPPackageInstalled

Leaving function Remove40WPPackage

Leaving function RemoveOldWebPartPackage

Could not load file or assembly 'Microsoft.Dynamics.AX.Fim.PaymentService,
Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of
its dependencies. The system cannot find the file specified."



The aboce error msg is misleading. If you go further down in the setup log file
you will see the SysDevelopmentProxy error . So to resolve this issue, you just
to recompile this class in a machine with .NET BC like issue (1)



(13) Update in Manage
Deployments or Generate Proxy gives No .NET Business Connector Session found error.



Some times , users open AxClient by click on a configuration file ( for example
, Test.axc). The Ax Client opens with configuration file, but when you generate
proxy or Update in Manage deployment , it uses the configuration defined for
Local Client in Configuration Utility. It does not take the configuration file
which is used to open the Ax Client. This is a bug. So to resolve, make sure
the Local Client confoguiration is set correctly in Ax Configuration Utility



(14)
EP Deployment is successful but when I try to navigate the site, I get 404
error



When EP Site is created,
it activates number of EP features and one of them registers the site with Ax (
adds an entry in WebSite table) and sets the master page. If the user that is
set as the Primary administrator account for the site during Site Creation does
not have access to Ax, this fails but site creation does not return error.
After the site is created, it gives 404 error.



So if you get 404 error, make sure EP is deployed correctly and then when
creating EP site , specify a valid AX user account as the administrator of the
site.



(15)When I create EP
site , it creates immediately and when I navigate it displays a team site



At the time of EP Site creation, if AOS is down or if .NET BC
Configuration specified in Configuration Utility is incorrect, EP Site creation
does not report error but creates the site. Since it's not able to connect to
AOS, it appears as a team site. To resolve this problem, make sure the .NET BC
configuration in Ax Configuration Utility is correct and is pointing to a valid
running AOS.



(16) After I installed
EP, the IIS Web site on which I installed EP appears to be in stop mode.



When an
IIS Web site is not yet extended with SharePoint and when you run EP setup on
this site, EP Setup extends the IIS Web site using SharePoint object model.
SharePoint actually creates a new IIS Website using the same port and extends
it and installs EP on it. The old site is stopped because it uses the same
port. SharePoint does it this way, later you have some other system installed
on the old site, you could just change the port and restart it.



So this is not an error. This is the behavior of SharePoint installation. When
you install SharePoint on existing IIS Web site, it creates a new IIS web site.

(17) SQL Server reporting services sp2 is not installed, I have
SQL Server 2005 Reporting Services installed and  Service Pack 2 was  installed also and still getting the error message

The same problem with SQL
Server 2005 SP3, this fix our problem:

Setup does not recognize that
SQL Server 2005 Service Pack 2 is installed When
installing the reporting extensions, you may receive an error message that
states that you must install SQL Server 2005 Service Pack 2. If you have
installed SQL Server 2005 Service Pack 2 and receive this error message,
complete the following steps. 1. Open the registry  (regedit command )and find the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server key. 2. Right-click the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL Server key and choose New > Key. 3. Name the key Reporting Services. 4.
Right-click the Reporting Services key and choose New > String Value. 5. Name the string value Version. The Version string value will have a type of REG_SZ. 6. Double-click the Version string value and enter 9.00.3042.00 as the
value data. Click OK.

(18)Deployment failed unexpectedly with the message:Client found
response content type of 'text/html; charset=utf-8', but expected 'text/xml'.

Check if proxy account was
added to ax db users, and have access right on db. If it is not so add proxy
account to db users

(19) Deployment failedand when check Event viewer found the
following error

 Dynamics Adapter Logon failed.

Connection with the Application
Object Server could not be established.

Microsoft.Dynamics.BusinessConnectorNet.LogonFailedException

  
at Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO*
pBCProxyAccountInfo, String company, String language, String objectServer,
String configuration)

Solution:

1-   
Check
business connector configuration using client configuration utility

2-   
Change
the active client configuration utility to connect to the AOS as the
configuration of  business Connector

(20)“Deployment failed with the following exception:

System.Runtime.InteropServices.COMException (0x80040208)

  
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)

   at System.Management.ManagementObject.Initialize(Boolean
getObject)

   at System.Management.ManagementBaseObject.get_Properties()

   at System.Management.ManagementBaseObject.GetPropertyValue(String
propertyName)

   at
Microsoft.Dynamics.Framework.Deployment.Reports.SrsWmi.get_ConfigPath()

   at
Microsoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.DeployBusinessLogicAssemblies(IEnumerable`1
businessLogicAssemblies, DeploymentLogger logger)

   at
Microsoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.Deploy(IEnumerable`1
reportLibrariesToDeploy, IEnumerable`1 transitiveReferenceClosure,
IEnumerable`1 cultures, DeploymentLogger logger, Func`2
connectionStringModifier)”

Solution:

·        
You just need to
disable the UAC (User Account Control), or to run the Deployment tool with
right-click “Run as administrator”. As it says in the Dynamics
AX installation guide.

(21) Error during
processing of ‘AX_CompanyName’ report parameter.
(rsReportParameterProcessingError)





and furthermore in the Windows Application Event
log on the SQL Reporting server we get the following error logged: 



Dynamics Adapter LogonAs
failed. 



Microsoft.Dynamics.BusinessConnectorNet.NoIISRightsException 

at
Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO*
pBCProxyAccountInfo, String company, String language, String objectServer,
String configuration) 

at
Microsoft.Dynamics.BusinessConnectorNet.Axapta.LogonUsingBCProxyAccount(_SEC_WINNT_AUTH_IDENTITY_W*
pImpersonatedUserAccount, NetworkCredential bcProxyCredentials, String company,
String language, String objectServer, String configuration) 

at
Microsoft.Dynamics.BusinessConnectorNet.Axapta.LogonAs(String user, String
domain, NetworkCredential bcProxyCredentials, String company, String language,
String objectServer, String configuration) 

at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.LogonAs(String
user, String domain, NetworkCredential bcProxyCredentials, String company,
String language, String objectServer, String configuration) 







Solution :

After further troubleshooting we identified that the user was not
licensed for the "Enterprise Portal Framework" module. SQL Reporting
extensions and integration uses the .NET Business Connector (BC.NET) and BC.NET
requires Enterprise Portal Framework license, even if you are not using Role
Centers and Enterpise Portal. When the business connector connects to the AOS
server if it does not find the license key, it throws the NoIISRightsException error
message as seen in the event log.