HOW TO CONFIGURE SQL SERVER REPORTING SERVICES IN ORDER

TO DEPLOY REPORTING SERVICES REPORTS FOR DYNAMICS GP

When you install SQL Server you have option to automatically deploy & configure SQL Server

Reporting Services (SSRS) with default settings. But in case if you already installed SQL but

didn’t installed SSRS, don’t worry you may configure these reports later on at any time you may

want. This post will elaborate step by step actions with screen shots, which you need to perform

while deploying SQL Server Reporting Services.

In order to start initial configuration of SSRS, or to change the configuration of an existing

installation, you need to start the Reporting Services Configuration Manager

Start menu >> All Programs >> Microsoft SQL Server 2008 R2 >> Configuration Tools >>

Reporting Services Configuration Manager;

The Configuration Manager works like a wizard, you proceed as you move down the tabs on the

left side of the window. Don’t forget to apply the changes you made on tab.

The first step is to set the Service Account. I am working on a test environment therefore I’m just

picking the Local System account but for a real environment (production server) you should use a

Domain User account which is created only to be used for executing SSRS service. After providing

the user details click the Apply button;

The Second step move to Web Service URL tab and provide virtual directory, by default it will

pick Report Server_ SQL instance name. You can use the same VD or can change it. On the same

tab you will configure web services site details by assigning it TCP port and IP addresses. Once

you have provided TCP port Reporting Services Configuration manager will generate report server

URL which you must note down because you will need the same URL while deploying SSRS

reports from within Dynamics GP.

After making necessary changes on the tab click apply to create virtual directory and reserve URL.

The results area will show confirmation and or error messages, if any issue are highlighted you

have to resolve them before proceeding.

Click the Database Tab to select, or create a new, database for use with reporting services;

Click on Change Database button to open the Report Server Database Configuration Wizard.

Select appropriate task of “create a new report server database” in order to create new database or

select “choose an existing report server database” if you want to change existing report server

database, and click next.

Enter the Server Name and connection details for the SQL server which will be used to connect

the SSRS database and click Next;

Provide database name and Temp database name, pick you language and select whether SSRS

should be in Native or SharePoint Integration Mode. For simplicity I have used default

configuration;

Enter the log on credentials. Again I have chosen Service Credentials but would recommend a

Domain User account for a production environment;

Click Next and you’ll be presented with a summary of your selections. Review them and click

Previous to make any changes or click Next to proceed;

The Wizard will verify the configuration and show confirmation. Click Next if configuration of

all components results in success otherwise click previous to make changes;

The Database tab of the main Reporting Services Configuration Manager window will be updated

with the database details. Review them and click Apply;

Navigate to the Report Manager URL tab and enter the Virtual Directory you want to use. Again

here for simplicity I left this at the default option;

After making necessary changes on the tab click apply to create virtual directory and reserve URL.

The results area will show confirmation and or error messages, if any issue are highlighted you

have to resolve them before proceeding.

Click E-mail Settings and configure the SMTP settings if you want to use Report Server e-mail

and click Apply;

On the Execution Account tab enter the details for accessing remote servers that store external

images (make sure you use a domain user account with minimal read-only permissions) and click

Apply;

Click onto the Encryption Keys tab. whenever I see a Backup button I feel the need to do so. In

the case of a test environment this it is not especially important, but on a production environment

I’d recommend you to take back up of Encryption Key in case of a need to recover or move the

SSRS database;

Enter a password which will be used to lock and unlock the Encryption Keys file (make sure you

pick a password that you will remember);

Once done, the Backup of the keys will be confirmed;

The final step is to scale out the Deployment should you wish;

When done click close and SSRS will be available for use within Microsoft Dynamics GP which

I’ll cover soon in the next post.