Errors running SQL Agent Jobs for 64 bit SSIS packages on a 64 bit server, but Source server 32 bit

Hi,
I can able ran the SSIS package in BIDS, since set to false in Run64BitRuntime property.
Then I created SQL server Agent job I tried the following ways
Step 1:
Type is set as SQL Server Integration Services Packages,
Run as - SQL Server Agent Service Account
Package source - FileSystem
then Execution option tab I selected 32 bit runtime
and then run the job I am getting the below error
Message
Executed as user: CIT\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 7:29:17 AM Error: 2013-11-28
07:29:18.57     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 07:29:18.57
Code: 0xC0014009     Source: Imports20_OAC_Gifts Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the
database server. End Error Error: 2013-11-28 07:29:18.59     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection
manager DataSource.DataExtract failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 07:29:18.59
Code: 0xC0047017     Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-2
Step 2:
Type - Operating sytem (CmdExec)
Run as - Sql Server agent service account
Command - C:\Program Files\Microsoft SQL Server\110\DTS\Binn\dtexec.exe /FILE "D:\Example\Example.dtsx" /x86 /CHECKPOINTING OFF /REPORTING E
then run the job I am getting the below error
Message
Executed as user: MIS\svc_CS_SS2008Agent. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved.    Started: 6:37:58 AM Error: 2013-11-28
06:37:58.94     Code: 0xC0014020     Source: Example Connection manager "DataSource.DataExtract"     Description: An ODBC error -1 has occurred. End Error Error: 2013-11-28 06:37:58.96
Code: 0xC0014009     Source: Example Connection manager "DataSource.DataExtract"     Description: There was an error trying to establish an Open Database Connectivity (ODBC) connection with the database server.
End Error Error: 2013-11-28 06:37:59.01     Code: 0x0000020F     Source: DFT_Example ODBC_SRC Example [11]     Description: The AcquireConnection method call to the connection manager DataSource.DataExtract
failed with error code 0xC0014009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2013-11-28 06:37:59.07     Code: 0xC0047017
Source: DFT_Example SSIS.Pipeline     Description: ODBC_SRC Example failed validation and returned error code 0x80004005. End Error Error: 2013-11-28 06:37:59.12     Code: 0xC004700C
Source: DFT_Example SSIS.Pipeline     Description: One or more component failed validation. End Error Error: 2013-11-28 06:37:59.16     Code: 0xC0024107     Source: DFT_Example
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1).Started: 6:37:58 AM Finished: 6:37:59 AM Elapsed: 1.373 seconds. Process Exit Code 1.
The step failed.
Note:
My source server is 32 bit and development environment in 64 bit
if anybody have idea please share your knowledge

Hi BIRam,
Based on the current information, the issue may be caused by the factor that the SQL Server Agent Service Account doesn’t have access to the MySQL server. Try to create a SQL Server Agent Proxy account that has sufficient permission on the MySQL server.
In addition, also pay attention to the package protection level setting.
For more information, please see:
http://social.technet.microsoft.com/Forums/sqlserver/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job?forum=sqlintegrationservices.
Regards,
Mike Yin
TechNet Community Support

Similar Messages

How to Create a SQL Agent Job For A SSIS Package with Sql Server Authentication

Hi ALl,
I have a SSIS package which basically has a data flow task in which i pull the data from one server and copy it into another server and my source server is the one where i dont have windows authentication and i have to only use a sql server authentication
. This package runs fine if i click the server connection properties type the password and save it.
Now, my task is to set up a sql agent job which basically uses a proxy account and takes this package from the file system and runs it.But when i try to run this package, its failing with an error saying
"Login Failed For rpt5user" where rpt5user is the username for my sql server authentication of the source connection.
Can someone please help me with any suggestions on how to do this?
I have heard that we can achieve it by using xml config file which i have never used and i am trying to google around but for no luck.
So, If someone can please throw any suggestions or ideas on this it would be great.
Thanks

You need to add password as a config item and set it from the file source or sql table
see this as an example
http://blogs.msdn.com/b/runeetv/archive/2009/12/22/ssis-package-using-sql-authentication-and-dontsavesensitive-as-protectionlevel.aspx
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

List of SQL server Agent jobs for a SSIS package

Hello everyone,
Can you please help me in trying to list all the jobs that have a particular ssis jobs. I saw that all the jobs and jobs steps with the query:
SELECT
   Srv.srvname AS ServerName,
   Job.name AS JobName,
   JStep.step_id,
   JStep.step_name AS StepName,
   JStep.command,
   Job.enabled
FROM   dbo.sysjobs Job
JOIN   dbo.sysjobsteps JStep
   ON JStep.job_id = Job.job_id
JOIN   MASTER.dbo.sysservers Srv
   ON Srv.srvid = Job.originating_server_id
--WHERE JStep.subsystem='SSIS'
WHERE    JStep.step_name = <Job_step_name>
And also found sysssispackages table for all ssis packages. But I am not sure how to link the package to job. Please help me.
Thanks in advance.

Try this:
USE MSDB
GO
SELECT
sj.job_id as JobId,
sj.name as JobName,
sjs.step_name as StepName,
sjs.Command as Command
FROM sysjobs sj
INNER JOIN sysjobsteps sjs
    ON(sj.job_id = sjs.job_id)
    WHERE sjs.subsystem = 'SSIS'
GO
or here is an
article that uses PowerShell
Andy Tauber
Data Architect
The Vancouver Clinic
Website | LinkedIn
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Is there a way to get long running SQL Agent jobs information using powershell?

Hi All,
Is there a way to get long running SQL Agent jobs information using powershell for multiple SQL servers in the environment?
Thanks in Advance.
--Hunt

I'm running SQL's to fetch the required details and store it in centralized table.
foreach ($svr in get-content "f:\PowerSQL\Input\LongRunningJobsPowerSQLServers.txt"){
$dt = new-object "System.Data.DataTable"
$cn = new-object System.Data.SqlClient.SqlConnection "server=$svr;database=master;Integrated Security=sspi"
$cn.Open()
$sql = $cn.CreateCommand()
$sql.CommandText = "SELECT
@@SERVERNAME servername,
j.job_id AS 'JobId',
name AS 'JobName',
max(start_execution_date) AS 'StartTime',
max(stop_execution_date)AS 'StopTime',
max(avgruntimeonsucceed),
max(DATEDIFF(s,start_execution_date,GETDATE())) AS 'CurrentRunTime',
max(CASE WHEN stop_execution_date IS NULL THEN
DATEDIFF(ss,start_execution_date,stop_execution_date) ELSE 0 END) 'ActualRunTime',
max(CASE
WHEN stop_execution_date IS NULL THEN 'JobRunning'
WHEN DATEDIFF(ss,start_execution_date,stop_execution_date)
> (AvgRunTimeOnSucceed + AvgRunTimeOnSucceed * .05) THEN 'LongRunning-History'
ELSE 'NormalRunning-History'
END) 'JobRun',
max(CASE
WHEN stop_execution_date IS NULL THEN
CASE WHEN DATEDIFF(ss,start_execution_date,GETDATE())
> (AvgRunTimeOnSucceed + AvgRunTimeOnSucceed * .05) THEN 'LongRunning-NOW'
ELSE 'NormalRunning-NOW'
END
ELSE 'JobAlreadyDone'
END)AS 'JobRunning'
FROM msdb.dbo.sysjobactivity ja
INNER JOIN msdb.dbo.sysjobs j ON ja.job_id = j.job_id
INNER JOIN (
SELECT job_id,
AVG
((run_duration/10000 * 3600) + ((run_duration%10000)/100*60) + (run_duration%10000)%100)
+
STDEV
((run_duration/10000 * 3600) + ((run_duration%10000)/100*60) + (run_duration%10000)%100) AS 'AvgRuntimeOnSucceed'
FROM msdb.dbo.sysjobhistory
WHERE step_id = 0 AND run_status = 1
GROUP BY job_id) art
ON j.job_id = art.job_id
WHERE
(stop_execution_date IS NULL and start_execution_date is NOT NULL) OR
(DATEDIFF(ss,start_execution_date,stop_execution_date) > 60 and DATEDIFF(MINUTE,start_execution_date,GETDATE())>60
AND
CAST(LEFT(start_execution_date,11) AS DATETIME) = CAST(LEFT(GETDATE(),11) AS DATETIME) )
--ORDER BY start_execution_date DESC
group by j.job_id,name
$rdr = $sql.ExecuteReader()
$dt.Load($rdr)
$cn.Close()
$dt|out-Datatable
Write-DataTable -ServerInstance 'test124' -Database "PowerSQL" -TableName "TLOG_JobLongRunning" -Data $dt}
You can refer the below link to refer out-datatable and write-dataTable function.
http://blogs.technet.com/b/heyscriptingguy/archive/2010/11/01/use-powershell-to-collect-server-data-and-write-to-sql.aspx
Once we've the table details, I'm sending one consolidated email to automatically.
--Prashanth

