You are not logged in.

Xmla Ssas

Dear visitor, welcome to Palo Community Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

  • 1
  • 2

gilbert

Intermediate

  • "gilbert" started this thread

Posts: 7

Date of registration: Mar 10th 2008

  • Send private message

1

Monday, March 10th 2008, 10:11am

Xmla Ssas

Hy All,

I use Palo web client. I tried to connect a ssas server after modifying
the parameters in the palo.properties file.

The connection parameters are as follow :
server3.dispname=MS AS 2005
server3.url=localhost
server3.service=olap/msmdpump.dll
server3.login=PaloWeb
server3.password=admin
server3.provider=xmla

A virtual dir is created mapped in IIS for the msmdpump.dll file.

I get tis message at connection
Application may behave incorrectly.
Call fail on server.
Reason: The call failed on the server; see server log for details

The localhost log file on TomaCat server contains the following
(the user 'PaloWeb' we use is created on the sql server we tried also creating this user as windows user. In the connection parameters we also tried with and without the user password but still have the same error)


10 mars 2008 09:59:34 org.apache.catalina.core.ApplicationContext log
GRAVE: Exception while dispatching incoming RPC call
com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract com.tensegrity.palowebviewer.modules.paloclient.client.XFolder com.tensegrity.palowebviewer.modules.engine.client.IEngineService.loadFavoriteViews()' threw an unexpected exception: com.tensegrity.palojava.PaloException: Could not login to xmla server 'localhost' as user 'PaloWeb'!!
at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:361)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:547)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:265)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:187)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:634)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Unknown Source)
Caused by: com.tensegrity.palojava.PaloException: Could not login to xmla server 'localhost' as user 'PaloWeb'!!
at com.tensegrity.palo.xmla.XMLAConnection.getServerInfo(XMLAConnection.java:532)
at com.tensegrity.palo.xmla.XMLAServer.getInfo(XMLAServer.java:27)
at org.palo.api.impl.ConnectionImpl.<init>(ConnectionImpl.java:75)
at org.palo.api.impl.ConnectionFactoryImpl.newConnection(ConnectionFactoryImpl.java:111)
at com.tensegrity.palowebviewer.server.PaloConnectionFactory.createConnection(PaloConnectionFactory.java:30)
at com.tensegrity.palowebviewer.server.ServerConnectionPool.openConnection(ServerConnectionPool.java:51)
at com.tensegrity.palowebviewer.server.ServerConnectionPool.tryGetConnection(ServerConnectionPool.java:73)
at com.tensegrity.palowebviewer.server.ServerConnectionPool.getConnection(ServerConnectionPool.java:62)
at com.tensegrity.palowebviewer.server.ServerConnectionPool.<init>(ServerConnectionPool.java:38)
at com.tensegrity.palowebviewer.server.GlobalConnectionPool.getConnection(GlobalConnectionPool.java:70)
at com.tensegrity.palowebviewer.server.GlobalConnectionPool.getConnection(GlobalConnectionPool.java:59)
at com.tensegrity.palowebviewer.modules.engine.server.EngineLogic.loadFavoriteViews(EngineLogic.java:294)
at com.tensegrity.palowebviewer.modules.engine.server.EngineService.loadFavoriteViews(EngineService.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:528)
... 16 more


Thanks for any Help

philipp

Professional

Posts: 31

Date of registration: Jul 16th 2007

Location: Düren, Germany

Occupation: Software Developer

  • Send private message

2

Monday, March 10th 2008, 10:48am

RE: Xmla Ssas

Hi,

your connection settings seem to be ok.
Have you tried accessing SSAS via a browser (firefox or ie)?
Try to visit "http://localhost/olap/msmdpump.dll" and see what happens. If it says that the "post syntax is invalid", it means you can connect to the site.

If that's not the case: Did you set up SSAS for use with XMLA? To do that, you will have to add a role to the SSAS. The users that will have to have priviliges in that role are:

IUSR_<your computer name>
SYSTEM (for windows XP, it's usually NT_AUTHORITY/System)
<your user name>

after you added that role, restart the IIS and try again.

Please tell me if that helped.
Good luck,
Philipp

gilbert

Intermediate

  • "gilbert" started this thread

Posts: 7

Date of registration: Mar 10th 2008

  • Send private message

3

Monday, March 10th 2008, 11:15am

RE: Xmla Ssas

Hi Philip,

the access to the url http://localhost/olap/msmdpump.dll
produces an 500 http error.

I created a role in SSAS and added the users :
IUSR_<Machine name>
SYSTEM
palo_web (a user i created)
but it stills not connection. message
Application may behave incorrectly.
Call fail on server.
Reason: The call failed on the server; see server log for details

philipp

Professional

Posts: 31

Date of registration: Jul 16th 2007

Location: Düren, Germany

Occupation: Software Developer

  • Send private message

4

Monday, March 10th 2008, 11:33am

RE: Xmla Ssas

Hi,

hmmm... The HTML 500 error seems to indicate that there's a problem in the configuration of your IIS.

So, first of all, are you running Vista or XP? (Or a different version of Windows?)
Which version of IIS are you running?

Can you verify that you have created the connection pool (or virtual folders) as described here.
Especially, can you verify that your user (palo_web) has read, execute, and list rights for the application pool in which you run your msmdpump.dll.

Also (just to make sure), please check that you are using the correct port (although an html 400 error would be expected if you used the wrong port).

Hope that helps,
Philipp

This post has been edited 1 times, last edit by "philipp" (Mar 10th 2008, 11:34am)

gilbert

Intermediate

  • "gilbert" started this thread

Posts: 7

Date of registration: Mar 10th 2008

  • Send private message

5

Monday, March 10th 2008, 11:45am

RE: Xmla Ssas

Hi,

i am on XP. I created the virtual dir as per the link you gave me.
now if i tray to browse the directory througnt IIS, i get a 403 error
I get it also with ie.

philipp

Professional

Posts: 31

Date of registration: Jul 16th 2007

Location: Düren, Germany

Occupation: Software Developer

  • Send private message

6

Monday, March 10th 2008, 11:57am

RE: Xmla Ssas

Ok, then what's the name of your virtual directory?
And what are the contents under that directory?

If your virtual directory is called "olap", _and_ the path to which your virtual directory points contains the "mdmdpump.dll", it _should_ work...

Note that the virtual directory you created matches the name of your link. Also, if you do not have the msmdpump.dll (directly) under the virtual directory, it won't work.

So, if you have for example:

C:\MyOlapDirectory\MyMainDirectory\msmdpump.dll

and you named your virtual directory "olaptest" and made it point to c:\MyOlapDirectory, your connection string would be:

http://localhost/olaptest/MyMainDirectory/msmdpump.dll

But you said you are getting a 400 error now, instead of a 500 error: What is it that you changed?

Also: Did you restart the IIS (or if in doubt: Restart your computer...)?

We'll get this to work! :)
Philipp

gilbert

Intermediate

  • "gilbert" started this thread

Posts: 7

Date of registration: Mar 10th 2008

  • Send private message

7

Monday, March 10th 2008, 12:03pm

RE: Xmla Ssas

I created a dir under inetpub named _olap
(C:\Inetpub\wwwroot\_Olap) and copied to it the contains of
the C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\isapi

The vitual dir is namped olap and points to the C:\Inetpub\wwwroot\_Olap
now i get the error 403 when browsing then url
http://localhost/olap (ie connects but access seems to be refused)

philipp

Professional

Posts: 31

Date of registration: Jul 16th 2007

Location: Düren, Germany

Occupation: Software Developer

  • Send private message

8

Monday, March 10th 2008, 12:09pm

Browsing to http://localhost/olap _should_ fail. Did you try

http://localhost/olap/msmdpump.dll

This should give you an xml text with a warning message that says something to the effect of "the get method is not supported" (which is entirely ok).

Did you try once again to connect with WPalo? What happens?

gilbert

Intermediate

  • "gilbert" started this thread

Posts: 7

Date of registration: Mar 10th 2008

  • Send private message

9

Monday, March 10th 2008, 12:14pm

Connecting to http://localhost/olap/msmdpump.dll produces error 500.
Palo cannot connect, i get the same message as before.

Marco Groeneveld

Sage

Posts: 138

Date of registration: Oct 27th 2005

  • Send private message

10

Monday, March 10th 2008, 12:17pm

Hi,

Visit ReportPortal.com and there you will find some answers on XMLA errors etc and whitepapers how to connect to XMLA.

Best regards,
Marco

philipp

Professional

Posts: 31

Date of registration: Jul 16th 2007

Location: Düren, Germany

Occupation: Software Developer

  • Send private message

11

Monday, March 10th 2008, 12:19pm

[Answered by mail. Maybe we can fix the problem through remote access.]

gilbert

Intermediate

  • "gilbert" started this thread

Posts: 7

Date of registration: Mar 10th 2008

  • Send private message

12

Monday, March 10th 2008, 12:40pm

I get another error as i switched off the option of friendly http messages deisplay from IE.
Browsing to

shows the following code
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <soap:Body>
- <soap:Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>XMLAnalysisError.0xc10e0002</faultcode>
<faultstring>Analyseur : La syntaxe pour « GET » est incorrecte.</faultstring>
- <detail>
<Error ErrorCode="3238920194" Description="Analyseur : La syntaxe pour « GET » est incorrecte." Source="Unknown" HelpFile="" />
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>

http://localhost/olap/msmdpump.dll

(The message is in french. it says GET syntaxe is incorrect)

gilbert

Intermediate

  • "gilbert" started this thread

Posts: 7

Date of registration: Mar 10th 2008

  • Send private message

13

Monday, March 10th 2008, 12:45pm

Palo web does connect. The server path was wrong because the full url was specified. Only olap/msmdpump.dll should be specified. Thanks for the help

amu

Trainee

Posts: 5

Date of registration: Apr 2nd 2008

  • Send private message

14

Wednesday, April 2nd 2008, 7:30pm

Hi,

I am facing same problem and also same error. I made virtual directory named olap. Whenever i am giving this URL on IE :-
http://localhost/olap/msmdpump.dll... once it's giving a error like 406 not accepted and also
some times it's opening a file and asking about open, save or cancel it but it's not opening XML file.Can anyone tell me what is the problem in it.

Thanks in advance

Marco Groeneveld

Sage

Posts: 138

Date of registration: Oct 27th 2005

  • Send private message

15

Wednesday, April 2nd 2008, 8:16pm

Hi,

Steps:

Just copy the full map into c:\inetpub\wwwroot\xmla or olap as you prefer.

In IISAdmin you should have .NET 2.0 and security settings as prefered and dll support added.

Depedent if you use Windows XP, Windows Vista or Windows 2003 you should have IISadmin settings updated.

For more info: www.reportportal.com

Best regards,
Marco

amu

Trainee

Posts: 5

Date of registration: Apr 2nd 2008

  • Send private message

16

Thursday, April 3rd 2008, 7:21am

hi macro,

i gone through reportportal.com but i m not getting Application Pool node in IIS. and also i m using Window XP, so it is necessary to create new application pool.
And also now i tried this one:

http://localhost/olap/msmdpump.dll

but it's asking to me that ' What u want to do : open, save , cancle'
just like whenever we try this:

http://localhost/olap/msmdpump.ini

can u plz tell me what is the problem in this.

thanks

Marco Groeneveld

Sage

Posts: 138

Date of registration: Oct 27th 2005

  • Send private message

17

Thursday, April 3rd 2008, 9:44am

Hi,

Do you have followed the steps as you find in this information:

http://www.microsoft.com/technet/prodtec…5/httpasws.mspx

Marco

amu

Trainee

Posts: 5

Date of registration: Apr 2nd 2008

  • Send private message

18

Thursday, April 3rd 2008, 11:35am

Yes macro, i did all things. and i m using window XP.

amu

Trainee

Posts: 5

Date of registration: Apr 2nd 2008

  • Send private message

19

Thursday, April 3rd 2008, 12:47pm

Connecting to http://localhost/olap/msmdpump.dll producing 406 not accepted Error. Can u tell me what is the problem.

Marco Groeneveld

Sage

Posts: 138

Date of registration: Oct 27th 2005

  • Send private message

20

Thursday, April 3rd 2008, 2:51pm

Just delete the folder and copy again and do the settings in IISadmin.
  • 1
  • 2
Rate this thread