Analysis Services Profiler trace local only?

Question

Analysis Services Profiler trace local only?

Pam Brisjar

SSChampion

Points: 12094
More actions
October 24, 2007 at 3:06 pm

#183147

I'm just setting up my first SSAS Profiler trace and it appears to be a bit quirky. Seems to be only a local connection will work and the Profiler itself doesn't want to connect to any other server to save the trace table. Also, no login / password required?
None of this is making me happy.
Is it me or is it SQL Server?

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Tommy Bollhofer SSChampion Points: 14940 More actions · Answer 1

I'm unable to reproduce this behavior - are you running SP2? Regarding login/password, SSAS only supports NTLM/Keberos authentication.

Tommy

Follow @sqlscribe

Pam Brisjar SSChampion Points: 12094 More actions · Answer 2

Pam Brisjar

SSChampion

Points: 12094

October 24, 2007 at 3:25 pm

#745131

Version is 9.00.3175.

Tommy Bollhofer SSChampion Points: 14940 More actions · Answer 3

I'm running cumulative update 3 (Build 3186) although there are no fixes for profiler in this build to the best of my knowledge. Does it give you a specify error when connecting to a remote server?

Tommy

Follow @sqlscribe

Pam Brisjar SSChampion Points: 12094 More actions · Answer 4

When I try to connect remotely I get:

An error encountered in the transport layer. The peer prematurely closed the connection. (pfutil90)

I connect fine to the Database engine, just not Analysis Services.

Also, when I go to save the trace data on the AS machine, only local servers show up. The network tab isn't even there.

zulumojo Newbie Points: 6 More actions · Answer 5

I am experiencing this same problem. Did you find a solution. I am NOT running SP2, do you think that will fix it?

Stefan K SSCommitted Points: 1786 More actions · Answer 6

Hi,

this sounds like an authentification problem. SSAS does use Integrated Windows Authentification only. This means that the current user's credentials (on your client) (user + password) are used to authenticate against the olap server. So your domain user (if you have a windows domain) has to have the accurate permissions to access the olap server. (maybe olap admin)

If you have only local users on your machines (no domain) you could use a trick. Create a user on the machine with the same name and password as you are logged on at your client. Give it the accurate permission and try it again.

Kindest Regards,

SK