Hello,

I am experiencing long connection times when trying to connect to Analysis
Services. As much as 10-15 seconds. It happens from Analysis Manager, the
MDX sample tool and Reporting Services (from this one up to 30-40 seconds).
Once I am connected any MDX query runs just fine, super fast.

The computers are on a private VLAN and there's no other network traffic.

Anyone has any idea how I can fix this?

Thank you so much,

Mike

Could you be having a domain issue? One of the things that AS does on a
connect is to valid the domain credentials (though an OS impersonation). I
have seen plenty of customer domains where it takes 5-10 seconds for a
domain controller validation.

Several things you can do to troubleshoot if you have domain issues:
1) add a file share to the Analysis server and create a restricted ACL
against it so the system has to validate your NT credentials. This is
similar to what AS does, so if you get a long delay with the file share and
AS then it is a good chance that this is the problem.
2) create a machine account on the Analysis server and a machine account on
your client (same username and same password). Logon onto the client with
that account and try accessing the Analysis server (try #1 also). Or rather
than doing an actual logon to the account, if the account you are using on
the client is an administrator of the client, then tou can also add a
shortcut to the desktop for the MDX Sample app and now the right-click menu
will include a "Run as..." option which you can specify the NT machine
account you want to use even if you are logged into a different account.
3) Try adding sspi=anonymous on the connect string -- this tells AS to not
do the impersonation. You can easily do this with the MDX Sample app by
adding it to the server name on the connect dialog box. If you server is
named "foo" then enter "foo;sspi=anonymous" as the server name on the
connect dialog box..
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Mike Sarbu" <m_sarbu (AT) yahoo (DOT) com> wrote

Sometimes, problem appear with bad configuration of network. Try to edit
'host' file into 'WINDOWS\system32\drivers\etc' and add your server ip/id on
the two side.



"Dave Wickert [MSFT]" wrote:

Thank you both for your answers.

Well, it's not the domain and it's not the network. I have installed
Analysis Services on a Win2000 machine in the same network and it works just
fine. The one that gives me headaches is a Win 2003 cluster. I have already
rebuilt the cluster once because of this issue. When I rebuilt it, I didn't
cluster AS again, I just left it on the active node. The database is 100%
MOLAP, so no access to the SQL database is needed when executing a query
against it.

Any other ideas? (other than switching my database cluster to Win 2k)?

Thanks a lot,

Mike





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

I read something regarding this problem a time ago.. and i think that
Analysis Services does a Reverse Domain Name lookup during the client
connection.
may be, the DNS server on the network don't have this reverse lookup zone
configured...once this zone is configured and PTR records are adding for the
machines, the connection time dropped to 15ms (from 10 or 15 seconds).

see KB article (828280) on using Kerberos with AS

Regards
Rodrigo

"Mike Sarbu" wrote: