SSIS Package "running" in Job History?

My first post to Technet fora: Hello to everyone!
Last March our DW-system was migrated from SQL Server 2005 to SQL Server 2008 R2. Several SQL Server Agent jobs using SSIS packages were also migrated. The packages were converted from 2005 to 2008 with Visual Studio conversion tools.
After the migration several (but not all) of these jobs show a peculiar behavior in 'View Job History'.
As you can see the job history consists of two rows. But the lower one - from Execute Package Utility - has the green 'arrow head', as if it were still running.
In the Selected Row Details Pane, however, everythig seems to be ok:
Message
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 8:00:02
DTExec: The package execution returned DTSER_SUCCESS (0).
Started: 8:00:02
Finished: 8:00:03
Elapsed: 1.482 seconds
Is this something to be concerned about? The job seems to work just fine (a simple sql query, results to flat file).

Welcome to the fora :)
Strange, everything indicates the job finished, except for that little icon.
I would ignore it and classify it as a visual glitch, but I understand it can be annoying.
MCTS, MCITP - Please mark posts as answered where appropriate.

Similar Messages

Pick out the SSIS package from a job

Hi Everyone,
I have a SQL 2k5 instance. Previously someone embedded a SSIS package in a job and I just want to look into the SSIS package to understand the logics. However, in the job property, the package source is "SQL Server" and I don't know where I can
find the package itself(actually I tried open corresponding integration service but found nothing) and make a copy. Could someone give me some advice? Thank you very much.
regards,
Oliver

Hi Jens,
Thanks for your reply. Actually 2 of the job parameters are as below:
Package Source: SQL Server
Server: DE-S-0157590\DE_S_0157590
I tried to connect to integration service "DE-S-0157590", and I expanded every folder in the object panel but didn't find any SSIS package there. Could you please give some more suggestions? Thanks a lot.
Hi Oliver_Wang,
According to your description, we need to verify if someone has delete the SSIS package which is used in your job, I recommend you run this job and check if the job can execute successfully. Or you can choose “Edit” in the job steps and check if the SSIS
package exists in select an SSIS Package Box.
If the package indeed exist, we need to verify if you choose the right SQL Server instance. In addition, when you connect to integration service, we need to verify if your login account has permission to view the SSIS package and so on. There is an article
about SQL Server Agent jobs for packages, you can review it.
http://msdn.microsoft.com/en-us/library/ms141701(v=sql.90).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Error with SSIS package running as SQL Agent job

I have a strange issue.
I have a SQL Agent job that execute 5 steps, each step is an SSIS package that imports a CSV file to a temp table, then executes a SQL script to update a production table.
This job runs every 3 mins, every day, and has been for over a year.
Every once in a while it will start failing on step 2. Sometime it only happens for a couple of runs, other times I have to restart the SQL server. Once it corrects itself, it could be months before it happens again, but usually happens every
few weeks.
The error in the job history is: "Unable to bulk copy data. You may need to run this package as an administrator"
Obviously I have all the permissions correct, as it was running successfully every 3 mins before this error suddenly starts. I'm at a loss as to what the problem is. It is always on step 2, which is identical to step 1 except its a different CSV file
going to a different table. As I typed this, it failed twice, then was successful afterwards.
Any ideas where to look for further information? I've checked the event viewer and looked in the SQL logs, nothing stands out at this time.

Hi Kerberos35,
It seems to be caused by the UAC feature which makes SSIS use the low-permissions token of the administrator Windows account under which the job runs. This issue is described in the following KB article:
http://support.microsoft.com/kb/2216489/en-us
To resolve the issue, you can install the latest service pack for your SQL Server. To work around this issue, you can also use one of the following two methods:
Method 1: Replace the SQL Server Destination components in the Data Flow Tasks that are failing with OLE DB Destination components that point to the same SQL Server connection manager.
Method 2: Create a SQL Server Agent proxy by using a Windows account that is not a member of the local Administrators group after you assign Create Global Objects permissions to that account.
To do this, follow these steps:
Click Start, point to Administrative Tools, and then click Local Security Policy.
Expand Local Policies, and then click User Rights Assignment.
In the details pane, double-click Create global objects.
In the Local Security Policy Setting dialog box, click Add.
In the Select Users or Group dialog box, click the user accounts that you want to add, click Add, and then click OK two times.
Regards,
Mike Yin
TechNet Community Support

SSIS package runs from BIDS and by Executing package, but failing with Job

