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 more information, see this Tech Net article.
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.
<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:
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.