locked
Cannot connect to SSAS 2005 server cube by server name RRS feed

  • Question

  • Hi

     

    In ProClarity Desktop Professional 6.3.129.200 we can only connect to a SSAS 2005 cube via IP address currently.

     

    We are all members of the admin role on the cube. We can publish and retrieve briefing books to the PAS

    server successfully, but these all connect to the cube using the IP address. When we change the cube connection

    to use the server name we are prompted for a log-in and password but then are denied access.

     

    We are intrigued as to why we can connect via IP address to the cube and run reports but are denied access to

    the cube when we attempt to connect via server name.

    Many thanks for your time in advance.

     

     

    Friday, January 25, 2008 6:28 PM

Answers

  • Did you try using servername with the portnumber, seperated by a colon in ProClarity?  If you're not running on a default port, you would need to enter the port number in ProClarity as well.

     

    Friday, February 1, 2008 10:39 PM

All replies

  • Hi Bryan,

     

    Can you ping the SSAS server by hostname, fqdn and IP address?  Is anyone able to connect to the SSAS server by hostname with any program?  The login prompt will appear no matter what server name you try and connect to, or even if you try and connect to a working server that is shut down, so the credentials prompt doesn't necessarily mean a connection is being made with access denied.

     

    hth

    Friday, January 25, 2008 7:25 PM
  • hi !

     

    yes we can ping the server by hostname and ip address. We can connect to the SSAS server in SQL 2005 Management Studio by using servernameStick out tongueortnumber and see/process the cube. Strangely, in Management Studio, servername on its own does not work(connect), which may be linked. ProClarity desktop pro works 100% fine using tcp address only, ProClarity via the web connects to the PAS server but not the cube ?

     

    Friday, January 25, 2008 9:21 PM
  • This sounds like a possible issue with the SQL box.  What you'll want to try next would be to connect to SSAS using another program, such as Excel or the MDX Sample App, and if you are able to connect via server name vs. IP address. 

    If you have more than one SSAS server in your environment you could test connecting to another server from ProClarity by hostname or fqdn.  Basically this would narrow the scope of the problem to the SQL server, ProClarity software, or something else in the environment.

     

    hth

    Monday, January 28, 2008 3:16 PM
  • Did you try using servername with the portnumber, seperated by a colon in ProClarity?  If you're not running on a default port, you would need to enter the port number in ProClarity as well.

     

    Friday, February 1, 2008 10:39 PM