Management Reporter 2012 server installation and configuration

Run the downloaded ManagementReporter2012-en-us.exe and select a location for the installation files to be extracted to;

Once extraction is complete, hit OK;

In the extract location you’ll see a collection of files and a pkg folder. Double click the Setup.exe to start the installation process and select Install Management Reporter Server;

Accept the terms of the License Agreement after reading it;

Select or confirm the destination folder;

Click Install to confirm the installation;

Management Reporter will then install before confirming a successful installation;

At this stage you can choose to start the Configuration Console of Management Reporter when you click finish. You can also proceed further without selection of check box and configure it afterwards.

Configuring Management Reporter 2012:

The configuration is done using the Configuration Console which is installed as part of the server installation, so in my case it is on the Reporting Server (RPT1).

To start the Configuration Console go to Start >> All Programs >> Microsoft Dynamics >> Management Reporter 2012 >> Configuration Console. Once started it will detect that configuration has not yet been done and present you with the Custom Configuration wizard;

By default both Microsoft Reporter Application Service and Management Reporter Process Service will be checked, and as I am dealing with Management Reporter integrated with Dynamics GP I also need to select Add Microsoft Dynamics GP;

If any prerequisites are missing, such as the Access Database Engine, you will be shown them and given the opportunity to install them before proceeding;

Next you need to configure the Service account. For a production environment this should always be a custom account with restricted privileges and a password that never expires (if you type in the username, ensure the Domain element is in all caps; e.g. DOMAIN\DynamicsGPuser) and supply the password;

Next, the database configuration needs to be completed. Enter the name of the SQL Server that the Management Reporter database will live on (in my case RPT1) and select the authentication method, either accept the default ManagementReporter database name or supply your own, enter a master key for encrypting sensitive information and select your Management Reporter administrator user (this will default to the logged in user);

