| Author |
 Topic  |
|
|
spadmanabhan
USA
9 Posts |
 Posted - 03/28/2005 : 15:19:56
|
For some IE browsers, the same portal is giving the following error:
"Permission denied" on http://... /reportportal/olap/MdxConnect.asp.
line 140 of that file when the user attempts to connect to the cubes.
The weird thing is it doesnt happen to all. But specific machines trying to access the site i setup on a different server. Is there any specific client browser requirement (apart from 5.0 or above which anyone accessing my server has) that I took care of (by virtue of playing with portal installs and all on my box) but not the other users ?
Any input willbe really appreciated. |
|
|
admin
1646 Posts |
|
|
spadmanabhan
USA
9 Posts |
Posted - 03/29/2005 : 15:15:17
|
| yep. Just that when it works for me, why not for my neighbour trying to access the same portal is the issue. Im not sure whats peculiar to his browser that permission is denied when it works for me. Not using local host. |
 |
|
|
admin
1646 Posts |
Posted - 03/29/2005 : 20:44:34
|
| Your neighbor has the problem because the server name in the browser and the admin page do not match. It works fine for you because you might have the sever added to user trusted server list. |
|
|
|
scaceres
Argentina
45 Posts |
Posted - 05/03/2005 : 08:42:01
|
I had the same problem, but not in my office's network.
At my office, the settings for OLAP and XMLA points to the same server, and the URL points to localhost. The error does not take place here. But... if I point the URL to the IIS SERVER, it does happen (in another network), maybe it's because the IIS SERVER and the OLAP/XMLA server are different.
BIServices S.A. |
|
|
|
spadmanabhan
USA
9 Posts |
Posted - 05/12/2005 : 11:18:33
|
Some lessons learnt (if this helps rest):
It depends on how you integrate portal with your website.
For example: security settings matter. You may need
HTTP and HTTPS enabled for XMLA. Also note, i found it better
to remove XMLA and do a clean install of it instead of using
the repair option there. In my experience, this was cleaner.
Also, use a common service account for your webserver and Analysis
server.
Ensure that datasources.xml file has the right path to msxisapi.dll and the datasource name.
You may need "Access to data sources across domains" enabled on
your browser.
I have tried several rounds since i have a webfarm talking to
clustered sql dbs. Now, it works uniformly everywhere, finally. :-) |
|
|
|
admin
1646 Posts |
Posted - 05/18/2005 : 10:37:55
|
| The latest build 35 has fixes to this problem. Now when you don’t specify the “XML for Analysis Server URL” it will use the URL for the server specified in the browser. |
|
|
| |
Topic |
|
Report Portal
Permission denied on some IE's
