Re: ImpersonationMode that is reserved for server administrators
- From: "Jeje" <willgart@xxxxxxxxxxx>
- Date: Tue, 2 Oct 2007 00:16:35 -0400
this article describe your issue
http://support.microsoft.com/kb/922853
click on the first link of the resolution section to obtain the hotfix...
"Ralph Lydin" <RalphLydin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D727A05F-ED82-40A4-9FB0-A7BC2D6D6642@xxxxxxxxxxxxxxxx
Using Microsoft Analysis Services 2005, we have found it impossible to deploy.
a database from BIDS (Business Intelligence Development Studio) without
giving the deployer an unacceptable permission level.
We have found that if the deployer is an NT server administrator or is in
the Analysis Services server role, the deployment runs.
However, if the deployer has no server-level authority, we get a message
like the following:
"The database , 'ASO_StatisticalAnalysis', contains an ImpersonationMode
that is reserved for server administrators"
This happens even if the database already exists, and deployer has been put
into a role that has full control of it.
It happens if the database is on the same server as BIDS, or on another.
It happens if the deployment option is ‘Deploy All’ or ‘Deploy Changes Only’.
We have tried this with the following data source impersonation modes, all
with the same result:
• Default
• Use the credentials of current user
• Use the service account
• Use a specific user ID and password
We have tried with Destination Server Edition set to ‘Enterprise’,
‘Developer’, and ‘Standard’, with default impersonation mode.
We have tried with both Service Pack 1 and Service Pack 2.
We have had similar problems when running an xmla script to do the deployment.
We have worked around this problem by giving server authority to anyone who
needs to deploy. This is obviously not an acceptable long-term solution.
Please advise.
- Prev by Date: Re: Parallellperiod with multiselect
- Next by Date: How to Back up a SQL Server 2005 database to 2000 format
- Previous by thread: Creating an artificial unique ID
- Next by thread: How to Back up a SQL Server 2005 database to 2000 format
- Index(es):
Relevant Pages
|