Configure the port which should be used for the Application Service (4712 is the default (this is the same port as Management Reporter 2).

You also need to define the Dynamics GP connection information (the eagle eyed among you will spot the Database server has been spcified as GPLIVE and not SQL1; this is because I have created a CNAME alias for the GP Server so I can move the installation in future to a new server without having to reset all passwords) and select the system Database;

Check the configuration summary and then click Configure to proceed;

Once configure is complete this will be confirmed or any errors reported;

Once you click close you’ll be returned to the Management Reporter Configuration Console where you can see the status of Management Reporter;

To add companies from Microsoft Dynamics GP, select Management Reporter Services >> ERP Integrations >> SERVER (DYNAMICS) in the Navigation Pane and click the Import button on the Server (DYNAMICS) detail pane;

You will be prompted to enter the GP credentials (in this case I used the sa user);

You’ll be presented a list of companies which can be imported, and can select companies which have already been imported or those which should be skipped. When you’re ready click the Import Companies button located at the bottom right of the window;

Management Reporter 2012 Configuration Console will confirm that the selected companies have been imported;

And that is the final part of the Management Reporter 2012 server configuration process. Next up is the client installation process…

Announcing Compatibility Certification of SQL Server 2012 and SQL Server 2012 SP1 with Dynamics AX 2009 SP1

Dynamics AX In-Market Engineering Team is proud to announce the following compatibility of released version of Dynamics AX with SQL Server 2012 and SQL Server 2012 SP1.
Required Hotfix with KB Number: 2836535

Microsoft Product	Dynamics AX Versions
SQL Server 2012 and SQL Server 2012 SP1	Dynamics AX 2009 SP1

The System requirements of Dynamics AX 2009 SP1 have been updated. 

Reference : https://community.dynamics.com/ax/b/dynamicsaxsustainedengineering/archive/2013/04/18/announcing-compatibility-certification-of-sql-server-2012-and-sql-server-2012-sp1-with-dynamics-ax-2009-sp1.aspx#.UX7LR8pYWSo 

Duplicate company in AX 2012

The Duplicate Company function in AX 2009 is deprecated in AX 2012, and the reason is "The organization model represents a paradigm shift in Microsoft Dynamics AX 2012", said by Microsoft. To copy a company in AX 2012 for demo or test, now you'll have to

1. create a definition group
2. export the def group from old company
3. import the def group to the new company

When you create def group, go to Include table group tab and make sure you've selected the tables you want to bring into your new company. When you import, go to the Advanced tab and select/deselect the Include shared tables checkbox as it's needed. Microsoft has a very detailed tutorial on this process:

Use Microsoft Dynamics AX to transfer (export and import) data [AX 2012]

Debugging Microsoft Dynamics AX 2009 SSRS reports with Microsoft Visual Studio 2008

While Microsoft SQL Server Reporting Services (SSRS) reports allowed in in Dynamics AX 4.0 a user to create Ad'hoc reports that were only based on the data stored in the Dynamics AX database, in Dynamics AX 2009 Production reports allow also the execution of Business Logic. The Business Logic can either be X++ code in the AOT or C# code directly in the SSRS report.

This also brings up the question how the C# code could be debugged when necessary. You can use the Visual Studio 2008 integrated debugger however you need to follow certain steps otherwise your breakpoints will not be hit.

You need a PC where the following components are installed:

• Microsoft Dynamics AX 2009 Client,
• Microsoft Dynamics AX 2009 Reporting Tools,
• Microsoft SQL Server 2005 or 2008 Reporting Services,
• Microsoft Dynamics AX 2009 Reporting Extensions, and
• Microsoft Visual Studio 2008

Note:In the following example we use a report that is based on Microsoft SQL Server Analysis Services (SSAS) data. Therefore the Dynamics AX default cubes need to exist, however SSAS does not necessarily need to be locally installed.

In the following steps I will explain how you can debug the standard SSRS / SSAS reportCust.CashInflowvsCashOutflow for example:

1. Start the Dynamics AX Client, open the AOT window and go to AOT\Report Libraries
    
2. Click with the right Mouse button at the Cust report library and select Edit in Visual Studio from the context menu
    
3. Wait until the Visual Studio IDE has launched completely
    
4. Make sure the active configuration of the Solution is set to Debug (to check the Active configuration go toBuild - Configuration Manager...)
    
5. Rebuild the whole Solution by selecting Build - Build Solution
    
6. Deploy the Solution to your Microsoft SQL Server Reporting Services by selecting Build - Deploy Solution
   (Note: It is important to deploy the Solution from within Visual Studio even if the SSRS reports were already deployed and did not change since then!)
    
7. Open the report CashInflowvsCashOutflow from the Visual Studio Solution Explorer window
    
8. In the Report Explorer window expand the node Data Methods and double click at GetDefaultCompany
    
9. Place a breakpoint (e. g. by pressing the [F9] key) at any line of code
    
10. Start the Internet Explorer and navigate to your Microsoft SQL Server Reporting Services Report Managerpage (e. g. http://localhost/reports)
     
11. Click at the Dynamics folder in the Report Manager page
     
12. Go back to Visual Studio and select Tools - Attach to Process from the menu
     
13. Make sure the options Show processes from all users and Show processes in all sessions are enabled(checked)
     
14. The next step is different based on the version of Microsoft SQL Server Reporting Services:
    1. If you are using Microsoft SQL Server 2008 Reporting Services:
       In the list of processes located the process ReportingServicesService.exe and attach to this process
        
    2. If you are using Microsoft SQL Server 2005 Reporting Services:
       In the list of processes located the process w3wp.exe and attach to this process (If you have more than one w3wp.exe process listed, see the appendix at the end how to determine the correct process)
        
15. Go back to the Report Manager page in Internet Explorer and execute the reportCust.CashInflowvsCashOutflow.FullPage
     
16. The breakpoint will be hit by the Visual Studio integrated debugger
     

Some more hints:

• On Windows Vista and Windows Server 2008 make sure you run Visual Studio with elevated privileges (Run as Administrator)
   
• Once the debugger is attached you can check what modules are loaded in the Visual Studio integrated debugger by selecting Debug - Windows - Modules from the menu (The Assembly the C# code is compiled to is Cust.BusinessLogic.DLL)
   

How can I determine the correct w3wp.exe process to attach to?

The Microsoft SQL Server Reporting Services 2005 are hosted in the Microsoft Windows Server Internet Information Services (IIS). Therefore the process to attach to for debugging is the IIS Worker Process (w3wp.exe). As IIS is starting at least one Worker Process per Application Pool, more than one w3wp.exe processes are usually running on a Windows Server.

In order to see what Worker Process is serving what IIS Application Pool tools exists:

• On Windows Server 2003 (IIS 6.0) run: iisapp.vbs
• On Windows Server 2008 (IIS 7.0) run: appcmd.exe list wp

The output of the tools looks as follows:

C:\Windows\system32>iisapp.vbs
W3WP.exe PID: 2056 AppPoolId: AxReportServer
W3WP.exe PID: 5092 AppPoolId: EP - 39014

C:\Windows\system32\inetsrv>appcmd.exe list wp
WP "6916" (applicationPool: SharePoint Central Administration v3)
WP "1356" (applicationPool: AxReportServer)

Once identified the correct w3wp.exe process (based on the Application Pool) use the PID (Process ID) to attach to the correct w3wp.exe process.

--author:	Alexander Lachner
--editor:	Alexander Lachner
--date:	16/06/2009

Source : http://blogs.msdn.com/b/emeadaxsupport/archive/2009/07/16/debugging-the-business-logic-in-microsoft-dynamics-ax-2009-ssrs-reports-with-microsoft-visual-studio-2008.aspx

Reproting Extension installation process tips and triks

Hi,

While installation of Reporting Extension of AX 2009 we are facing lots of Errors and Warning, so this post is for some tips and tricks regarding  installation of Reporting Extension as much as possible without of Errors and Warning.

1. Install all the prerequisite for reporting extensions.
2. Configure the Reporting services with the use of Reporting services configuration manager from configuration tool of SQL server 2008
3. Check the URL both reporting service url and reporting manager url from configuration services for accessing and proper running.
4. In the Dynamics AX 2009 >> Administration >> setup>> Reporting services .. Update the information regarding reporting services and create folder named DynamicsAX and click on the create button to create Datasource on the reporting manager URL.
5. Install reporting Extensions from AX 2009 setup
6. reset the IIS
7. Deploying  reports : Please do this activity with the login of BCPROXY user only.
Run report deployment tool from Dynamics AX 2009
8. Do not deploy all the reports at a time.
9 Deploy the reports one by one or select the some bunch of reports ( like all reports which start from letter B,C,D...or else )
10. Please do not deploy or select any reports which start with letter "S".
11. In Between this you might get warning with HTML code and reports failed to deploy at this time the general solution is to restart the Reporting services from Services.msc
12. And at the end you can deploy the all remaining reports.


----
Kishor

Report Deployment Errors in AX 2009

While deployment of reports (Reporting Extensions) in Ax 2009 the following error has been generated. 

Error:
Unable to connect to http://server:port/ReportServer/ReportService2005.asmx as specified in the config file for the report server at DriveName:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\RSReportServer.config. 

If this url is not correct please update the config file, otherwise make sure the report server is configured correctly.

Solution:

Go to Encryption Keys >> Delete Encrypted Content >> Delete 

------