Running SQL agent jobs in parallel

I have around 60 SQL agent jobs (each job has 1 step that loads data from ORACLE to SQL using attunity) that run SSIS packages that I need to run in parallel. I did some testing and found that the server can handle 10 of them running at the same time.
I know I need to loop through sysjobhistory and find the ones (all 60 jobs start with PS) that haven't ran today, currently not running and the first tow words of the name = 'PS'. Any advice on how to get this accomplished would be appreciated.
I have seen some articles that mention adding 10 data flows to a SSIS package and run them that way but I would like for SQL to handle it, so I can get the time.
Thanks!

That will definitely help identify the jobs but I need to figure the looping logic that will allow 10 jobs to run in parallel.
try this.. not tested.. left comments where possible for you to understand..may need to tweak it a bit..
declare @a intset @a=0
declare @jobname nvarchar(200)
-- checks if there are already 10 jobs running
while (@a <10) and ((Select count(C.Name) as [JobName]
from (Select max(Session_id) as Session_Id from msdb.dbo.syssessions) A
INNER JOIN msdb.dbo.sysjobactivity B on A.Session_id=B.Session_ID
INNER JOIN msdb.dbo.sysjobs C on B.job_id=C.Job_ID
where B.stop_execution_date is null AND B.run_requested_date is not null and C.Name like 'PS%') < 10)
begin
--loops through to fetch one non-running job at a time and fetches upto 10 jobs
Select top 1 @jobName = name
from msdb.dbo.sysjobs X
INNER JOIN msdb.dbo.sysjobactivity Z on Z.job_id=X.Job_ID
where name like 'PS%' and
--checks the job is currently not running
name not in (
Select C.Name as [JobName]
from (Select max(Session_id) as Session_Id from msdb.dbo.syssessions) A
INNER JOIN msdb.dbo.sysjobactivity B on A.Session_id=B.Session_ID
INNER JOIN msdb.dbo.sysjobs C on B.job_id=C.Job_ID
where B.stop_execution_date is null AND B.run_requested_date is not null)
--makes sure the job already did not run today
and cast(Z.run_requested_date as date)<>cast(getdate() as date)
order by name
Execute msdb.dbo.sp_start_job @job_Name=@jobName
set @a=@a+1
End
Hope it Helps!!

