Author |
Topic |
|
rinkurose@gmail.com
India
7 Posts |
Posted - 12/22/2009 : 04:52:39
|
hi after installation i m getting below error
1)HTTP Error 403.1 - Forbidden: Execute access is denied. Internet Information Services (IIS) 2) make sure nt user belong to olap role or olap admin local group analysis service srever....
|
|
admin
1637 Posts |
Posted - 12/22/2009 : 10:17:03
|
Please make sure that Windows user you used for XMLA access exists, has the right password and has access the XMLA physical folder (C:\Inetpub\wwwroot\ReportPortal). |
|
|
pcl_xl
11 Posts |
Posted - 12/29/2009 : 16:56:54
|
Hi... I also got the similar error message. I have also added user permission for XMLA and ReportPortal folder with the same user i used to create UDL (and the UDL is succeeded...), but still the error shows up... These are my installation steps: 1. Install Windows Server 2003 Enterprise (also adding IIS component) 2. Install SQL Server 2005 Enterprise 3. Copy database and deploy the OLAP cubes 4. Install MSXML and XMLASdk 5. Install ReportPortal 3 build 167 6. Adding permission for: Network Services, ASPNet Machine, login user, olap user, on ReportPortal and XMLA folder.
Is there any missing or false step...? Thanks. |
Edited by - pcl_xl on 12/29/2009 16:58:04 |
|
|
admin
1637 Posts |
Posted - 12/29/2009 : 20:01:18
|
pcl_xl,
Is your SSAS server installed on your web server?
The UDL file will use Windows authentication and the identity of the currently logged in user even if you enter the user id and password, unless you are using XMLA URL instead of the server name in the Data Source field. To test the UDL connection for another user you will need to login (or remotely connect) to your PC as that user.
Please put the domain name in front of the Windows user name (like domain1\user2) for the Anonymous User of the XMLA virtual directory.
You don’t need XMLA SDK when connecting to SSAS 2005. |
|
|
pcl_xl
11 Posts |
Posted - 12/31/2009 : 03:01:12
|
It's finally succeed although actually it was really confusing... What we've done was : - uninstall RP, including .Net framework 2.0 - Re-install all again with sequence: install IIS, install .Net framework 2.0, install RP then... tadaa it works... I fell relief but in the same time confuse about what the problem was... Maybe Marco or you have any idea about this case? Thanks a lot. Happy new year |
|
|
|
Topic |
|