Hi,

Please help, I have been searching over the web for the past few days but
still couldn't find a solution.

Server
Win 2003 Server with SP1
SQL 2000 Standard Edt with SP1
Analysis Services with SP4

Workstation
Win XP with SP2
SQL 2000 Personal Edt with SP2
Analysis Services with SP4

I am trying to connect to a Cube created on the Server from my workstation
via PivotTable. I can't connect. It says "Unable to open connnection.
Unspecified error". But I can connect to the one on my workstation.

Please help.

By any chance do you have the Windows XP firewall or the firewall on the
server operational? You'll need to insure that ports 2393 and 2394 (this is
for Analysis Services 2000) are open to allow connectivity. As well, are
your two boxes connected to a domain such that you are authenticated user
that is connecting from the client to the server?

--
HTH!
Denny Lee
<dennyglee_at_hotmail_dot_com>

Blog at:: http://spaces.msn.com/members/denster/



"BN" <BN (AT) discussions (DOT) microsoft.com> wrote

Hi Denny,

Thanks for your reply.
I have enabled those ports, but still same error.
The AS server is a standalone server, hence no domain.
Is this the culprit? But I can connect to the SQL server.

Regards,

"Denny Lee" wrote:

Hmm - it may be. When you connect to the SQL server, are you connecting via
"domain" of sorts or using the SQL login? SQL has its own authentication
system that allows you to "bypass" windows authentication. In the case of
Olap, though, you need to utilize windows authentication. Saying this, you
may be able to work around it by using basic authentication where you would
need to have your pivot pass in username and password in clear text and then
have your OLAP server be able to recognize and allow access to that user.
But in general, the preferred option is having a domain such that the OLAP
server can use Windows auth instead.

--
HTH!
Denny Lee
<dennyglee_at_hotmail_dot_com>

Blog at:: http://spaces.msn.com/members/denster/



"BN" <BN (AT) discussions (DOT) microsoft.com> wrote

You can also work around this by setting up a local account on the AS2k
server that has the *identical* username and password to a local account
on your workstation (it must be a local account on your machine)

Make sure that the local account on the server is in role in AS that
will allow it access to the OLAP database and log on to your workstation
using the local machine account and you should be able to get access.

I have used this scenario at client sites where they used Novell Netware
and we did not have an NT domain.

--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

In article <edzMdIx2FHA.3628 (AT) TK2MSFTNGP12 (DOT) phx.gbl>,
dennyglee (AT) hotmail (DOT) com says...