Databases
StackOverflow2013
Postsdbo
POSSIS error with xp_cmdshell
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSSIS error with xp_cmdshell
    primarykey
    data
    text
    <p>I'm new to a project and created a new SSIS package. When I execute the package by double-clicking it, it works. When I type into the shell:</p> <pre><code>dtexec /F "D:\path\to\my\ssis\package\mypackage.dtsx" /SET \Package.Variables[User::MyVariable].Properties[Value];"10" </code></pre> <p>It works also. But when I run my Stored Procedure which has the following code:</p> <pre><code>EXEC xp_cmdshell 'dtexec /F "D:\path\to\my\ssis\package\mypackage.dtsx" /SET \Package.Variables[User::MyVariable].Properties[Value];"10"' </code></pre> <p>It fails. The error has the source: mypackage Connectio manager "my connection manager" Desc: "Login failed for user 'myUser'." 'myUser' has rights to execute xp_cmdshell. It is the proxy user. Oddly enough, I can execute other packages without any problems, just this one doesn't work. Any idea what I'm missing? (BTW: all Packages have DontSaveSensitive protection level)</p> <p>Here the full error message, any ideas?</p> <pre><code>Elapsed: 0.296 seconds Finished: 10:33:44 Started: 10:33:44 DTExec: The package execution returned DTSER_FAILURE (1). End Warning d in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specifie Source: csv_v1_import_package Code: 0x80019002 Warning: 2013-07-18 10:33:44.60 End Error Description: Failed to acquire connection "My Connection Manager". Connection may not be configured correctly or you may not have the right permissions on this connection. Source: Update MyTable SQL Code Execute SQL Task Code: 0xC00291EC Error: 2013-07-18 10:33:44.60 End Error An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E4D Description: "Login failed for user 'MY_SERVER\username'.". Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. Source: csv_v1_import_package Connection manager "My Connection Manager" Code: 0xC0202009 Error: 2013-07-18 10:33:44.60 Started: 10:33:44 NULL Copyright (C) Microsoft Corporation 2010. All rights reserved. Version 10.50.4000.0 for 64-bit Microsoft (R) SQL Server Execute Package Utility </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBaseBallBatBoy
    1. USBaseBallBatBoy
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI found my problem. In the package I actually use a data source as my connection manager (yellow container with 4 blue arrows). I switched to use a real connection manager (yellow container) and then it works all fine...
      singulars
      1. POSSIS error with xp_cmdshell
      1. USBaseBallBatBoy
    2. COpossible duplicate of [Passing a variable through DTEXEC with xp\_cmdshell (SQL Server 2008)](http://stackoverflow.com/questions/10982780/passing-a-variable-through-dtexec-with-xp-cmdshell-sql-server-2008)
      singulars
      1. POSSIS error with xp_cmdshell
      1. USbillinkc
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload