Showing posts with label deploy. Show all posts
Showing posts with label deploy. Show all posts

Monday, March 12, 2012

I tried deploying an SSAS project under SQL 2005 dev server, but, deployment fails

This project is with multi data sources, multi cube - when I deploy, I get the following error:

Error 1 Either the 'MELLONBANK\ADCDT2Q' user does not have permission to create a new object in 'SMAMSQL5DEV', or the object does not exist. 0 0

I tried from SQL Server Management studio, I can create tables, write to it fine.

I asked the DBA whether permission problem - she said if SSIS is trying to write to file, there might be some problems, but, database creation shouldn't be a problem. My question is does SSIS try to write some XML when I deploy - my guess is it does with all the properties written in XML. Just trying to confirm with you guys!|||

I assume that you were actually talking about SSAS, not SSIS in your previous post.

The fact that you get this error when deploying an SSAS project means that you are not in the Admin group for SSAS. SSAS is different to the SQL Server relational engine and the fact that you could create tables/databases there does not mean that you have permissions to do this in SSAS.

You will need an Administrator (maybe the person who installed SSAS) to open up SQL Server Management Studio and do 1 of 2 things.

either.

1) Right click on the server, go to properties, click on the security option and add your user account - this will set you up as an SSAS administrator, which will let you create new databases.

Or

2) Create an empty database for you, add a role with your user account and set this role to have admin priviledges just on this database.

|||

My Admin has created an empty database and an Role for Me with Admin Permission,

but I am Still not able to Deploy the Solution with BIDS.

Error was "Für die XYZ-Datenbank wurde ein Identit?tswechselmodus festgelegt, der für Serveradministratoren reserviert ist."

if i freely translate to englisch "For the database xyz a identityimpersonationmode was set that is reserved for system administrators"

Whats wrong there?

Best Regards

HANNES

|||This has to do with how your datasource is configured. If you are not an admin, you cannot deploy a database that has a datasource with the identityImpersonate property set to something like ImpersonateServiceAccount. This is to prevent you possibly getting access to a connection with higher priviledges than your user account. You will either need to set the impersonation mode to another value. If you need it to be set like it is then you could get the admin to change it for you after deployment, the make sure you only deploy changed values or use the Database Deployment Wizard to deploy without the datasources.

I tried deploying an SSAS project under SQL 2005 dev server, but, deployment fails

This project is with multi data sources, multi cube - when I deploy, I get the following error:

Error 1 Either the 'MELLONBANK\ADCDT2Q' user does not have permission to create a new object in 'SMAMSQL5DEV', or the object does not exist. 0 0

I tried from SQL Server Management studio, I can create tables, write to it fine.

I asked the DBA whether permission problem - she said if SSIS is trying to write to file, there might be some problems, but, database creation shouldn't be a problem. My question is does SSIS try to write some XML when I deploy - my guess is it does with all the properties written in XML. Just trying to confirm with you guys!|||

I assume that you were actually talking about SSAS, not SSIS in your previous post.

The fact that you get this error when deploying an SSAS project means that you are not in the Admin group for SSAS. SSAS is different to the SQL Server relational engine and the fact that you could create tables/databases there does not mean that you have permissions to do this in SSAS.

You will need an Administrator (maybe the person who installed SSAS) to open up SQL Server Management Studio and do 1 of 2 things.

either.

1) Right click on the server, go to properties, click on the security option and add your user account - this will set you up as an SSAS administrator, which will let you create new databases.

Or

2) Create an empty database for you, add a role with your user account and set this role to have admin priviledges just on this database.

|||

My Admin has created an empty database and an Role for Me with Admin Permission,

but I am Still not able to Deploy the Solution with BIDS.

Error was "Für die XYZ-Datenbank wurde ein Identit?tswechselmodus festgelegt, der für Serveradministratoren reserviert ist."

if i freely translate to englisch "For the database xyz a identityimpersonationmode was set that is reserved for system administrators"

Whats wrong there?

Best Regards

HANNES

|||This has to do with how your datasource is configured. If you are not an admin, you cannot deploy a database that has a datasource with the identityImpersonate property set to something like ImpersonateServiceAccount. This is to prevent you possibly getting access to a connection with higher priviledges than your user account. You will either need to set the impersonation mode to another value. If you need it to be set like it is then you could get the admin to change it for you after deployment, the make sure you only deploy changed values or use the Database Deployment Wizard to deploy without the datasources.

Friday, March 9, 2012

I need to know how to deploy reports without Visual Studio

I have reviewed the available documentation and was unable to locate a
method to deploy reports outside of Visual Studio without instantiating
the web service. We have a package we would like to bundle with some
reports.
Does anyone know an easy way to deploy reports using an .rdl file?The only way to deploy reports is through the web service. (VS uses the web
service) Look for the method CreateReport. You can always use rs.exe and
create a simple script to do the deployment.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kelly Gross" <kgross@.htp-inc.com> wrote in message
news:1103233970.824910.306870@.f14g2000cwb.googlegroups.com...
>I have reviewed the available documentation and was unable to locate a
> method to deploy reports outside of Visual Studio without instantiating
> the web service. We have a package we would like to bundle with some
> reports.
> Does anyone know an easy way to deploy reports using an .rdl file?
>|||The rs utility requires administrator permission on the target machine.
We are using an msi install which runs in the context of the local
system account. Do we have sufficient permission to run the rs utility?|||Non admins can run rs, but there is an issue on W2k that prevents this. XP
and W2k should be fine. However the local system account is an admin so you
should not see this issue (although I have not tried it and can't be 100%
sure). The problem is not a permission issue, but something with the
framework.
The user will need permission within RS. As long as local admins have
permission to publish to RS then you should have no issues.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kelly Gross" <kgross@.htp-inc.com> wrote in message
news:1103235966.097594.118890@.f14g2000cwb.googlegroups.com...
> The rs utility requires administrator permission on the target machine.
> We are using an msi install which runs in the context of the local
> system account. Do we have sufficient permission to run the rs utility?
>|||Why not use the upload file buttom of the Report Manager
(http://yourreportsite/reports) to do the deployment?
a) Upload the rdl;
b) Create the db connection manually again within the Report Manager.
Tao
"Daniel Reib [MSFT]" wrote:
> Non admins can run rs, but there is an issue on W2k that prevents this. XP
> and W2k should be fine. However the local system account is an admin so you
> should not see this issue (although I have not tried it and can't be 100%
> sure). The problem is not a permission issue, but something with the
> framework.
> The user will need permission within RS. As long as local admins have
> permission to publish to RS then you should have no issues.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Kelly Gross" <kgross@.htp-inc.com> wrote in message
> news:1103235966.097594.118890@.f14g2000cwb.googlegroups.com...
> > The rs utility requires administrator permission on the target machine.
> > We are using an msi install which runs in the context of the local
> > system account. Do we have sufficient permission to run the rs utility?
> >
>
>