Authentification problem

[fknusername]

Hi everyone !

I installed a console (client part) so that I can work on my machine instead of having to work on the server. My problem is : I cannot connect to the server. I get the "Security error. Unable to authentify user" error. It's a translation, 'cos it's in french, so it might not be the EXACT message.

Does anyone have an idea about how to fix this thing ?

 

[JayKusch]

Have you applied the latest service pack for AS?

Thanks

J. Kusch

 

[MDXer]

1 Question and 1 thing for you to check into

Question: Is your client machine on the same domain as the server machine?

Check: Make sure that the domain logon you use on your desktop is a member of the OLAP Administrators group.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck

 

[AMJackson]

Just some points of caution on this.
If you're trying to impersonate someone else, this could also give you problems unless you're using Kerberos (or Negotiate) security protocols.
If you're using NTLM and you're impersonating someone elses credentials then the security token for NTLM is not strong enough when you pass it to the OLAP server and it won't let you in.

 

[fknusername]

Well, thank you guys. First of all, we'll install the SP, then we take a look at the rest. Because I know the user is member of OLAP Administrators, but the machine isn't on the same domain. This causes no problem whatsoever for the SQL Server part, I can access it through the MMC console with no problem at all.

I won't be able to take a look at this until next wwek, so I'll come back to you then.

Thanks again for the tips !

 

[MDXer]

If the machines are on diffrent domains then it is more than liely the problem. Analysis Services doesn't handle Security the same way SQL does (why? don't ask me it makes no sense). When attempting to login across domains Analysis Services will take the UserName and Password you provide and try to authenticate it against the domain it lives on. If you look at you Security Event Logs on the machine you will probably see a bunch of failed logins. There is a work-around but it probably isn't a very secure one so I won't post it. If you find this is your problem, let me know.

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck

 

[fknusername]

As a matter of fact MDXer, this seems to be the problem. I finally found some time to take a look at it and you're 100% right. The simpliest solution we think about is to put the server on the main domain. So everything will then be fix and we'll be able to use the OLAP capabilities efficently.

Thanks again for your help !

 

[MDXer]

Glad you found the problem

"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck

 

[kirni]

Hi MDXer,
I've got the same problem and can't change the domain structure of our firm. We have two domains connected over a VPN.
You talked about a workaround to solve the problem. How can I solve the problem?

 

[MDXer]

kirni possible work around (may not work in every case) is to create an identical username with the axact same passowrd on the domain where the Analysis services Server is.

Domain 1
Username: OlapUser
Password aBcD123


Domain 2
Username: OlapUser
Password aBcD123

I encountered this problem prior to SP2 or SP3 so I am not sure is it has been fixed in either of these service packs




"Shoot Me! Shoot Me NOW!!!"
- Daffy Duck