What Permissions Are Required To Call The ReportingService2005.CancelJob Method?
Apr 14, 2008
I'd like to cancel my long running Reports via ReportingService2005.CancelJob(). It seems, while I'm able to start a job I don't have the permission to cancel it. I always get the error message:
The permissions granted to user '<my-account>' are insufficient for performing this operation.
Do I have the be a member of a special group on the server running the Reporting Services?
I've created an SSIS package that contains a Sequence Container with TransactionOption = Required. Within the container, there are a number of Execute Package Task components running in a serial fashion which are responsible for performing "Upserts" to dimension and fact tables on our production server. The destination db configuration is loaded into each of these packages using an XML configuration file. The structure of these "Upsert" packages are nearly identical, while some execute correctly and others fail. Those that fail all provide the same error messages.
These messages appear during Pre-Execute
[Insert new dimension record [1627]] Error: The AcquireConnection method call to the connection manager "DW" failed with error code 0xC0202009.
[DTS.Pipeline] Error: component "Insert new dimension record" (1627) failed the pre-execute phase and returned error code 0xC020801C.
... which are followed by
[Connection manager "DW"] Error: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction.".
[Connection manager "DW"] Error: An OLE DB error has occurred. Error code: 0x8004D00A.
While still in debug mode, I can check the properties of the "DW" connection and successfully test the connection within the packages that fail.
The same packages run successfully when tested outside the container (i.e. no transaction) or when the configuration file is modified to point the "DW" connection to a development version of the db which is running on the same server as the source database.
I have successfully used DTCtester to verify that transactions from source to destination server are working correctly. Also tried setting DelayValidation = True with no change. I have opened a case with Microsoft and am awaiting a reply so I thought I'd throw a post out here to see if anyone else has encountered this and might have a resolution. Here's some more on the environment:
Source Server:
Windows Server 2003 Enterprise Edition SP1 SQL Server 2005 Enterprise Edition SP0
Destination Server:
Windows Server 2003 Enterprise Edition SP1 SQL Server 2000 Enterprise Edition SP3 (clustered)
Thank you in advance for any feedback you might be able to provide.
Hello! I have the following problem. I developed CLR Stored Procedure "StartNotification" and deploy it on db. This sp calls external web service. Furthermore, this sp is called according with SQL Server Agent Job's schedule. On my PC SQL Server works under Local System account and this web service is called correctly (Executed as user: NT AUTHORITYSYSTEM). But on ther other server the following exception is raised during job running: Date 17.04.2007 16:42:10 Log Job History (FailureNotificationJob)
Step ID 1 Server MSK-CDBPO-01 Job Name FailureNotificationJob Step Name MainStep Duration 00:00:00 Sql Severity 16 Sql Message ID 6522 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: CORPmssqlserver. A .NET Framework error occurred during execution of user defined routine or aggregate 'StartNotification': System.Security.SecurityException: Request for the permission of type 'System.Net.WebPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. System.Security.SecurityException: at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) at System.Security.CodeAccessPermission.Demand() at System.Net. The step failed.
What is the reason of this behaviour? Unfortunately I do not have direct access to this server. I have the following guesses: 1) CORPmssqlserver may have not enough permissions to call web service 2) Something wrong with SQL Server account's permissions 2) Something wrong with SQL Server Agent account's permissions I will take the will for the deed. Thanks.
I created a wrapper class for a function, and exposed it through CLR. However, if I call this function form SQL it blows up but if I call directly from a test Windows Form the call works fine.
The blow up is related to EnterpriseLibrary.Data, where my Queue class uses that library to do all data access call ops
Here's my wrapper class:
namespace inlineCLRsql{
public static class Wrapper{
public static void CallQueueEntry(int queueId, int deskNo, int missed){
EXTERNAL NAME inLineLib.[inlineCLRsql.Wrapper].CallQueueEntry
GO
sp_CallQueueEntry 4,2,0
Here is what I get as a result
System.NullReferenceException: Object reference not set to an instance of an object.
System.NullReferenceException:
at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseConfigurationView.get_DefaultName()
at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseMapper.MapName(String name, IConfigurationSource configSource)
at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.ConfigurationNameMappingStrategy.BuildUp(IBuilderContext context, Type t, Object existing, String id)
at Microsoft.Practices.ObjectBuilder.BuilderBase`1.DoBuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)
at Microsoft.Practices.ObjectBuilder.BuilderBase`1.BuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)
at Microsoft.Practices.ObjectBuilder.BuilderBase`1.BuildUp[TTypeToBuild](IReadWriteLocator locator, String idToBuild, Object existing, PolicyList[] transientPolicies)
at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.EnterpriseLibraryFactory.BuildUp[T](IReadWriteLocator locator, IConfigurationSource configurationSource)
at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.EnterpriseLibraryFactory.BuildUp[T](IConfigurationSource configurationSource)
at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.NameTypeFactoryBase`1.CreateDefault()
at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseFactory.CreateDatabase()
at inLineLib.Queue.getNextQueueEntry(Int32 servedBy)
at inLineLib.Queue.callQueueEntry(Int32 servedBy, Boolean callMissed)
at inlineCLRsql.Wrapper.CallQueueEntry(Int32 queueId, Int32 deskNo, Int32 missed)
This may be the wrong forum for this - if so, please direct me to the appropriate forum.
I've recently upgraded to MSSQL 2005 and I'm trying to execute the sp_databases stored procedure, but I'm having what looks like permissions problems. I can execute the stored procedure, but it doesn't return any results. As far as I can tell, the problem is that my userid can't see any rows in sys.master_files (I can select from the view, it just doesn't return any rows).
I've tried any number of things to get this to work, but the only thing that's been successful is to change my userid's database role membership to db_owner. In the long run, this isn't really a viable solution for me, since my userid should only really have read(select) access to the database in question.
I'd appreciate any pointers that you can give me - I figure I'm doing something stupid, but haven't been able to figure out what, yet.
Has there been any fix for this bug? The workaround in the KB article did not work for me and I cannot run my entire application from the Windows directory even if it did.
Please help.
Original Thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=1&SiteID=1&PostID=274359
Workaround KB article: (I cannot run my app from Window directory) http://support.microsoft.com/kb/920272
Hi, I've got the error message below: "Error 80040E2F. A duplicate value cannot be inserted into a unique index [Table name=_SysRDASubscriptions, Constraint name=c_LocalTableName]"
I'm using SQL Server 2005 Compact Edition and still cannot solve the problem although the KB article (920272) said it is fixed in V3.1.
What I need to do is to drop a table and then Pull it again to the PDA but it gives me that error message during pull method. However, I can use the same process to drop and pull other tables and works fine. Will that be the problem related to primary key or to the data of the table?
Hi All, I have a DB2 database on aix server. we had to move some tables to SQL Server 2005. We created individual SSIS files for each table and saved it on the desktop. When I run the package file by double clicking on it the "Execute Package Utility" dialogue box appears and I can click on the "Execute" button and everything goes fine. But if I try to open the same package using "SQL Server Business Intelligence Devlopment Studio" or to run the same package with DTEXEC /f <Filename> , it gives me below error. ===================================================================================== Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. =====================================================================================
We have a SQL2K5 SP2 (x64) in active/passive cluster running an ERP application database. I have users in remote office who are requesting the ability to run the "standard reports" from SSMS such as Disk Usage, Disk Usage by Table and so on. The user in question has AD account within the instance with db_datareader role.
What other database or server defined role is required to allow this user to launch and view the standard reports from SSMS?
I have a SQL Server Agent job with a step to execute an SSIS package. The package has as one of it's connection managers the Connection Manager For Excel Files. When I run the job it fails every time. I have implemented logging and in the OnError event it states "The AcquireConnection method call to the connection manager "LOBMappingExcel" failed with error code 0xC0202009".
I've seen the previous threads on this (although maybe not all of them). However, i don't think I'm getting the error for the same reason. The full error I'm getting is:
I am facing a problem with the connection method, it says,
"[Store [10069]] Error: The AcquireConnection method call to the connection manager "Data Source Destination" failed with error code 0xC001A004. "
(Store - Look up component.)
This problem occurs only when i am using Transaction option, all the component(Look up,Destination etc) says the same error message in the Pre-Execute phase. But i can open the component and can able to see the data in preview.
And also this is not occuring in our testing environment. We have copied the same pakages in our production, the package failed stating the above. I can not simulate the same problem in my testing server.
Has anyone faced this kind of problem? please help me to solve this.
I have prepared several DTS packages which must be launched by a custom external application. What is the best way to provide access to this application? What are the minimum security requirements? Currently, they are local packages; I understand that some utility is offered by saving them as .DTS files, but I don't know the pros & cons. Are there advantages to using the Repository? The app should be able to do its work from a different box on the same network as the server. (Ultra-super-secret security isn't an issue, but I don't want to have give our developers sa-level access unless necessary.)
I've got a Server setup at work on our RD domain It's Windows 2012, running SQL Server 2012 with reporting Services I've installed our application and reports to this server.
If I'm on my CORP domain on my development laptop I can enter the following into IE [URL] ...... and the SSRS reports page opens up fine
I then RDP into this server using my same CORP credentials Open IE on this server and enter the same URL within IE and get User 'CORPORATEjoep' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account Control (UAC) restrictions have been addressed.
I'm on the Server itself. Why does my account not work there, but when I access SSRS from outside this SERVER with same login, it works
I have a SSIS package that reads the data from an Excel file using an Excel Connection Manager and imports the data to a table on a SQL Server 2005 DB instance.
When I run this package locally on the server the package being on the file system, the package executes perfectly. Now I upload the package to the msdb database and the run the package from there and the package still executes successfully.
Now I schedule the package to run as a SQL Server Agent job and the package fails and when the logging is enabled I see this in the log file;
OnError,WEB-INTSQL,NT AUTHORITYSYSTEM,Copy to CRN-ALLOCATION_COMMENTS_TEMP,{40A6BF6E-7121-448B-A49D-DED58FDC746A},{BD991566-F4BD-41BC-AEBF-264032D8D0D3},5/9/2006 1:54:52 PM,5/9/2006 1:54:52 PM,-1071611876,0x,The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.
OnError,WEB-INTSQL,NT AUTHORITYSYSTEM,Copy to CRN-ALLOCATION_COMMENTS_TEMP,{40A6BF6E-7121-448B-A49D-DED58FDC746A},{BD991566-F4BD-41BC-AEBF-264032D8D0D3},5/9/2006 1:54:52 PM,5/9/2006 1:54:52 PM,-1073450985,0x,component "Allocation Comments" (1) failed validation and returned error code 0xC020801C.
I am wondering why the AcquireConnection method call is failing when the package is scheduled? I am running the step as a SQL Agent Service Account and it is the Local System account that starts up the SQL Server Agent and Server and is an Administrator on the box.
User 'DMNServerBreanch' does not have required permissions. Verify that sufficient permissions have been granted and Windows User Account.Control (UAC) restrictions have been addressed.
what are the minimum required permissions for being allowed to deploy a report? When I try to deploy a report in BIDS I get the error message that my user has not sufficient rights for doing so.
Some key data for my configuration:
Windows Server 2003 Standard Edition with Service Pack 1 SQL Server 2005 Standard Edition with Service Pack 1 I'm not a local administrator, but I have administration rights for SQL Server and Analysis Services I'm in the Reporting Services' system administrator and system user groups
I can access http://localhost/Reports, but not http://localhost/ReportServer I have access to the directory (incl. subdirectories) MSSQL.2, but not to MSSQL.1MSSQL and MSSQL3Reporting Services I can't run the Reporting Services Configuration Tool (see http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1565766&SiteID=1) I can't connect to Reporting Services in SQL Server Management Studio
My question is (as I have already mentioned in the beginning): what are the minimum rights the IT administrator has to assign to my user so that I'll be able to deploy reports? Giving me local administrator rights is not possible.
Thanx in advance and kind regards, Gerald
Update:
In the meantime I have found out, that I'm most probably not a member of the Publisher role. But although I am in the System Administrator role I cannot assign myself to this role. When going to http://localhost/Reports the required links are just not visible. Is this because I'm not a member of the groups SQLServer2005ReportServerUser$... and SQLServer2005ReportingServicesWebServerUser$... ?
I'm implementing row-level security in a SQL Server database that uses Microsoft Access for the front end. I'm using a UDF (a view behaves the same way) to restrict access to specific rows of a base table based on membership in a role. According to the reading I've done, if the base table has DENY ALL permissions for the role, and the UDF has GRANT ALL, members of the role should be able to update records in the base table via the UDF, without having direct access to the base table. However, I find that unless I grant appropriate permissions on the base table, the user is unable to update the table via the UDF.
Is this expected behavior? Nothing I've read suggests I should have to grant permissions on the columns of the base table.
The package runs fine if I run it by itself. Unfortunately we want to call it from another package and when we do so it fails everytime with the following error; "AcquireConnection method call to the connection manager "BPCSF" failed with error code 0xC0202009." This package is calling an AS400 and pulling data from it into a staging environment. The task that is failing is 4th task on the list and is the 3rd task to call the AS400 environment. If I need to provide more information I would be happy to do so. Any help would be greatly appreciated. Thanks!
I have an SSIS package which takes input from Flat file and transfer the data to SQL Server using OLEDB Destination Data Flow Item. The OLEDB Connection Manager used for the destination is configured to use SQL Server Authentication for the user €˜sa€™. The package works fine without enabling the configurations. But when I enable package configuration and save the configuration of the various connection managers in an XML configuration file and then run the package it gives the following error in the validation phase: [OLE DB Destination [21]] Error: The AcquireConnection method call to the connection manager "<Connection Manager Name>" failed with error code 0xC0202009. And after the validation phase is complete the following error message is given for the package execution: [Connection manager "<Connection Manager Name>"] Error: An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client€? Hresult: 0x80040E4D Description: "Login failed for user 'sa'." Has anyone else run into this? I am running SQL 2005 9.0.1399 and VS 2005 8.0.50727.42 (RTM.50727.4200) on Windows Server 2003 Enterprise Edition SP1. Any suggestions would be welcome. TIA, Robinson
What are the minimum permissions required by the SQL Server 2005 Upgrade Advisor (UA)? I could not find it in the documentation.
Obviously being a local Administrators Windows group and a member of sysadmin SQL Server role will do the trick.
But will being a member of only the sysadmin SQL Server role be enough? I know that the UA does want to read the registry.
Running it under just sysadmin generates the following type of errors:
Database Server PreUpgrade Requested registry access is not allowed. WINSOCKPROXY
Database Server PreUpgrade Requested registry access is not allowed. FTUNSIGNEDCOMPONENTS
Database Server PreUpgrade Requested registry access is not allowed. NETPROTOCOL
Database Server PreUpgrade Requested registry access is not allowed. FTMULTIPLEINSTANCES
Database Server PreUpgrade Requested registry access is not allowed. INVALIDNAMEDPIPE
Database Server PreUpgrade Requested registry access is not allowed. FTCOMPONENTREG
Database Server PreUpgrade Requested registry access is not allowed. FTACCTPASS
The issue then is whether these are significant or not. If the UA is only reading the registry to determine if SSAS, DTS, etc is installed then that is not important. But if it is affecting the end result because it cannot read critical information from the registry that is another matter.
Is it possible to force a build to fail when a stored procedure in a project calls another stored procedure with one or more required parameters missing. E.g.: Â CREATE PROCEDURE [App].[ServiceUser_Save] @userID int-- Param #0 ,@serviceuserID int-- Param #1 ,@version int-- Param #2 etc...
And then in a separate stored procedure we have the following
I can run this package in Studio and it works fine, but when I run it from SQL Server Agent, it throws this error. Does anybody know what would cause this problem. This appears to occur during validation for the package because none of the data flow steps run. The connection being used is the same connection used in all of the data flows. If validation is done in order, then prior steps using the same connection are passing validation.
I have a Windows NT group that is used to delegate certain database responsibilities to other members of staff and I am trying to grant permissions for the members of the group to be be able to establish database mirroring sessions, as in run the following:
ALTER DATABASE <database> SET PARTNER = 'tcp://principal_server.domain.com:port';
Although the group has db_owner role membership to the user database which grants the ALTER permission on the database, the following is being generated in the error log when they get to this step on the intended Mirror instance after restoring the database correctly in preperation:
SqlDumpExceptionHandler: Process 59 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. * ******************************************************************************* * * BEGIN STACK DUMP: * 10/29/15 11:16:15 spid 59 * * * Exception Address = 00007FF9A6AF838C Module(sqlmin+000000000003838C) * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION * Access Violation occurred reading address 00000000000000D8 * Input Buffer 210 bytes - * alter database <redacted> set partner = '<redacted>';
As you can see, the statement is denied to the user. There are no issues with the database as I am able to run the same query successfully using my own sysadmin account after the failed attempt. What other minimum permissions the group might need to successfully enable them to setup a mirroring session?
I'm making a copy of some tanles between 2 servers.
Server 1 requires a sql login
Server 2 is using Windows Auth.
I have a user on server 1 named "odbc" able to log in.
however my copy task fails, when I drill the error, it's lists the first user in server 1 alphabetically as the failed login???? but in my dts I am specifying the "odbc" user and password.
I think I have a permissions problem on server 1. So my Question, what minimum permissions does user "odbc" need to copy a table?
On server 1 I can copy from northwind to server 2 just fine..but any other db on server 1 causes the weird failure with the wrong username.
Error at Text Inbound Task [SQL Server Destination [9]]: The AcquireConnection method call to the connection manager "Server.Northwind" failed with error code 0xC0202009. Error at Text Inbound Task [DTS.Pipeline]: component "SQL Server Destination" (9) failed validation and returned error code 0xC020801C.
Please keep me posted with alternate work around(s) /solution(s).
Hi All, I am getting the following error if I am using the package "Transaction Option=Required" while running through Sql Job: The AcquireConnection method call to the connection manager "<connection name>" failed with error code 0xC0202009.
while I running the SSIS package on BI environment, I am getting the following error: [Connection manager "<connection name>"] Error: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction.".
I know the alternative solution is to make the "Transaction Option=Supported", but in my case I have run the whole flow in a single transaction. I came to know that this has been fixed in the service pack1(ref. to http://support.microsoft.com/kb/914375). FYI.. some time it was running successful.
I have taken all the necessary step to run the SSIS package in a distributed transaction(like the steps for MSDTC) and also created the package flow in a sequence.
I was going through the link - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=160340&SiteID=1 but all those didn't solve my problem.
If anyone can help me it will be great. or it is a bug in SSIS?
I am struggling with this error and it's starting to get to me!
I have setup a simple project with just a data flow task. In this task, it retrieves a simple record "Select * From Table1 WhereId=1". The connection is an OLE Db connection using Advantage Oledb Provider (a provider for accessing dBase). It is accessing a Novell network drive. I have setup the package to both "EncryptSensitiveWithPassword" and "DontSaveSensitive". Both times i have received this error.
The funny thing is, when I set the package to "EncryptSensitiveWithPassword" and I setup a job to run the package, it never asks me for the password even though I set one up! I have a previous package (few months ago I made) that accessed the same database on the same Network drive and it works! It also asks me for a password when I try to modify or run the package (b/c I set it to "EncryptW/Password").
I am using SSIS 2005 on Windows 2003 server. Using Excel Source to dump the data for staging database. I am getting following error while I execute it through BI studio's execute button.
I have deployed my packages into Sql Server and I am using Configuration File. As my Data Source is Excel, I have changed the connection string during deployment with Server Path. But I am getting the following errors. Actually the File Exist in Path. May I know What is cause of the issue? Do I need to give any permission to execute the package.
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
component "Excel Source Service Contract Upload" (1) failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
DTS_E_OLEDBERROR, Error Code: 0x80004005 Source: "MS JET DB Engine" Description : Path is not valid
Does anyone have any experience with this object, or any working examples, I suspect I'm still missing some permissions thing but at the moment all I get is this annoyingly unhelpful message:
Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'. The request failed with the error message: --
BODY {font-family:Verdana;font-weight:normal;font-size:8pt;color:black;} H1 {font-family:Verdana;font-weight:700;font-size:15pt;} LI {font-family:Verdana;font-weight:normal;font-size:8pt;display:inline;} .ProductInfo {font-family:Verdana;font-weight:bold;font-size:8pt;color:gray;} A:link {font-size:8pt;font-family:Verdana;color:#3366CC;text-decoration:none;} A:hover {font-size:8pt;font-family:Verdana;color:#FF3300;text-decoration:underline;} A:visited {font-size:8pt;font-family:Verdana;color:#3366CC;text-decoration:none;}
Reporting Services Error
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help
For more information about this error navigate to the report server on the local server machine, or enable remote errors