I have SQL Serve 2012 SSIS. I have problems to run from SQL Server Agent Job.
Steps runs SSIS package without configuration file. Package Run64BitRuntime is False in BIDS.
Package is runned by SQL Server Agent Service Account.
Server does not have Office 2010/2013 installed. Should it be installed?
ERROR1:
Description: The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered.
If the 64-bit driver is not installed<c/> run the package in 32-bit mode.
ERROR2: (here SSIS package is trying to import XML source, but cannot file file)
Description: An error occurred with the following error message: "Could not find file 'D:\Integration\Metadata\'.".
Kenny_I

Hi Kenny,
It seems like you are using Excel as source file right? If yes, then please follow below steps:
Edit the job step and Check the option: Use 32 bit run time. Below is the screenshot for the same.
Please let me know for any questions.
Thanks, Madhu

Running a SSIS package with SQL Job and Linked Server

I have a SSIS 2008 package. In one of the Script task I am calling a stored procedure which is using Openquery using linked server. I deployed this package with protection level as "EncryptWithPassword" and gave a password to the package.
Created a SQL job and edited its command line to include the password. If I login to SQL Server Mgmt Studio with Windows Authentication and run the job manually it runs fine. But when I schedule it then I get an error that "The Communication link to Linked
server failed".
Please help

Hi Vivek.B,
The issue should occur because the SQL Server Agent Service Account or SQL Agent Proxy account under which the job step runs doesn’t have sufficient permissions on the linked server.
If the job owner is the sysadmin fixed server role, the job can be run under the SQL Server Agent Service Account or a proxy account, then please make sure the SQL Agent Service Account or the proxy account has corresponding login on the linked server. If
the job owner is not a sysadmin fixed server role, the job must run under a proxy account. In this case, make sure the proxy account has a corresponding login on the linked server.
Reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
Regards,
Mike Yin
TechNet Community Support

Running SSIS Package from SQL Job - with Set Values, a string containing";"

Can anybody help with this problem please?
I’m using “set value” in SQL agent to pass in an email address to my SSIS package, if I put in a value of:
[email protected]
It works fine, but if I attempt to input multiple email addresses it fails
[email protected];[email protected]
It doesn’t appear to like the “;”.
Any ideas anyone???
BoroFC

Hi Jamie, many thanks for the response.
If I look at my command line table when Email = [email protected], it looks like:
/SET "\package.Variables[EmailAddress].Value";"[email protected]" /REPORTING E
If I change the value to “[email protected];[email protected]”, it looks like:
/SET "\package.Variables[EmailAddress].Value";"\""" [email protected];"" [email protected] ""\"" /REPORTING E
But the weird thing is, if I close the job properties window and re-open it again, I lose this line from my set values screen all together!!!
Help ???
BoroFC

SSIS Package Runs OK Manually But Not From SQL Server Agent...Permissions?

I have a problem where I have an SSIS package (SQL Server 2005) that won't run properly from SQL Server Agent, but it runs fine when kicked off manually from Integration Services -> Run Package or when run in debug from Visual Studio.
The first step in the package checks for the existance of a file via a script task. The script looks like this...
Code Block
Public Sub Main()
Dim TaskResult As Integer
Dim ImportFile As String = CStr(Dts.Variables("BaseDirectory").Value) + CStr(Dts.Variables("ImportDirectory").Value) + CStr(Dts.Variables("ImportFile").Value)
If Dir(ImportFile) = "" Then
Dts.TaskResult = Dts.Results.Failure
Else
Dts.TaskResult = Dts.Results.Success
End If
Return
End Sub
This script runs fine and the file is seen as expected when I run the package manually. But as a step in a SQL Server Agent job, it doesn't see the file.
The SQL Server Agent service is set to start up / log on as a Local System Account. I've also tried setting up a credential / proxy (using an account that I know can see and even move / rename the file) to run the job as but that didn't seem to help.
The package is being run from SQL Server (stored in MSDB) and is set to rely on SQL Server for sensitive information, so I don't think that's an issue; other packages are set up like this in terms of sensitive data and run fine.
Any ideas why my script can't "see" the file I'm looking at when it's kicked off by SQL Server agent? I've looked and looked...I can't seem to figure this out. I would really appreciate any help you might be able to offer up.

If the variables are fine, then I think it is very likely that this is security related. Since the Agent is running under the local system account, have you verified that the local account can access the file? When you tried the proxy account, are you positive that it was set up properly, and that the account had the permissions to read the file?
Another thing to check - is this a local file or is on another computer? If it is on another computer, make sure you are using a UNC path and not a mapped drive.

