SSIS Sql Agent Run As Proxy Error
May 29, 2008
I'm attempting to run a ssis package via sql server agent.
The package and the DB are on a cluster.
The package runs fine when 'Sql Server Agent' is the run-as.
When I try and use a proxy to run the package, it fails with this error:
Date 5/28/2008 6:21:54 PM
Log SQL Agent (Current - 5/28/2008 6:21:00 PM)
Message
[136] Job CorpFoo New reported: The process could not be created for step 1 of job 0xDAE2A53F27943D4CA412A0D177CAA546 (reason: A required privilege is not held by the client)
I've:
Create Credential to be used by proxy
Create Proxy
Give Permissions to Proxy in SQL Server
Give Permissions to Proxy at the Server for SQL Agent Batch Run
Give Permissions to Proxy at the Server to Connect to SSIS
EXEC dbo.sp_grant_login_to_proxy
@login_name = N'Myapplication_DBO',
@proxy_name = N'Myapplication_Batch_PROXY' ;
EXEC dbo.sp_grant_proxy_to_subsystem
@proxy_name = 'Myapplication_Batch_PROXY',
@subsystem_id = 11;
I've tried a number of things, including adding the sql user (who has access to the proxy) as sys admin on SQL and the OS. That didn't help either.
Has anyone experienced this error? Is there any way to further diagnose this (completely unhelpful) error message?
Thanks,
Steve.
View 2 Replies
ADVERTISEMENT
Feb 13, 2008
Hello!
I have SSIS Package that needs special permissions in network. I want to schedule SSIS running using SQL Agent. I don't want to other Jobs starts with special permissions. So, I decided to use proxy account to impersonate SSIS starting process by account with those permissions. I've perfomed following steps:
1. Create Login for the future proxy account and add it to sysadmins role.
2. Create Credential with account name and password information.
3. Create proxy account and give to it rights to run SSIS, CmdExec and ActiveX create.
4. Set Run as for step that starts my package to this proxy
5. Start my job.
and I receive error "Process couldnot be created for step 1 job xxx. Reason: 1314"
SQL Agent account and proxy accounts has also administrators rights on SQL Server computer and rights to login as service.
When I change step configuration to run as SQL Agent account job completes succesfull.
What do I do wrong?
Thx,
Olga
View 8 Replies
View Related
Mar 6, 2008
I had a question about proxy account for ssis.
Is it necessary to set up credential with windows account for proxy account so that ssis package can be setup as a job in agent ?
without proxy account ssis package is unable to run under agent as a job ..but..
does identity in credential for proxy need to be windows account ?
View 4 Replies
View Related
May 15, 2007
I have read all the posts regarding this error, but non-solve my problem as I had already addressed them.
I am setting up Merge Replication via the Web and I get this error when i try to sync. Let me give you some background.
I wrote a small windows test app to test merge replication, in which i am using RMO to accomplish the replication. This works. It syncs every time. I then copied the "sync" code from the winform application and created a Windows Service in which i placed "sync" code. The sync code did not change other than adding the additional following four lines:
_mergeAgent.InternetUrl = _internetURL;
_mergeAgent.InternetLogin = _internetLogin;
_mergeAgent.InternetPassword = _internetPassword;
_mergeAgent.InternetTimeout = _internetTimout;
where the internet url is https://ipaddress/virtualdirectory/replisapi.dll
I have been working with this for a while now trying to figure out why this works (on the same machine) in a winforms app but not through the web (via a windows service).
Any insight would be greatly appreciated.
Thanks...
View 3 Replies
View Related
Jul 21, 2006
My proxy class returns web service responses well if I use it in a C# code.
I compile it with CSC and put it in GAC to use it with SSIS.
Then I get web service response with some field values populated with "Exception of type :{System.InvalidOperationException "' occured.
Here is the part of web service response received by the C# program:
Name
Value
Type
mainAddress
{Address}
Address
city
Metuchen
string
cityField
Metuchen
string
country
USA
Country
countryField
USA
Country
state
NEW_JERSEY
State
stateField
NEW_JERSEY
State
Here is the same object returned by compiled dll used in SSIS:
mainAddress
{BrokerConnectServiceV1.Address}
BrokerConnectServiceV1.Address
city
Metuchen
String
country
{System.Nullable(Of BrokerConnectServiceV1.Country)}
System.Nullable(Of BrokerConnectServiceV1.Country)
HasValue
FALSE
Boolean
Value
Exception of type: '{System.InvalidOperationException}' occurred.
BrokerConnectServiceV1.Country
Data
{System.Collections.ListDictionaryInternal}
HelpLink
Nothing
InnerException
Nothing
Message
Nullable object must have a value.
Source
mscorlib
StackTrace
at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
at System.Nullable`1.get_Value()
TargetSite
{System.Reflection.RuntimeMethodInfo}
state
{System.Nullable(Of BrokerConnectServiceV1.State)}
System.Nullable(Of BrokerConnectServiceV1.State)
HasValue
FALSE
Boolean
Value
Exception of type: '{System.InvalidOperationException}' occurred.
BrokerConnectServiceV1.State
Below is another posting by my associate on the same issue :
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=536615&SiteID=1
Any help is appreciated....
View 11 Replies
View Related
Sep 26, 2006
I seem to be having issues getting some of our SSIS packages to work with proxy accounts
The package is a simple pull from an access db into a sql table. The package encryption is set to EncryptAllWithPassword. The .dtsx file and the access db are both on local drives and do not have restrictive permisssions.
The package runs fine under the dev studio as well as from the command line on the server while logged in with the domainSqlJobs account. But attempting to execute the job from the Sql Agent using a using a proxy account fails, giving the following error information.
The AcquireConnection method call to the connection manager "test" failed with error code 0xC0202009.
component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
The SSIS service is running under the domainSqlServiceP account.
So here is what I have done....
I have created a login, credential, and proxy for the domainSqlJobs account. The SqlJobs proxy has been assigned principals to the desired login accounts and was assigned as the Run As account in an execute SSIS package step of a Sql Agent Job. With the proxy in place the job fails if started manually from the Managment Studio, or scheudled, no matter what account kicks off the job.
Logging in as an admin and changing the step to execute under the Sql Agent Service Account will allow the job to be run successfully, but I would rather not have to manage all of our developers jobs or elevate their rights. Using the same proxy as before, but changing the step to a cmdexec gives the same error as above. The proxy will execute SSIS packages that do not involve an access db data source
again...Logging in directly to the server with the proxy account and running the package from the command line does work...
Am I missing something?
View 1 Replies
View Related
Jan 11, 2008
Hi,
I am having problems with an SSIS package whereby the first step of the package is failing. I am getting the following error message:
Unable to connect to FTP server using "FTPLocation".
This only happens when I use a Agent Proxy as the 'Run as' option. If I change it back to SQL Agent Service Account it works perfectly.
For the credentials of the proxy, I have used my own windows login as the identity. And I have full priveleges on the server, ie if I log on to the server I can successfully ftp to the same site and download the file without any problems. So shouldn't the Agent be able to do so too when it uses my credentials?
Any help would be much appreciated.
DrBrain
View 3 Replies
View Related
Mar 13, 2008
to DTEXEC from a agent job , what will be the permissions that are needed ?
I guess that can be SQL Server login with admin permissions will be fine and we don't need a proxy setup.
View 1 Replies
View Related
Mar 14, 2008
Hi there,
I hope I'm posting this in the right section but I have a few SSIS packages that run as SQL Agent jobs that bomb out and does not give me much of a description as why it did. I only get a message that the package failed.
On a different machine, a sql cluster more specific, the job history use to be more elaborate and told me exactly which component errored out.
Is there a setting that I must set somewhere to get a more descriptive error message in the job history?
Thanks in advance
Mike
View 10 Replies
View Related
Sep 5, 2007
I have a SSIS package that reads from a remote directory on another server that is on the same domain. When I run the package under my domain user, it runs fine, however when I try to start the SQL job which has the package as the first step, the job fails. I created a proxy account with domain user credentials, set it to be active under "SSIS Package Execution" and set the SSIS package to run as the proxy account, but I get the following error message:
"Unable to start execution of step 1 (reason: Could not get proxy data for proxy_id = 2). The step failed."
I'm not sure what to do at this point, so any help would be appreciated.
View 8 Replies
View Related
Aug 3, 2006
I am trying to
copy a database from our company's external SQL
Server(production) to our local SQL
Server(development). The Copy Database wizard fails on the step
"Execute SQL Server Agent Job".
Following is the error in the log file.. Please advise
InnerException-->An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
View 7 Replies
View Related
Apr 15, 2008
do sqlagent service account proxies need more than just permissions on the app databases being read from and written to in the executing ssis package?
it looks like there are some prep steps when a pkg is going to be run. In my case, the pkg comes from msdb which has it's own security roles. So will my proxies need "datareader" permission on msdb...in addition to datareader and datawriter permissions on the other databases the pkg reads/writes from/to?
are there other permissions/roles normally important to proxies used in getting ssis pkgs to run? Where are they set?
View 7 Replies
View Related
Aug 17, 2006
I have an SSIS package that runs fine through command pormpt although when I try to run it from a SQL Servr Agent Job CmdExec step it bombs out. Please help this has me stumped...the SSIS package uses an XML connection string so certain key settings such as connection strings and email info can be changed easily. Currently this is all on the same machine. I have not moved it beyond where I am developing.
On the command line I am using the following command...
dtexec /F "S:connectionscontacts.dtsConfig" /DE "password"
Below is the output log...
Microsoft (R) SQL Server Execute Package Utility
Version 9.00.1399.06 for 32-bit
Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 6:59:40 PM
Progress: 2006-08-16 18:59:41.29
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.29
Source: Data Flow Task
Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.71
Source: Data Flow Task
Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.73
Source: Data Flow Task
Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.77
Source: Data Flow Task
Validating: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.79
Source: Data Flow Task
Prepare for Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.81
Source: Data Flow Task
Pre-Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.84
Source: Data Flow Task
Pre-Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.90
Source: Data Flow Task
Pre-Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.90
Source: Data Flow Task
Pre-Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Post Execute: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.92
Source: Data Flow Task
Cleanup: 0% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 33% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 66% complete
End Progress
Progress: 2006-08-16 18:59:41.93
Source: Data Flow Task
Cleanup: 100% complete
End Progress
Progress: 2006-08-16 18:59:41.95
Source: Send Mail Task
The SendMail task is initiated.: 0% complete
End Progress
Progress: 2006-08-16 18:59:42.09
Source: Send Mail Task
The SendMail task is completed.: 100% complete
End Progress
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 6:59:40 PM
Finished: 6:59:42 PM
Elapsed: 1.984 seconds
When I try to use the same command within SQL Server Agent Job using a CmdExec step I get the following error...
Description: The package is attempting to configure from the XML file "S:connectionscontacts.dtsConfig". End Info Warning: 2006-08-16 18:40:03.15 Code: 0x80012012 Source: contactsPackage Description: The configuration file name "S:connectionscontacts.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2006-08-16 18:40:03.15 Code: 0x80012059 Source: contactsPackage Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Info: 2006-08-16 18:40:03.20 ... Process Exit Code 1. The step failed.
Thanks in advance for any help!!!
View 2 Replies
View Related
May 29, 2008
Hi There
We executed windows scheduled batch failes that execute as DOMAINuser1 to dtsexec packages.
I moved these packages to run in sql jobs.
The agent runs as local system. In order to get the packages to run since they are encryoted with DOMAINuser1 key.
I created a DOMAINuser1 credential and a proxy.
I execute the SSIS package job steps under this proxy.
One day it all works the next day they fail randomly with the "unable to decrypt with user key" error.
I am very familiar with this error, however it makes no sense, thses packges are not being touched, no one is altering them and perhaps saving them with different user keys. They are all encrypted with the DOMAINuser1 key. One day everything works the next day they fail.
A master package will run and in the middle of executing other package it suddenly gets this error, like the proxy suddenly stops working.
I have found nothing in the event logs?
Any ideas ?
View 6 Replies
View Related
Dec 7, 2006
Hello,
I have a problem running a Package stored in the msdb datatabase (The
Database Engine is configured as a 1 node cluster) using a SQL Job that uses
Creadential/Proxy
Every time I try to run the SQL Job, it fails with the following error
message:
Unable to
start execution of step 1 (reason: Error authenticating proxy
MydomainMyaccount, system error: Logon failure: unknown user name or bad
password.). The step failed.".
The package runs perfectly if I run it logged as MydomainMyaccount ussing
DTExec.exe from the command line. if I run the sql job as "SQL Agent Service
Account" instead of using a proxy, it works great, but if I use the same
account as a credential, the sql job fails.
In other offices I have the same scenario in a non-cluster environment
running without any problems, (Also one with a 2 node cluster)
I am using Windows 2003 with SP1 and SQL 2005 SS with SP1 (build 2056)
Any idea?
Thanks in Advance Javier VillegasMediterranean Shipping Companyjvillegas@msc.us
View 9 Replies
View Related
Jun 8, 2006
(Posting this again since my original post has disappeared from the forum sometime during the day.)
I have about a dozen jobs that are being started at the same time (1:30am). Each time they start up, I end up with a random number of those jobs failing to run and logging the follow error:
Unable to start execution of step 1 (reason: Error authenticating proxy LSPJobUser, system error: Logon failure: unknown user name or bad password.). The step failed.
Each night it is a different collection of failed jobs (some work and some do not). If I manually run the job they ALL work EVERY time.
As anybody experienced this before? Is it possible that SQL Agent cannot handle a dozen jobs at once? (Or at a minimum cannot authenticate a dozen jobs at once.) (I do not believe it but cannot think of any other possibility.)
(For a quick fix I am going to stagger the dozen jobs to start over a ten minute period instead of starting at the same time.)
- Jason
View 4 Replies
View Related
Aug 3, 2005
I'm trying to set a proxy account for the SQL agent. The user is Local
administrator on the SQL Server when I try to set the account I get a message back that says
"The system cannot find the path specified."
I get the same error with TSQL too.
EXEC master..xp_sqlagent_proxy_account
'SET', N'MY_DOMAIN', N'Myadm', N'MyPassword'
My system :
Windows Server 2003 SP1
SQL Server 2000 SP4
I am worried it might be interfering with someing.
Any ideas what paths it could be after?
View 5 Replies
View Related
Jun 16, 2015
I running SSIS package job without sql agent , it is working fine.when i am running through sql agent not running.
created Proxy accountÂ
job failed and give above error.
Server is cluster and taking data from desktop.
server is in one domain and desktop in another domain.
View 3 Replies
View Related
Feb 5, 2008
Hello,
I am trying to create a job that runs a SSIS package. I am getting the following error:
Message
Unable to start execution of step 1 (reason: Error authenticating proxy domainsckeels, system error: Logon failure: unknown user name or bad password.). The step failed.
Our DBA ran the following to create the credentials and proxy account.
USE MSDB
CREATE CREDENTIAL [sckeels] WITH IDENTITY = 'domainsckeels', secret = 'sckeels_credentials'
GO
Sp_add_proxy @proxy_name='ssis_users', @credential_name='sckeels'
GO
Sp_grant_login_to_proxy @login_name='domainsckeels', @proxy_name='ssis_users'
GO
Sp_grant_proxy_to_subsystem @proxy_name='ssis_users', @subsystem_name='SSIS'
Any help with this would be appreciated.
Steven
View 7 Replies
View Related
Feb 6, 2006
I have been attempting to create a snapshot of a database. Just install a SQL2005 cluster. The snapshot appears to create ok, but when I view snapshot agent status I get the following error which I have not been able to figure out:
Unable to start execution of step 2 (reason: Error authenticating proxy ohaevservices, system error: Logon failure: unknown user name or bad password.). The step failed.
This account has admin and dbowner --- Help
View 15 Replies
View Related
Sep 18, 2007
Hi all,
I have a problem while i create a proxy account.The situation is like this...There is a user who has an login in to the server.He has a stored procedure which calls some on the SSIS packages and XP_cmdshell...so this stored procedure basically load some data in to the tables .So for the login in order to execute the stored procedure as he is not a Sys admin I have created a proxy account in my account as Iam an SA and then in the proxies and in principals I selected his login name and this way I have created a credential and a proxy account.
Now the problem is if he logins with his id and password and try to execute the stored procedure it gives an error message
Server: Msg 15153, Level 16, State 1, Procedure xp_cmdshell, Line 1
The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the '##xp_cmdshell_proxy_account##' credential exists and contains valid information.
....so this mean the login is not able to see the proxy account.So what I did is I created a job and then in the job owner tab I have selected his login and then created a step with the type operating system (CmdExec) as I need to just execute the stored procedure and used the proxy account that I have created.
so I gave the command -- exec <stored procedure> --.
But this job fails and gives the error message as
[298] SQLServer Error: 536, Invalid length parameter passed to the SUBSTRING function. [SQLSTATE 42000]....
So now ....first My question is am I doing in a right way....if its right then why Iam not able to execute the stored procedure.
If there is any other way through which I can execute the stored procedure using a proxy account for the logins who are not sys admins....please do let me know.....
Thanks
Raja.V
View 2 Replies
View Related
Jan 11, 2007
Hello Experts,
I have a Report Server when i try to deploy my report on the same server and if i use the Fully Qualified Domain Name in my report path i get the below Error
TargetServerURL : http://jptoclq901.corpusers.net/ReportServer
Error : The request failed with HTTP Status 407 : Proxy Authentication Required (Microsoft.ReportingServices.Designer)
but if i use the TargetServerURL as http://localhost/ReportServer, things do work fine. but company requirement is to use complete path.
Is this a limitation or some way out, any Idea???
Thanks in advance for the help
/Soni
View 1 Replies
View Related
Oct 29, 2007
I have an SSIS package (TransAgentMaster) that I recently modified to include a call to a child package via the file system. The child package creates a text file. When I run the package in dev studio then the child package/text file is produced.
I then imported the TransAgentMaster as a stored packagesfilesystem package into SQL SSIS and executed the package. The child package produced the text file.
I then ran the SQL Server Agent to see if the child package would work and it did not generate the text file. Thus after updating a SSIS package importing the package into SSIS the job that calls the package will not call the child package. Please not that the TransAgentMaster package calls 7 children packages €¦ just not my new one.
Any thoughts why the agent will not run the child newly crated childe package?
View 3 Replies
View Related
Jan 4, 2007
Phil writes "Hi,
Here is my dilemma. I would like to create an SSIS package that will dynamically run different scripts/reports for my company. I would like to use one SSIS package and then dynamically create the jobs based on the schedule of when these scripts should run. For instance, if I have two scripts that create excel documents that run at 2:00 P.M daily I would like to use the job agent and have both of these scripts start at 2:00 PM. Instead of having one run and then the other has to wait until it's complete. First of all, is this even possible? Second has anybody ever played around with this and if so can you give me some guidance?
Thanks,
Phil"
View 2 Replies
View Related
May 22, 2002
I get this error in my Agent after starten to synchronise.
I see the access mdb been created and then deleted and renamed to
name_old.mdb
Do you have some help?
Richard
View 1 Replies
View Related
Jan 29, 2008
I have a really odd one here. We have a production server which is running SQL 2000 Enterprise Edition SP3. It has a number of databases which are backed up nightly. Last night all of the back-up jobs failed with the following error: -
Msg 913, Sev 16: Could not find database ID ##. Database may not be activated yet or may be in transition. [SQLSTATE 42000]
The databases are in good shape - no issues to report. When I run the Agent Job code within a Query Analyser session it works fine.
When I try and re-start the back-up from the Agent Job it continues to fail with the same error.
Any ideas?
View 2 Replies
View Related
Mar 31, 2008
Hello all,
I have designed a SSIS Package. The process of SSIS package is import the data from Excel sheet daily. The package is working fine. When I run from SQL agent job, it is continuously failing. I have created credentials, proxy and I have mapped it. I am doing this process by remote desktop connection. I red lot of articles, nothing was helped me. I hope I will get a solution over here!!
Thanks
Krishna
View 20 Replies
View Related
May 5, 2006
Hi,
Can we allow SSIS to be scheduled via SQL Agent. Is there any security concerns.
Thanks & Regards
Shri.DBA
View 4 Replies
View Related
Oct 27, 2007
Is there a detailed, step by step manual that explains how to set this up?
I can run the package from SSIS but the process to set this up from the job agent is really murky mostly from a security standpoint of setting up user/proxy etc
So I need a cookbook with nice clear explanations
Does one exist?
Thanks
JPS
View 1 Replies
View Related
Aug 29, 2007
I've seen many postings on various forums on how to get SQL agent to execute an SSIS package. I have one that was originally created via the import wizard in SSMS, later modified in VS2005, and then re-imported in SSMS using the Object Explorer interface to load the dtsx file into SQL storage. I've tried several package protection options when importing the package: "Don't save sensitive data" (the package has no passwords in it), server storage and roles, and a specified package password (which I entered as a /DECRYPT command line parameter in the Agent job step). Agent is running using a domain admin account. No matter what I've tried, I still get an error during job execution that it failed to decrypt the password XML node. The package runs just fine when executed manually in the SSIS Object Explorer.
How can I resolve this?
View 6 Replies
View Related
Feb 22, 2008
We are just migrating to sql servr 2005. I have created ssis pkg that runs fine when run mnaulli under BI. However, when I setup the ssis pkg to run as a SQL job. It errors out. Err is listed below. Seems like it is running the job under the SQL Agent account which does not have permissions to access the server i am pulling data from. Can u assit.
1984-2005. All rights reserved. Started: 1:30:51 PM Progress: 2008-02-22 13:30:57.55 Source: DTSTask_DTSDataPumpTask_1 Validating: 0% complete End Progress Error: 2008-02-22 13:30:58.33 Code: 0xC0202009 Source: Laser- Connection manager "FTWSQL" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E4D Description: "Login failed for user 'CFC 0SQLA'.". End Error Error: 2008-02-22 13:30:58.33 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "FTWSQL" failed with error code 0xC0202009. There m... The package execution fa... The step failed.
View 4 Replies
View Related
Feb 25, 2006
I need to pass a value to a package level variable in an SSIS package from a SQL Agent job. If I use dtexecui the syntax for passing the variable in the Property Path is
Package.Variables[User::MyVar].Properties[Value]
and the package runs fine.
When I use this syntax, or any similar format I can think of, in SQL Agent, my job fails. In SQL Agent you put this in the Property Path on the Set Values tab of the Step that runs the package. If I remove passing in the variable my package runs fine.
BOL says use the format Package<container name>.<property name> but I can find no examples. Can anyone provide a working sample to make this work?
Thanks.
View 4 Replies
View Related