| Author |
 Topic  |
|
|
rkrishnan
3 Posts |
 Posted - 07/06/2006 : 11:17:15
|
Hi Igor,
We just started using ReportPortal 2.1, Build 97.
When we create a new report and save it tag is getting also getting saved.
In our case it is:
http:\\server1\xmla\msxisapi.dll.
The Javascript when it loads this report interprets \xmla as a hexadecimal and errors out. If you remove the tag from report definition the report works fine.
Has it been fixed in new releases?
Ramani
|
|
|
admin
1645 Posts |
Posted - 07/07/2006 : 10:21:39
|
1) Please go to Admin > Connections > and change you "XMLA connection" from
http:\\server1\xmla\msxisapi.dll to
xmla/msxisapi.dll
2) Your report definitions would be updated to have xmla\msxisapi.dll
3) The newest build will let you search and replace the connection string in your reports by going to Admin > Edit Report Schema
|
 |
|
|
tranber
4 Posts |
Posted - 08/29/2006 : 03:28:36
|
Hi,
Using build 124, I cannot figure out how to setup properly my xmla connection.
In Admin > Connections , my XMLA connection is defined as:
http://localhost:8000/xmla/msmdpump.dll
(my IIS runs on port 8000)
However, when saving an Olap Report, the report schema will be saved as:
<XmlaServer>:8000/xmla/msmdpump.dll</XmlaServer>
(the begining of the url is truncated)
which results in an error when trying to open the report again:
'sXmlaServer not set'
Of course I can update the report schema and modify the <XmlaServer> to set the correct url, then the report will open.
But I think this behaviour is not correct, I should not have to manually edit the report schema... What do you think ? Could you provide a fix in the next build ?
Thanks !
|
|
|
|
admin
1645 Posts |
Posted - 08/30/2006 : 19:08:18
|
tranber,
You should not use the "http://localhost:8000/" part. Instead do the following:
1) Please go to Admin > Connections
2) Enter "xmla/msmdpump.dll" for the connection information
3) Click Update
The next build will handle things differently when there is a port number in XMLA URL.
|
|
|
|
tranber
4 Posts |
Posted - 08/31/2006 : 01:09:21
|
It's not working...
If I enter "xmla/msmdpump.dll" (without the "http://localhost:8000/" part) for the xmla connection information, I cannot connect anymore to my olap cube.
When trying to connect, the server connection string is defined as "http://localhost/xmla/msmdpump.dll" (missing the port number), and an error is raised: "Errors xfaultcode->Server xfaultstring->Unknown server error xfaultsoap->".
So I obviously need to set the port number somewhere. That's why I have added the "http://server:port" in the xmla connection information. However this part is not completely saved in the report schema, which results in an error when opening the report...
So no work-around for this problem ? (except manually editing the report schema).
I hope there will be a fix soon.
Thanks for your answer. |
Edited by - tranber on 08/31/2006 01:13:37 |
|
|
|
admin
1645 Posts |
Posted - 08/31/2006 : 19:32:59
|
Please try this work around until the next build is out:
Go to Admin > Settings > Site Settings > Set “Site URL” to http://<YourServerName>/ReportPortal/
|
|
|
|
tranber
4 Posts |
Posted - 09/01/2006 : 01:04:18
|
I have already this setting :
Site URL : http://localhost:8000/ReportPortal.
It does not change anything to the xmla connection...
Anyway, I'll wait for the next build.
Thanks again. |
|
|
|
admin
1645 Posts |
Posted - 09/01/2006 : 05:35:14
|
Please try this:
Go to Admin > Settings > Site Settings > Set “Site URL” to http://<YourIP>/ReportPortal/ |
|
|
|
tranber
4 Posts |
Posted - 09/01/2006 : 06:03:07
|
I'm not sure I was clear about my problem.
My IIS is running on port 8000, so I definitely need to set this port number in the xmla connection.
I do not think changing the site url will have any effect about that.
When I set the complete xmla connection (http://localhost:8000/xmla/msmdpump.dll), the connection is working perfectly, the only problem is that it is not saved correctly in the report schema.
When manually modifying the report schema, I can work around the problem.
I'll wait for the next build as you told me it will handle things differently... perphaps my problem will be fixed !
Thanks. |
|
|
| |
Topic |
|
Report Portal
Hexadecimal error when opening saved report.