Run SQL Agent Job in endless loop(When it's done, start over again)

Hi All,
There is an SQL Agent Job containing a complex Integration Services Package performing some ETL Jobs. It takes between 1 and 4 hours to run, depending on our data sources. The Job currently runs daily, without problems. What I would like to do now is to
let it run in an endless loop, which means: When it's done, start over again.
The scheduler doesn't seem to provide this option. I found that it would be possible to use the steps interface to go to step one after the last step is finished, but there's a problem using that method: If I need to stop the job, I would need to do that in
a forceful way. However I would like to be able to let the job stop after the next iteration. How can I do that?
Thanks in Advance...

Seriously I cant think of a reason for continuosly running a step like this
Do you mean you need to keep on polling db for something continuosly ?
If thats the requirement there's no need of continuosly calling the step
Instead of that you can include a loop with wait logic to keep on checking for your condition until it satisfies. You can WAITFOR clause for that
see an example here where I've implemented similar logic in SSIS
http://visakhm.blogspot.in/2011/12/simulating-file-watcher-task-in-ssis.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

[SQLSTATE 42000][Error 4834] - SQL Agent Job failing

Hello,
I have started getting the below error message on a bulk insert job that has been running over several months.
Error is:
Executed as user: domain\svc_sql. You do not have permission to use the bulk load statement. [SQLSTATE 42000] (Error 4834). The step failed.
Domain\svc_sql is also service account for SQL Server. Both the SQL server and SQL agent are running under this account and it has sysadmin and bulkadmin privileges.
Bulk insert is from csv file in a folder for which domain\svc_sql has full permission.
I've now ran out of ideas.
Could anybody advise?
Many thanks,
Mohan

Hi Mohan,
According to the error message, it can be caused by that when SQL Server Agent performs EXECUTE AS USER, you are by default sandboxed into the database, and therefore you don't have access to server-level tasks.
To work around the issue, as Praveen’s post, you can set the database TRUSTWORTHY to ON, however it might cause some security issues. For more details, please review this article:
Giving Permissions through Stored Procedures Ownership Chaining, Certificates and the Problematic EXECUTE AS.
Personally, I recommend you create the bulk insert job as a CmdExec job which uses SQLCMD to run scripts. For more information about CmdExec job, please review this article:
Create a CmdExec Job Step.
There is also a discussion about the error 4834 in the following thread.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/48621876-11a0-468c-95b4-2a682f0134aa/bulk-insert-not-working-through-an-agent-job
Thanks,
Lydia Zhang

How to schedule SQL Agent job for XMLA script file of SSAS database instead of taking a backup.

I want to script XMLA file instead of backup of database and also want to schedule a job for the process in SQL Agent.
Is there any pros and cons when I script the XMLA file of the SSAS db instead of taking a backup ?
Amir

Hi Amir,
You can take the Create SSAS database XMLA script and run the job to create the cube. The script contains the Metadata definition of the Database and it does not contain the actual data.
Pros: Since you are only creating an empty cube the script will run faster
Cons: You still need to process the created cube to use it for reports.
Fastest option is to take the backup of the cube and restore wherever necessary.
And you can also use TFS source control to deploy the cube and process it later.
Regards,
Venkata
Venkata Koppula

SQL AGENT JOB FOR DISK SPACE USAGE ALERT

Hello Experts
what is the best way to set up a disk space usage alert for my sql server 2008r2 databases. i want to get a notification or alert whenever the disk usage is >80%, thank you as usual.

Hi
You can use sql server job for same. I am using below procedure configured with sql job running every 15 mins
Example: EXEC [DBA_DiskSpaceMntr]
@mailto = 'team mail',
@CDrivethreshold = 1024,
@OtherDrivethreshold = 10240
CREATE PROCEDURE [dbo].[DBA_DiskSpaceMntr]
@mailto nvarchar(4000),
@CDrivethreshold INT,
@DDrivethreshold INT,
@YDrivethreshold INT,
@OtherDrivethreshold INT
AS
BEGIN
declare @count int;
declare @DiskFreeSpace int;
declare @tempfspace int;
declare @tempdrive char(1);
declare @mailbody nvarchar(4000);
declare @MailSubject nvarchar(1000);
declare @AlertMessage nvarchar(4000);
declare @altflag bit;
declare @sub nvarchar(4000);
declare @cmd nvarchar(4000);
set @count = 0;
SET @mailbody = '';
SET @cmd = '';
set nocount on
IF EXISTS(select * from sys.sysobjects where id = object_id('#driveinfo'))
drop table #driveinfo
create table #driveinfo(id int identity(1,1),drive char(1), fspace int)
insert into #driveinfo EXEC master..xp_fixeddrives
SELECT @DiskFreeSpace = fspace FROM #driveinfo where drive in ('C')
IF @DiskFreeSpace < @CDrivethreshold
Begin
SET @MailSubject = 'Drive C: free space is low on ' + cast(Serverproperty('Machinename') as nVarchar)
SET @mailbody = 'Drive C: on ' + cast(Serverproperty('Machinename') as nVarchar) + ' has only ' + CAST(@DiskFreeSpace AS VARCHAR) + ' MB left. Please free up space on this drive. '
--select * FROM #driveinfo where drive in ('L')
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'SQLDBA_Support',
@recipients= @mailto,
@subject = @MailSubject,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
End
SELECT @DiskFreeSpace = fspace FROM #driveinfo where drive in ('D')
IF @DiskFreeSpace < @DDrivethreshold
Begin
SET @MailSubject = 'Drive D: free space is low on ' + cast(Serverproperty('Machinename') as nVarchar)
SET @mailbody = 'Drive D: on ' + cast(Serverproperty('Machinename') as nVarchar) + ' has only ' + CAST(@DiskFreeSpace AS VARCHAR) + ' MB left. Please free up space on this drive. '
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'SQLDBA_Support',
@recipients= @mailto,
@subject = @MailSubject,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
End
SELECT @DiskFreeSpace = fspace FROM #driveinfo where drive in ('Y')
IF @DiskFreeSpace < @YDrivethreshold
Begin
SET @MailSubject = 'Drive Y: free space is low on ' + cast(Serverproperty('Machinename') as nVarchar)
SET @mailbody = 'Drive Y: on ' + cast(Serverproperty('Machinename') as nVarchar) + ' has only ' + CAST(@DiskFreeSpace AS VARCHAR) + ' MB left. Please free up space on this drive. '
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'profile_name',
@recipients= @mailto,
@subject = @MailSubject,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
End
set @mailbody='';
while (select count(*) from #driveinfo ) >= @count
begin
set @tempfspace = (select fspace from #driveinfo where id = @count and drive not in ('C','Q','D','Y'))
set @tempdrive = (select drive from #driveinfo where id = @count and drive not in ('C','Q','D','Y'))
if @tempfspace < @OtherDrivethreshold
BEGIN
SET @altflag = 1;
SET @mailbody = @mailbody + '<p>Drive ' + CAST(@tempdrive AS NVARCHAR(10)) + ' has ' + CAST(@tempfspace AS NVARCHAR(10)) + ' MB free</br>'
--SET @cmd = 'dir /s /-c ' + @tempdrive + ':\ > ' + @logfile
--EXEC xp_cmdshell @cmd
END
set @count = @count + 1
end
IF (@altflag = 1)
BEGIN
SET @sub = 'Monitor Space on ' + cast(Serverproperty('Machinename') as nVarchar)
set @mailbody = 'The below drives on ' + cast(Serverproperty('Machinename') as nVarchar) + ' have low disk space then threshold limit ' + CAST(@OtherDrivethreshold as VARCHAR(10)) +' Please free up the space in below specified drives <p>' + @mailbody
--print 'Space on ' + @tempdrive + ': is very low: ' + str(@tempfspace)+ 'MB'
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'Profile name',
@recipients= @mailto,
@subject = @sub,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
END
drop table #driveinfo
set nocount off
END
Thanks Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem

HOw to avoid DeadLocks when you schedule a Sql Server Agent Job and calling SSIS packages

Hi All,
I have scheduled 2 packages in in Sql Server Agent jobs .
First job which is having Package 1 executing at 11 AM and where I am inserting the data in the table.
Second job which is having Package 2 executing at 12 AM and where I am updating the data in the table based on the first job inserted records.
When I am executing my first job it taking more time and executing till 12 AM and from 12 AM my job 2 also starting ,so getting deadlocks conflicts because inserting happening from job1 and updating happening from Job 2.
How to avoid deadlocks and fix the issue.
Please Suggest .
Thanks & Regards,
Anand

Hi Anand,
Here is another solution, you can set the Job 2 not to run based on a schedule, and create another SQL Server Agent Job which starts at 12 AM and run with a specified time interval to execute a SQL statement in which you do the following steps:
1. Get the status information of Job 1 using the statement:
DECLARE @i int;
EXEC @i = msdb.dbo.sp_help_job @job_name = ‘Job Name'
2. If the value of @i is 1 which means the status of job 1 is success and current time is, then start the job 2. So, the statement is as follows:
IF @I = 1
EXEC msdb.dbo.sp_start_job @job_name= ‘Job Name’
Regards,
Mike Yin
TechNet Community Support

Scheduling SQL AGENT JOB for SSAS DataBase to take backup files Daily with Different Names

Hi All,
I am working with SSMS. I have Analysis Services DataBase.
i want to Schedule a SQL SERVER AGENT JOB.
I want to take that AS DB BackUp Daily and has to be stored in Same
Folder/same path in my local
machiene with Different Names.
Means, There should be Daily BackUps Files in that Path. According to that we have to Schedule the JOB.
Can anyone help me for this..
Thanks,
Supraja.

Hi Katherine,
Thanks a lot for your Response. what
you have posted is very useful for me.
But i am searching the result using AS
DataBase BackUp Script.
i found one of the easy way. its working for me.
Please check the below link for your reference..
http://dbatasks.blogspot.in/2012/08/taking-backup-of-ssas-database.html
Thanks,
Supraja.

Script to stop running SQL Agent job without passing job name as a parameter

Looking for script to stop running job and don’t want to pass job name as a parameter, any job which is in running state I want that to be stop/disable.
I have script to disable all jobs however if any jobs are in running state my requirement is to stop that job immediately and gets disable.
Rahul

Try the below scripts and then apply script to disable all jobs.
execute xp_cmdshell 'net stop sqlserveragent'
execute xp_cmdshell 'net start sqlserveragent'
Regards, RSingh

Unable to Run SSIS Package Through SQL Agent Job

Hi,
I recently upgraded SQL server 2008 R2 to SQL Server 2012. I also upgraded all the packages on the server. The package runs fine from BIDS. However when I try to run the package through the SQL Agent Job it fails with the error below:
Executed as user: A. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:43:04 PM Could not load package "\FolderA\Package.dtsx"
because of error 0xC00160AE. Description: Connecting to the Integration Services service on the computer "S2345WE" failed with the following error: "Access is denied." By default, only administrators have access to the
Integration Services service. On Windows Vista and later, the process must be running with administrative privileges in order to connect to the Integration Services service. See the help topic for information on how to configure access to the service. Source:
Started: 11:43:04 PM Finished: 11:43:04 PM Elapsed: 0.016 seconds. The package could not be loaded.
Using Windows Authentication I am able to login to Integration services through SSMS. In the SQL Agent job I am using package store to execute the package. I have admin permission on the server. The integration services currently uses my credentials while
running.I am not sure why I am getting this error.
Please advice..
Thanks,
EVA05

Hi ,
similar thread - http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/25e22c7e-bae0-42e4-b86d-2db7a4af519d
Try this link -
http://msdn.microsoft.com/en-us/library/dd440760%28v=sql.100%29.aspx
sathya --------- Please Mark as answered if my post solved your problem and Vote as helpful if my post was useful.

SSIS package is failing in SQL agent job with webserviceTaskException: Service Description cannot be null

Hi All
we are using webservice task in our ssis package and the package is successful in SSDT . when we created SQL job using that package it is failing with webserviceTaskException: Service Description cannot be null.
we have given access to web service for ssis proxy account and have access on wsdl file folder and given access to temp folder .
what would be the reason for the failure?
Surendra Thota

Hi Surenda,
As per my understanding, the error message is too general. In order to troubleshoot this issue, we should view the detail error message about this job. For more details, please see:
Troubleshooting Jobs
SQL Server Agent Error Log
Besides, since when you call a Microsoft SQL Server Integration Services (SSIS) package outside a SQL Server Agent job step, the SSIS package runs successfully. However, if you do not modify the SSIS package, then execute it via SQL Server Agent job step,
it fails. The scenario always related to the user account that is used to run the package under SQL Server Agent. Please also verify that the account has access to the Web site or to the Web Service Description Language (WSDL) file for HTTP connection manager.
References:
SSIS package does not run when called from a SQL Server Agent job step
Example using Web Services with SQL Server Integration Services
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Get error from SQL AGENT: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024

I am running SQL Agent that executes an SSIS process from sql server1. The SSIS process executes its SQL/tables/sp’s against another sql server2.
I get an error after adding data flow tasks with transaction supported within a sequence with transaction required. The error, “The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D024 "The transaction
manager has disabled its support for remote/network transactions"
Prior to adding this sequence everything was working from sql agent, and there were other sequences with oledb destinations.
Everything works when running within SSIS Package.
I see this article on similar issue,
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/0bfa2569-8849-4884-8f68-8edf98a9b4fe/problem-to-execute-a-package-and-tasks-with-a-certain-transactionoption-property-i-need-help?forum=sqlintegrationservices
“I had similar issue and solved by setting the following on both the machines. Allow Remote Clients, Allow Remote Administration,
Allow Inbound Clients, Allow Outbound Clients, and TIP are enabled in Component Services/My Computer/Properties/MSDTC/Security Configuration.”
I don’t want to remove transaction required for the “Remove Duplicates from Staging” sequence.
Anyone seen this?
Greg Hanson

DTC was running on remote computer. The problem was it was no longer accepting transactions from remote servers. This was in SSIS so I had to turn to "Transaction Supported" for all Data Flow Transactions.
Greg Hanson

Errors running SQL Agent Jobs for 64 bit SSIS packages on a 64 bit server, but Source server 32 bit

Similar Messages

Maybe you are looking for