| Author |
 Topic  |
|
|
Vincent
USA
20 Posts |
 Posted - 06/16/2006 : 05:50:41
|
We're having problems connectiong to the olap reports over the internet. Do any other ports other than 80 have to be opened in the firewall? Everything works fine from within the firwall.
Thanks |
|
|
marco
Netherlands
588 Posts |
Posted - 06/16/2006 : 05:53:31
|
What is the ip address for testing.
Normal it should be working.
Marco |
 |
|
|
Vincent
USA
20 Posts |
Posted - 06/16/2006 : 08:11:44
|
I forgot to mention, the error we are getting when coming in from the internet is:
Errors xfaultcode->Client xfaultstring->Internal error xfaultsoap->The system cannot locate the resource specified.
Thanks |
|
|
|
Vincent
USA
20 Posts |
Posted - 06/16/2006 : 08:37:57
|
quote:
Originally posted by Marco Groeneveld
What is the ip address for testing.
Normal it should be working.
Marco
Thanks for the reply Marco. We are using integrated authentication so posting the url or ip here wouldn't be much help, I think. |
|
|
|
marco
Netherlands
588 Posts |
Posted - 06/16/2006 : 10:12:17
|
Is that not the problem ?
|
|
|
|
Vincent
USA
20 Posts |
Posted - 06/16/2006 : 12:21:12
|
| I don't think so. We are logging in to the network as domain users before getting these errors. |
|
|
|
admin
1645 Posts |
Posted - 06/16/2006 : 22:32:08
|
Only port 80 has to be open.
Please go to Admin > Connections and select your connection of "XMLA URL" type. What do you see? Does it begin with http:// ? If yes make sure that the server name matches the server name you use to access Report Portal in your browser.
|
|
|
|
Vincent
USA
20 Posts |
Posted - 06/20/2006 : 10:18:56
|
| It is http:// but the server name is not the same as the one we use to host the Report Portal. We have XMLA set up on the database server. This configuration works internally. Is it a requirement that it must be set up on the Report Portal web server to have it work externally? |
|
|
|
admin
1645 Posts |
Posted - 06/22/2006 : 20:45:34
|
| XMLA web service and ReportPortal virtual directories must reside on the same web serer. XMLA web service can still point to a Analysis Services on a separate server. |
|
|
|
RonC
1 Posts |
Posted - 06/23/2006 : 08:08:33
|
I work with Vin and have some more data to supply - maybe something will stand out.. First, let me state that everything works perfectly inside our own lan. The problem arises when connecting to the portal from the Internet. The portal site appears, but when we try to display an olap report, we get the error Vin mentioned above. Also, test results indicate that the browser is being instructed to connect to the cube via http. Here is the setup that we currently have:
bi.rfbd.org - Web server, W2K3, IIS6, ReportPortal, OLEDB for Analysis 9, OLAP virt directory set up per MS instructions. Pump pointed to AS 2005 for http cube access.
bidb.rfbd.org - SQL 2005 Standard, AS, permissions to data & cube set up for domain users.
Both servers are in the same domain, integrated authentication set up, RP set up to utilize pass-thru auth. Again, everything works perfectly inside firewall.
On the web server, RP is set up to use http://bi.rfbd.org/reportportal as the site url. Under connections, we use http://bi.rfbd.org/olap/msmdpump.dll to connect to data. Type is XMLA URL.
Inside the local network, I verified that the client web browser (IE6) is connecting to both the web server AND the AS server - I'm just not sure why. Outside the firewall, the error seems to occur because the browser tries to connect to the AS server and cannot. I'm pretty sure that it is not supposed to connect to anything but the web server.
Ron |
|
|
|
marco
Netherlands
588 Posts |
Posted - 06/23/2006 : 14:23:54
|
Hi,
What is the username and password to type in the popupbox. Or maybe you can have ReportPortal (not Integrated Security) So I can see the RP interface for testing internet.
Marco |
|
|
|
admin
1645 Posts |
Posted - 06/29/2006 : 05:49:49
|
There were two problems:
1) The report definitions are pointing to absolute path http://20sbutil1/olap/msmdpump.dll and not a relative one “/olap/msmdpump.dll”. Please go to Admin> Edit Report Schema and change:
<XmlaServer>http://20sbutil1/olap/msmdpump.dll</XmlaServer>
to:
<XmlaServer>/olap/msmdpump.dll</XmlaServer>
2) Pass-though authentication option was interfering with the XMLA provider. Whenever I was trying to create a new report I was getting:
Internal error: An unexpected error occurred (file '', line , function '').
After disabling “Pass-though authentication” option the problem went away.
|
|
|
| |
Topic |
|
Report Portal
Firewall changes
