SQL Server 2014 Analysis Services Deploy Permission Error - ssas

How can I resolve this permissions error when deploying an Analysis Services cube? The user already has SA privileges on the localhost server.
------ Build started: Project: FerrariRusso, Configuration: Development ------
Started Building Analysis Services project: Incremental ....
Dimension [Date] : Create hierarchies in non-parent child dimensions.
Dimension [Customer] : Create hierarchies in non-parent child dimensions.
Dimension [Product] : Create hierarchies in non-parent child dimensions.
Build complete -- 0 errors, 3 warnings
------ Deploy started: Project: FerrariRusso, Configuration: Development ------
Performing an incremental deployment of the 'FerrariRusso' database to the 'localhost' server.
Generating deployment script...
Add Database FerrariRusso
Process Database FerrariRusso
Done
Sending deployment script to the server...
Error -1055391738 : Either the 'ACMECorp\tarzan' user does not have permission to create a new object in 'ACTARZAN-WIN81', or the object does not exist.
Deploy complete -- 1 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

If the user you are deploying with is not a member of the Analysis Serices administrators group, you can modify role membership using the following procedure.
Run SQL Server Management Studio as administrator
Open the Analysis Services server in the Object Explorer
Go to Properties
Go to Security
Add the user as an administrator.

Related

Job fails when loading data from server1 to server 2 inside SQL Server agent

I have created a ssis package to load data from server 1 table1 to server 2 table2. This package is running fine inside the business intelligence studio. But the issue is , when I schedule this package in SQL server agent as a job, the package execution is failing.
The error I am getting is
SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. Description: "Login failed for user 'Domain\Server1$' .
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "Server2.Database2" failed with error code 0xC0202009.
Please help me to fix the issue. I am using SQL Server 2014
Thank you very much for your time and help!
This is a security / permissions issue. Update the SQL Server Agent job to use an account which has sufficient permissions to complete all of the actions inside the SSIS package.
Explanation
The package completes succesfully when executed from Business Intelligence Studio, because that execution is running under you credentials. It is running as you. When you run the package from SQL Service Agent job, it is NOT using your credentials. Instead it is using account 'Domain\Server1$' and that account does NOT have sufficient rights against Server2.Database2 to complete all of the package actions.
To solve this, you could update the security on Server2.Database2 and allow 'Domain\Server1$' to perform the same actions as you, but that is unadvised. Instead, best practice here is to establish an SSIS proxy account. Here is a good article discussing how to go about that. After you have established this proxy account, grant the new proxy account sufficient permissions to complete the actions inside of your SSIS package and your error message will go away. Hope this helps!

SQL Server Agent Jobs to Run SSIS Package

I have a SSIS package which i tried to schedule as a job in SQL Server Agent.
In order to achieve this i have created a Credentials with User having SysAdmin role to the server. Also i have created a proxy account to run the job where the principals added for
SQLServerAgent,SQLServerOperator,SQLServerReader.
While configuring job selected package source as File system and given the package path to execute the same.
Package is running good and updating results to table stand alone but not working when executing via SQL Job.
Error:
The process could not be created for step 1 of job 0x7D722F8836388B46956B164E33DE8955 (reason: A required privilege is not held by the client). The step failed.,00:00:00,0,0,,,,0
Fix Tried: Modified the package security with Encryptallwithpassword and no luck still.
Check your SQL Server Agent service account to make sure it has permissions to the database and the folder where the packages are being called from.
The proxy account is the user that the package will run as, so make sure that is selected in the job step.
For package encryption, unless you are saving credentials in the package, you can set the protection level to "DontSaveSensitive". It sounds like the proxy account will have the permissions you need already assigned.

reporting server error in IE browser

Using server server 2008 r2 and vs08 i use SQL reporting services and i also install iis so when i deploy reports it show me like this
Deploying to http://localhost/ReportServer
Error rsServerConfigurationError : The report server has encountered a configuration error.
Deploy complete -- 1 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
and when i go to this url http://localhost/ReportServer in IE(Internet Explorer ) then it show me like this in browser
pic IE
where problem occurred and how i resolved this problem
i try so many times to deploy errors but in every time any error must come ..ughh :(
You may want to see if SSRS will resolve 'localhost' correctly. There are a few things to think about deploying to SSRS as well.
You need to be a role under the SSRS site that allows deployment. You can try all day and if your 'Role Assignment' is not 'Publisher' or 'Content Manager' for your domain user/user or applicable group in a domain you will not be able to publish.
SSRS resolves to fully qualified paths and any breaks in names or leaving a report folder blank could potentially cause issues. When you are in Business Intelligence Development Studio(BIDS in Visual Studio), your project's 'properties' must be configured correctly and for the correct version of SSRS you are deploying to.
Check the SSRS Config tool for what it shows the service to be at qualified. Generally it is:
http:// (servername)/ReportServer
NOT
http:// localhost/ReportServer
I wrote up a pretty thorough answer to this on another thread.
How SSRS deployment works?
Did you make any changes to the reporting services config files?
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer
Is ReportManager working ok?
Have you another ReportServer that you can deploy to?
If it deploys elsewhere ok, I would re-install reporting services
I have red that you have IIS and SSRS Server on the same machine. The standard port for both is 80, perhaps it would worth a try to change the port for SSRS to a different value. (Reporting Services Configuration Manager -> Web Service URL -> TCP Port and Report Manager URL -> Advanced -> Edit -> TCP Port)

Unable to execute query against a linked server inside a SQL Job

My server setup is a bit weird. One of my DB Admins added a Linked Server to my server. In the linked server properties, I see the following in the Security view:
Local server login to remote server login mappings:
Local Login Impersonate Remote User Remote Password
domain\myusername CHECKED
For a login not defined in the list above, connections will:
- Be made using the security context
Remote login: linkedserveruser
With password: **************
Therefore, when I created a stored procedure with the following:
SELECT *
INTO #TEMP
FROM LINKEDSERVERNAME.DBName.dbo.TableName
-- Update local table after processing #TEMP
And setup a SQL job, it was failing with the following message:
Message
Executed as user: NT AUTHORITY\NETWORK SERVICE. Login failed for user 'linkedserveruser'. [SQLSTATE 28000] (Error 18456). The step failed.
After, digging through documentation, I found a KB811031 article that explains this problem and suggested that I map the security context and run the job as osql.
I did not have to map the security context because (as you can see from the settings of the linked server above), it already was mapped. I changed the Type to Operating System Command as suggested. When I run the job now, I get the following message:
Executed as user: domain\MYMACHINENAME$. Msg 18456, Level 14, State 1, Server SOMEOTHERDATABASENAME, Line 1 Login failed for user 'linkedserveruser'. Process Exit Code 0. The step succeeded.
And the job quits reporting success when in fact it failed. Any suggestions on how I can get this type of stored procedure containing a query to a linked server to run as a SQL job?

SQL JOB reason 193

I create MSSQL job with console application (operating system - cmdExec), I get error with eason 193.
There is full message:
Executed as user: NT AUTHORITY\NETWORK SERVICE. The process could not
be created for step 1 of job 0x4CB38CF498AEE244A487876F4746F5A7
(reason: 193). The step failed.
What could be a cause of it?
Have you gotten this kind of error before or have you successfully created jobs in the past?
It's likely that that specific account doesn't have the permissions necessary to create the job. If you've got access to SQL Server Management Studio, you can use the two links to learn more about the permissions needed (inside of the MSDB database) as well as how to check and set those permissions for a specific account.
SQL Agent permissions Reference
Check and set permissions for SQL Agent Jobs