SSIS Package runs from the Package executer and from BIDS but not from the sql agent schedular

Hi Experts,
I have 2 packages :
1. Main Package -For each loop package
2. Sub Package - As we need to collect the information from several other DB with same table structures .
The Main Package calls the Sub Package and loops through several linked server (9 of them ) .
From last 2 weeks the scheduler is running on time but no data is loaded into our destination DB .
Daily i need to manually run the package .
The SQL Agent task is scheduled using the service account from which the sql server was installed on the server so it has the full privledges.
If i run the Main package from the BIDS i see 2 messages related to the configuration of xml no error message and executes fine.
If i run the Package from the execute package utility it runs fine.
Now if the package is scheduled for a nightly load it executes fine successfully no error message also in the Job History
but when i check for the data loaded on that day no data loads up in the destination DB . Due to this behavior of the sql agent even if am on leave i have to login on to the server and exec manually so if at times i forget the exec we are in big trouble
Please experts help me in troubleshooting the issue.
Thanks
Priya

Hi Visakh16 ,
We are using a service account to run the package .. Earlier in the BIDS i was getting the error crypotgenic
something password .. I googled out and changed the security : Protection Level : Dont save Sensitive
information . So that error now its not showing in the BIDS
And how is login mapping done for the linked servers? You've configured a mapped login for the service account also?
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

SQL 2012 SSIS package runs from the command line (dtexec.exe) and completes right away ...

Hi
I’m upgrading our SSIS packages from SQL 2005 to SQL 2012 .
Everything is working fine in Visual Studio, but when I’m submitting dtexec.exe it’s finishing right away in the command line (the actual execution takes long time).
It looks to me that as the return code doesn’t pass properly.
As I have depending tasks how I can make sure all jobs will be executed in the proper order.
(We never had this issue in SQL 2005)
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn>dtexec.exe /ISSERVER "\"\SSISDB\Direct_Prod\Direct_SSIS_Package
\DD_Load_Customer.dtsx\"" /SERVER TORSQLSIS01 /ENVREFERENCE 2
Microsoft (R) SQL Server Execute Package Utility
Version 11.0.2100.60 for 32-bit
Copyright (C) Microsoft Corporation. All rights reserved.
Started: 10:21:55 AM
Execution ID: 21138.
To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report
Started: 10:21:55 AM
Finished: 10:21:56 AM
Elapsed: 0.766 seconds

As per MSDN /ENVREFERENCE argument is used only by SQL Server Agent
see
https://msdn.microsoft.com/en-us/library/hh231187.aspx
below part is what it says
/Env[Reference] environment reference ID
(Optional). Specifies the environment reference (ID) that is used by the package execution, for a package that is deployed to the Integration Services server. The parameters configured to bind
to variables will use the values of the variables that are contained in the environment.
You use /Env[Reference] option together with the /ISServer and the /Server options.
This parameter is used by SQL Server Agent.
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

Advice on SSIS package running in a procedure

Hi guys, I'm struggling with a situation like this:
I got a SQL job Obava, within the job I have got two package ( I mean I set up two package on cascade). If I run
EXEC
msdb.dbo.sp_start_jobN'Obava'
SSMS returns
Job 'Obava' started successfully.
But nothing happens. If I run the package directly everything is ok ( even the mail sent to myself).
Any thoughts why? Thanks

Is the package in a remote path? Is the path given local path of the folder? Are you configuring the job in the same machine? Also does the account executing the package from the job has access to the path where package resides?
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Pass Variable to SSIS Package through SQL JOB -2012

So here is what i am trying to do.
I have a EXECUTE SQL Task - that executes a Stored Procedure with a Parameter. EXEC dbo.Procedure @Variable
I have deployed this SSIS on Server - Now i want to pass different values to this variable using SQL JOB at different times.
How can i achieve this in SQL 2012.
Thanks

Hi there,
MSDN is pretty clear on that:
Map Query Parameters to Variables in an Execute SQL Task
If not there are tons of blog posts: http://sqlage.blogspot.ca/2013/07/ssis-how-to-pass-parameter-value-to-ole.html
Arthur
MyBlog
Twitter

Execute SSIS Package from JOB which contains Execute Process Task calling a .bat file

Hi All,
I have a EXCEL Macro needs to be called from SSIS. We could not use Script task because of some internal reason.
So we have taken an approach to call a .BAT file using Execute Process Task. This .BAT file will call a .VBS file which will execute the EXCEL Macro.
The SSIS Package is running good if I execute the package from BIDS.
But the real problem is with the scheduling this SSIS Package using SQL JOB.
If i execute this SSIS package from SQL Server Job, its executing the whole package successfully except the Execute Process Task.
So the overall issue is SQL Server Job is not executing properly if I call any .BAT file from the SSIS Package.
Please give me suggestion to get rid of the issue. Thanks in advance.

Hi Sai.N,
If you run the SQL Server Agent job manually from SSMS, does the package execute properly? If the package executes properly when you run the job manually, the issue should occur due to permission issue. In this case, I suggest that you create a SQL Server
Agent proxy based on the current Windows account which you use to log onto the operating system, and run the job under the proxy account.
If it is not the issue, please enable logging in the package as Visakh mentioned and post the warning/error message for further analysis.
Regards,
Mike Yin
TechNet Community Support

Where is the account to execute ssis in file system when run a job

Hi
I have a ssis package in file system, and create a job, in general... the section package:... select "File System".
but it thrown: access denegate: the user should be administrator..
what is the account or where is it, that use to run the job in agent, this is owner of the job?
this is my configuration..
http://blog.sqlauthority.com/2011/05/23/sql-server-running-ssis-package-in-scheduled-job/

By default it would be the service account which SQLAgent uses
You can see this from services properties
for that go to start-> run
type services .msc
In local services window right click SQL Agent Service and check the properties and in LogOn tab you will see the account configured for it
Most cases it would be network service account and in some cases local system account (if not in a domain)
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

Execute the SSIS packages (2008 version) using SQL job 2008

We need to execute the SSIS packages (2008 version) using SQL job Please help with details information how to execute it.
1.Protection level of the SSIS packages.
2.Configuration File (Curently using XML file)
3.Please provide details how to create Credential (Windows User etc) Do we need to create windows cred explicitly to run the Job etc..
4.Please provide details for creating Proxy.
5.How can we configure the xml file since the xml is reading from local box but when the package is moved from developement box to production box
then the local drive might not be mapped with Production box .
6.Roles that need to be tagged for the Proxy/Credential.
7.Which is the best and safest way to execute ssis packages either msdb deployment or filesystem deployment and other necessary details.

Hi,
If you want to Execute your SSIS package using SQL job then best solution is to first deploy your Package
either using msdb deployment or filesystem deployment.The simplest approach to deployment is probably to deploy to the file system.
So, here is the deployment steps;
There are four steps in the package deployment process:
    The first optional step is optional and involves creating package
configurations that update properties of package elements at run time. The configurations are automatically included when you deploy the packages.
    The second step is to build the Integration Services project to create a package deployment utility. The deployment utility for the project contains the packages that you want to deploy
    The third step is to copy the deployment folder that was created when you built the Integration Services project to the target computer.
    The fourth step is to run, on the target computer, the Package Installation Wizard to install the packages to the file system or to an instance of SQL Server.
you can use below link also;
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
After that you need to Schedule package using SQL Agent then Have a look at the following link. It explains how to create an SQL job that can execute an SSIS package on a scheduled basis.
http://www.mssqltips.com/sqlservertutorial/220/scheduling-ssis-packages-with-sql-server-agent/
Deployment in msdb deployment or filesystem deployment has there own merits and demerits.
For security point of view msdb deployment is good.
it provides Benefits from database security, roles and Agent interaction
Protection Level;
In SQL Server Data Tools (SSDT), open the Integration Services project that contains the package.
Open the package in the SSIS designer.
If the Properties window does not show the properties of the package, click the design surface.
In the Properties window, in the Security group, select the appropriate value for the
ProtectionLevel property.
If you select a protection level that requires a password, enter the password as the value of the
PackagePassword property.
On the File menu, select Save Selected Items to save the modified package.
SSIS Provide different Protection levels;
    DontSaveSensitive
    EncryptSensitiveWithUserKey
    EncryptSensitiveWithPassword
    EncryptAllWithPassword
    EncryptAllWithUserKey
    ServerStorage
For better undertsnading you can use below link;
http://www.mssqltips.com/sqlservertip/2091/securing-your-ssis-packages-using-package-protection-level/
Thanks

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

SSIS Package "running" in Job History?

Similar Messages

Maybe you are looking for