Configure the new Reporting Services instance

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Complete the following procedures to configure the new instance of Microsoft SQL Server Reporting Services. This topic assumes that the new instance of Reporting Services meets the version requirements that are listed in Install multiple instances of Reporting Services on the same computer (for use with Microsoft Dynamics AX).

Configure the Reporting Services instance by using the Reporting Services Configuration Manager tool

Use the following procedure to configure the new Reporting Services instance.

1. Click Start > All Programs > Microsoft SQL Server > Configuration Tools > Reporting Services Configuration Manager to open Reporting Services Configuration Manager.

2. Connect to the new Reporting Services instance.

3. Configure the options that are described in the following table. For detailed information about each option, see the SQL Server documentation.

   Click this option…	To do this…
   [ServerName]\[InstanceName]	Verify that the Reporting Services instance is running. If it is not running, click Start.
   Service Account	Enter the name and password of the account that is used as the Business Connector proxy. Note To view the account that is used as the Business Connector proxy, open Microsoft Dynamics AX and then click System administration > Setup > System > System service accounts.
   Web Service URL	Create a virtual directory for the Reporting Services web service. By default, the virtual directory is named ReportServer, and the URL is http://[SSRSServerName]:80/ReportServer_[SSRSInstanceName].
   Database	Create a database for the Reporting Services instance.
   Report Manager URL	If Reporting Services is running in native mode, create a virtual directory for Report Manager. Report Manager is the website that reports are published to. By default, the virtual directory is named Reports, and the URL is http://[SSRSServerName]:80/Reports_[SSRSInstanceName]. If Reporting Services is running in SharePoint integrated mode, skip this page. Report Manager is not used when Reporting Services is running in SharePoint integrated mode.
   E-mail Settings	This option is not required. For more information, see the SQL Server documentation.
   Execution Account	Enter the name and password of the account that is used as the Business Connector proxy.
   Encryption Keys	This option is not required. For more information, see the SQL Server documentation.
   Scale-out Deployment	This option is not required. For more information, see the SQL Server documentation.

4. Click Exit to close Reporting Services Configuration Manager.

Configure the Reporting Services instance for local administration

To administer an instance of the report server locally, you must complete additional configuration steps when you deploy Reporting Services on Windows Server 2008. Windows Server 2008 limits the overuse of elevated permissions by removing administrator permissions when you access applications. If you are a member of the local Administrators group, you run most applications as if you are using the Standard User account because the operating system removes permissions.

Although this practice improves the overall security of your system, it prevents you from using the predefined, built-in role assignments that Reporting Services creates for local administrators. However, by completing additional configuration steps, you can manage the report server's content and operations by using standard user permissions. For instructions, see How to: Configure a Report Server for Local Administration on Windows Vista and Windows Server 2008 on TechNet.

After you have configured the Reporting Services instance for local administration, verify that you can access the sites that are listed in the following table.