May 4, 2011 at 10:01 pm
Hi,
I am having trouble running an XMLA script to deploy an analysis services database. If I use the service account for SSAS as the impersonator of the connection it works fine, yet when I try and use a windows account who is an administrator on the server and in the sysadmin group I get a connection error??
Doesn't make sense to me?
I have had a good look around yet can't find anything
Any help appreciated
May 4, 2011 at 10:07 pm
Can you post an image of the error or the error message?
Steve.
May 4, 2011 at 10:13 pm
Actually, on re-reading, can you open SSMS in the context of the service account user. Connect to the SSAS instance and then right click, select Properties. Nav to the Security page and check whether the specific user, the local admins group or the sysadmins group (assuming you have a windows group called sysadmins, not just hoping that the SQL group will work here) are present. If none are present then you'll want to add this specific user for which the connections are failing.
Note: adding a user here is the equivalent of sa in SQL server - ie you don't want to give everyone this privilege. Most of the time, you can manage security on a database by database level.
Steve.
May 5, 2011 at 2:53 am
Thanks Steve,
The Administrator user is in the Windows Administrator Group, so he automatically is a member of sql server sysAdmin group and he has been assigned to the analysis services Server Administrators group.
there is no problem deploying straight from BIDS yet when I create an xmla deployment script using the comes up with an error.
Some of the error script is:
<Error ErrorCode="3238068224"Description="The following system error occurred: there are currently no logon servers available to service the logon request.
and..
<Error ErrorCode="3239182436" Description="Errors in the high-level relational engine. A Connection could not be made to the data source with the dataSourceID of 'Adventure Works DW2008 Source' ....
I am running this on virtual server - Don't know if that has anything to do with it.
cheers in advance
May 9, 2011 at 7:12 am
The virtual server could be an issue, but not so much because it's virtual and more if it's not in a domain or a DC itself (not really recommended).
The last time I saw this error " there are currently no logon servers available to service the logon request." it was being caused by a user (and machine) not on our domain attempting to access resources on the domain. We were using windows authentication and had added the 'foreign' DOMAIN\user to the list of allowed users, but when IIS attempted to validate the credentials, that was the error that was thrown.
Steve.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy