Report Portal

1. Open the Windows Explorer, right click on C:\Inetpub\wwwroot\ReportPortal folder, select on the security tab, give ASPNET and Anonymous (IUSR_<Machine Name>) users full control to the folder, click on the advanced button to replace permission entries on child objects.
2. If previous step did not work, open IIS admin and change the Anonymous user for ReportPortal virtual directory to some other user that has access to the ReportPortal folder.
3. If previous step did not work, create a copy of the folder (C:\Inetpub\wwwroot\ReportPortal) called ReportPortal2 in C:\Inetpub\wwwroot. Create and point new ReportPortal2 virtual directory to the folder.

To make the error visible in the Internet Explorer go to: Internet Explorer > Tools.. > Internet Options > Advanced Tab > Uncheck "Show Friendly Error Messages".

Please enable "IIS 6 management Capability" for your IIS.

1. Click Start, click All Programs, click Administrative Tools, and then click Server Manager.
2. Right-click Roles, and then click Add Roles.
3. Click Next to get to the Server Role Screen.
4. Mark the checkbox for the following roles, and then click Next.
   • Application Server
   • File Services
5. Click Next to get to the Roles Services for the Application Server.
6. Select the checkbox next to Web Server (IIS) Support. When the Add Roles Wizard box comes up, click Add Required Role Services, and then click Next.
7. Click Next to get to the Web Server Role Services, keep the existing checkboxes that are marked and mark the checkbox next to IIS 6 Management Compatibility, and then click Next.
8. Click Next to get to the File Services Role Services, mark the checkbox next to Indexing Service , and then click Next.
9. Click Install

Please enable "IIS 6 management Capability". For more information, see this Tech Net article.

To turn off UAC:

1. Click Start, and then click Control Panel.
2. In Control Panel, click User Accounts.
3. In the User Accounts window, click User Accounts.
4. In the User Accounts tasks window, click Turn User Account Control on or off.
5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.
7. Click Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window.

1. Setup XMLA manually using instructions in this article or this article. Make sure that XMLA virtual directory has a *.dll script map pointing to msmdpump.dll file.
2. During the installation, for "SQL Server Analysis Services" selection page pick: "Not Used / Already Configured".
3. After the installation, register XMLA with ReportPortal: go to Admin > Connections > (Type = XMLA URL) and put xmla2005/msmdpump.dll for the connection string.

1. If using Windows Server 2003+, you will need to enable ISAPI extensions for XML/A to work.
2. Login to your web server with the user id you used for Anonymous user. Create a UDL file (like test.udl) and point it to SSAS 2005+ server using Microsoft OLE DB Provider for Analysis Services
3. Type the URL for msmdpump.dll in you browser. Make the error visible in the Internet Explorer go to: Internet Explorer > Tools.. > Internet Options > Advanced Tab > Uncheck "Show Friendly Error Messages".
4. Please check your windows event log.
5. Try using the SDK sample application to make sure that XMLA SDK is properly installed.
6. Here is Microsoft's white paper that could be useful.

XMLA SDK 1.1 requires MSXML 4.0. It can be downloaded by clicking here. Try using the SDK sample application to make sure that XMLA SDK is properly installed. You can also test the connection with this page MDX.htm. Please save this page to desktop before running it. Sometime it is necessary to restart the IIS service or the PC for the XML/A web service to work.

You might need to explicitly enable ISAPI extensions for XML/A to work.

Enabling the HTTP compression on the web server can significantly improve performance. This article explains how to enable HTTP compression. Make sure that HTTP compression does not have caching enabled. Use MetaEdit tool to set parameter "max-age"property should be set to zero.

Open Handler Mappings and look for *.ASPX. If you cannot find it your server does not have ASP.NET configured. Take these steps:

1. For Windows Server 2012, run the following command from an administrative command prompt:
   
   dism /online /enable-feature /featurename:IIS-ASPNET45
   
   
2. For Windows Server 2008 and below, run the following the command line depending of .Net version you have installed:
   
   %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
   %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

Please download and run this script. It will remove ReportPortal from your registry and from the list.

You can also manually remove the product from Windows Registry by searching for "ReportPortal" under HKEY_CLASSES_ROOT\Installer\Products. (It is recommended that you backup Windows Registry before updating it.) The ReportPortal folder under web root folder (C:\Inetpub\wwwroot) will also have to be deleted.

Yes, this can accomplished in two steps:

1. Uninstall the Evaluation version of Report Portal. Choose "NO" when asked to delete the database.
2. Install Report Portal by double clicking on ReportPortalSetup.msi file. Choose the same database name used by the Evaluation version.

Download backup file FoodMart2000.zip. Open "SQL Server 2005 Management Studio. Right click on "Databases" and choose "Restore..."

It looks like your Reporting Services "ReportServer" virtual directory is using Windows Integrated Authentication. XMLA web service is unable to handle a Windows Authentication. After being authenticated by Reporting Services virtual directory, your browser challenges XMLA service and the service breaks. Please enable basic anonymous/basic authentication instead for "ReportServer" virtual directory.

You will need to configure the amount of memory used by XMLA. Please open datasources.xml (C:\Program Files\Microsoft XML For Analysis SDK\Config\datasources.xml) file in Notepad. Change text inside DataSourceInfo XML tag like so:

<DataSourceInfo> Provider=MSOLAP.2;Data Source=local; Client Cache Size=150; Execution Location=3; Default Isolation Mode=1; Large Level Threshold=100; </DataSourceInfo>

Here are the connection properties to change:

1. Client Cache Size=150; - try to make smaller
2. Execution Location=3; 3 - Queries are executed on the server.
3. Default Isolation Mode=1;
4. Large Level Threshold=100; - try to make smaller

Please open Web.config and uncomment this section:
<httpModules>
<add name="Session" type="System.Web.SessionState.SessionStateModule"/>
</httpModules>

When Reporting Services is given an MDX statement it executes it entirely and coverts it into intermediate RDL format. When a user tries to drill down he pulls additional data from the RDL "cache". Report Portal, on the other hand, accesses data only as needed. When dimensions are large Reporting Services will take very long time to execute an MDX statement.

Reporting Services does not provide for slicing, drillthrough, dimension member search, calculated members, member properties and other standard OLAP features.

Office XP BI Portal requires OWC (Office Web Components) for Office XP installed on each client computer. OWC requires also Microsoft Pivot Table Services be installed on the client computer.

Report Portal does not require any client side installation or configuration. The only client requirement is Interment Explorer 5.0 or higher. Report Portal can also optionally use Office Web Components for Office 2000, which is currently more popular and is covered by both Office 2000 and Office XP licensing.

Report Portal also supports features, that Office XP BI Portal does not, such as: member properties, data mining, snapshot and relational support.