What's the difference between the Current User and the ID I'm using to login?
When I test the Run as feature on SSAS, what's the different between the Current User (logged in as domain\tom) and explicitly specify to run as domain\tom?
The funny thing now is if I run as the Current User (logged in as domain\tom), I can actually browse the cube. However if I explicitly specify to run as domain\tom, it says log in failure - unknown user name or bad password.
Btw, domain\tom is the SSAS Administrator.
Any idea?
The funny thing now is if I run as the Current User (logged in as domain\tom), I can actually browse the cube. However if I explicitly specify to run as domain\tom, it says log in failure - unknown user name or bad password.
Btw, domain\tom is the SSAS Administrator.
Any idea?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
However I did log in the Windows as domain\tom.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well, actually I'm not sure if we really have a <sub domain name>. We always use the <large domain name> to log in.
Can you point me to something like the different ways we can architect this large domain - sub domain environment? I suppose we can do synchronization. Can we do like directly authenticating by using the large domain controller? If we are directly authenticated by the large domain controller, meaning there is no directory information stored on my local domain controller, right?
I also remember there is something called Trusted Domain? I'm not sure if this is really our case here - just wondering.
Thanks.
Can you point me to something like the different ways we can architect this large domain - sub domain environment? I suppose we can do synchronization. Can we do like directly authenticating by using the large domain controller? If we are directly authenticated by the large domain controller, meaning there is no directory information stored on my local domain controller, right?
I also remember there is something called Trusted Domain? I'm not sure if this is really our case here - just wondering.
Thanks.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm directly using BIDS on the SSAS server which is the DC of the sub domain.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I just confirmed with my system administrator. There is no subdomain. The server is just a regular server in the domain. It's not a domain controller. There is only one domain.
Any idea?
Any idea?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, will do when I have a chance. However when I tested earlier, I was testing directly on the server, so I was using localhost.
Btw, everything was working fine in the past.
Btw, everything was working fine in the past.
ASKER
Thanks.
ASKER
I do need to check since my domain is a sub domain of a large one. I'm not sure if they are doing synchronization or what - need to find out.