.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Post New Web Links

graphically monitor the running status of a package?

Posted By:      Posted Date: October 22, 2010    Points: 0   Category :Sql Server

hi all,

one of my packages is supposed to be run once per day.

if i add it to an SQL Agent Job, how can i graphically monitor the running status——which task has finished, which task is currently running,etc— of this package ,just as if i pressed the run button in BIDS and then watched the tasks turn yellow and then green.

or any suggestions?


Thanks in advance.

Andrew Chen
Interested in BI related technologies

View Complete Post

More Related Resource Links

SSIS package Scheduled Job Not Running

I'm not sure which way to research this issue.. I have an SSIS package that we can run just fine manually. But, when we put it into a scheduled job, it won't run. The package is on the same system as the SQL Server (2005), but it does call for updates from tables on another SQL Server (2000) on another domain (trusted). So, I'm thinking this might be a permissions / security issue, but not sure where to start... The package ProtectionLevel is "don't save sensitive", but that didn't help. Any help would be appreciated. Thanks. jill

No logging when running package from job!!

We are facing an issue when deploying some packages to the server. Our packages are deployed to File System in SSIS package store. We have defined a logging connection to MSDB in all packages and use that to log to msdb..sysssislog. Also, a config file(for each package) is used to store the connections and other variables Problem is, when we schedule the package through a job(using SSIS Package step type) , giving the config file...the package executes but it doesnt log anything to sysssislog. However, if I right click on the package in the Filesystem store and run it, providing the same config file. It runs and also logs.. We are trying to figure out why it wont log from the job

Problems running a bat file within a SSIS package

I have a ssis package which has 2 tasks, first it builds an excel sheet with data on the server from where I am running the ssis pkg and the second task (a sql process task), runs a bat. the bat file that basically copies the  excel sheet created from the first step to another server. Problem is that the ssis pkg runs succesful when i run it from BIDS, bust when I run is as ajon, it gets hung. It completes the first step, it is the sescond step that is get hung. I noticed that when i run from BIDs, it does come up with a window open file - security warning and says the publisher could not be verified, are you sure you want to run this software. why does it do that ??? the file I am asking to run is a .bat file. it should automatically use the cmd.exe app to run the bat file. Please help !!!   Thanks in advance.

DTExec is MUCH slower that just running my package in Debug mode in BIDS 2005

I am using BIDS / SSIS 2005.  I have a large package that runs very smoothly and fairly quickly when run in debug-mode through BIDS.  When I actually deploy the package to SSIS and execute it using either DTExec or DTExecUI it is WAAAAYYY slower than when run from the development environment.  So slow that I become convinced it is hanging on steps that execute very very quickly in BIDS.  I have read this thread -> http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/5585fa13-dd15-4406-9d4a-e993f2af5929 which has not helped. I understand that DTExec would be faster than DTExecUI because the former does not have to deal with the GUI component but I would have expected both (and especially DTExec) to be faster than running in debug from BIDS. I realize I am not providing a ton of detail here, problem is I just don't know where to start... any advice on what I should be looking at to improve package execution through DTExec and / or DTExecUI would be greatly appreciated.  Why would DTExec be so much slower than BIDS Debug??? Thanks in advance.. - Charles

SSIS package is giving error when ran thru JOB...its running good when I execute in BI Studio or Exe

Friends I am getting weird issue...I built an SSIS package. In one variable I used express builder and built like this... RTRIM( (DT_STR, 2,1252)  (((DT_I4) ( (DT_WSTR, 3) (SUBSTRING( @[system::machineName] , 12, 16 ))) +1) /2)) when I run the package outside ie., with VStudio or execute utility it running absolutely with out any problem. But when I created a job just to execute that package in particular timings...the job is totally failing by throwing error....the error output is like the following: Started:  10:22:33 AM Error: 2010-02-27 10:23:06.23    Code: 0xC00470C2    Source: Rerun_MissingFiles    Description: Error code 0x80020005 occurred attempting to convert from data type DT_WSTR to data type DT_I4. Error: 2010-02-27 10:23:06.23    Code: 0xC00470C4    Source: Rerun_MissingFiles    Description: Casting expression "(SUBSTRING( @[system::machineName] , 12, 16 )))" from data type "DT_WSTR" to data type "DT_I4" failed with error code 0xC00470C2. End Error Can any one help me please? Thanks in advance.

Running DTSWizard on French and Japanease OS ? How to prepare package ?

Hi, I am able to export query results via DTSWizard to Excel on English OS.   I would like to explore its use as reporting requirement for a project. Is there any way for French customer ( with OS and SQL in french) will get results in 1 or few click ?  I can prepare English package as per http://msdn.microsoft.com/en-us/library/cc952922(SQL.100).aspx Here I would like to avoid scenario like customer running queries manually in SQL management studio to get the reports? Appreciate your inputs... Thanks,    

Problem running SSIS package in Jobs

Hello friendsI'm trying to run my SSIS packages as a step inside a sql agent job.This runs normally when the package uses the SAME database as used to create my job.The problem occurs if I create a job to run the package and this package must execute queries in another database. Probably authentication problem. So how to authenticate my package and the job runs normally ?thanks in advance.

What can I do when I get messages like this during package running:


[SSIS.Pipeline] Information: The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. 108 buffers were considered and 108 were locked. Either not enough memory is available to the pipeline because not enough is installed, other processes are using it, or too many buffers are locked.



Running a WPF application from a console app and return status/console output from the wpf


I am trying to run a WPF application from a console application (e.g. a .bat file) but need to be able to receive console and error output from the WPF application.

I have console.writeline() and console.error.writeline commands in the WPF application but these are not received by the console application.

I would also like to receive a status value from the WPF on completion.

Is this possible?

If so could you give me a simple example using VB?

"Long Running Jobs" SCOM Monitor Alert Question

In SCom Monitor Alert we are receiving this Alert. Yet there seems to be no way of identifying the long running jobs.

Is there an easy way of identifying these jobs.


p.s. We are using an enterprise job scheduler (ESP) to schedule batch jobs.

Can a stored procedure programmatically determine if an SSIS package is running?



If I have the 'ExecutionInstanceGUID' value for an SSIS package that I know was started, is there a way that a stored procedure can programmatically determine whether the SSIS package still is running?

Thanks -



SQL Agent - Running SSIS Package - Windows Server 2008/Windows 7 - Messenger Services


We have tried to run a SQL job for SSIS Package. But it failed during the execution with the error "[364] The Messenger service has not been started - NetSend notifications will not be sent". But in the job, no notifications have been configured and in windows server 2008/Windows-7 there is no messenger service at all.

When we search for the the messenger service in windows 7/windows server 2008, we found that service is not in both the OS and it was replaced by msg.exe. 

Any help or workaround would be appreciated.

Thanks in advance.

PS: The normal SQL jobs other than SSIS are working fine without any error.

Vijay Pandurangan

How do I troubleshoot SSIS package hanged for running?


[This is just for sharing information for those common asked questions collected from forums. If you have any better way or feedback, please directly reply in this thread so that community users can benefit from your answers.]

My SSIS package is running in a SQL Server Agent job, but when it is running, it hangs. I could not see error messages from the job history. What is the problem?
There might be various reasons to cause a SSIS package hanged for running and generally for a hang issue, there is no log information helpful for diagnostics. These are the difficulties of troubleshooting hang issues. In this FAQ, we would like to give you three common aspects to help you perform self-troubleshooting:
1. Resource bottleneck
2. Blocking or Deadlock
3. Poor performance query

Resource Bottleneck
Generally resource bottleneck includes bottlenecks of memory, processor, physical disk or network interface. You can run Performance Monitor (perfmon.exe) to collect the trace with the following counters:
Processor: %Processor Time
Processor: %DPC Time
Processor: %Privileged Time
Processor: Interrupts/sec
Memory: Available Bytes
Memory: Pages/sec
Memory: Page Faults/sec
Memory: Committed Bytes

Subscription Status: Not running???


I rebooted my pub and subscription server. Now Tx Replication Subscription Status is Not running? Why and how can i get to the bottom of this? I did receive an error Alert that i set up saying

The job failed. Unable to determine if the owner  of job xyz has server access (reason: Could not obtain information about Windows NT group/user "ME", error code 0x6fd. [SQLSTATE 42000] (Error 15404)).

Please guide.


Running SSIS package from Stored Procedure using dtexec and Pass boolean value



We are using SSIS 2005 and sql server 2005. My package has a boolean type package level variable. Eg: IsClientNull boolean type.

I call this package from stored procedure. In addition to passing values for other parameters, how can I pass boolean value.

My code is like this:

SET @CMD='dtexec ' +
'/FILE ' + @pShareName + @pPackageName + ' ' +
'/MAXCONCURRENT " -1 " ' +
'/SET "\Package.Variables[User::StartDate].Properties[Value]";' +
CONVERT(char(10), @pStartDate, 120) + ' ' +
'/SET "\Package.Variables[User::EndDate].Properties[Value]";' +
CONVERT(char(10), @pEndDate, 120)
IF (@pClient IS NULL)

 SET @CMD = @CMD + ' ' +
 '/SET "\Package.Variables[User::IsClientNull].Properties[Value]";' +

job fails when running a dtsx package


hi all,

I am trying to solve the following problem: I have an SSIS package developed with VS2008 that simply dumps a text file into a table.
The file is on a network.

1. From the VS 2008, running the project doesn't give any errors - it fills the table OK.
2. I added the dtsx package to the Data Collector folder under Stored Packages/MSDB - I executed the package from there, again NO ERROR.
3. I created a job and added one step that is the dtsx package - it fails saying The file name "\\myFileServer\myData\myFolder\H29102010.txt" specified in the connection was not valid.  End Error  Error: 2010-10-29 10:03:11.83     Code: 0xC001401D     Source: myJOB      Description: Connection "c1" failed validation.  End Error  Error: 2010-10-29 10:03:11.84     Code: 0xC001401E     Source: myJOB Connection manager "c1"

The SSIS service is not running under NT ADMIN\Network Service but I changed to an account that can read/write to the above network location.
Also the package has been saved with password encryption (the user key encryption would raise erorrs, too).

What I can't understand is why would the packa

People_DL_import not running - Membership & BDC Import Status idle

Recently, we noticed that not all of our AD groups were showing up in MOSS people picker for audiences, and those that were did not always have the correct number of users in them.

Investigating this, we discovered that on the "User profiles and properties" page of the SSP, the "Membership & BDC import status" was always idle.
Clicking the "View import log" link, and choosing "PEOPLE_DL_IMPORT" in the
"Content Sources" drop down revealed that the last time crawled was over a
week ago.

Starting a full profile import did not have any effect - the profiles
appeared to import OK, but the membership and bdc import status remained with
a status of "idle"

I have managed to update the group memberships manually by using the
powershell script below:
$spsite = new-object Microsoft.SharePoint.SPSite(http://SITEURL)
$sc = [Microsoft.Office.Server.ServerContext]::GetContext($spsite)
$cm = new-object

which manually starts the DL import (the user profiles and management page
shows the membership and BDC status is enumerating, then importing). Doing
this manually, the import logs then show entries
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend