Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

SSIS scheduled job runs but nothing happens unless manually executed

Posted on 2012-03-17
1
924 Views
Last Modified: 2012-03-17
I have an SSIS job schedled to run every hour.  The job runs perfectly without errors when manually executing it.  On the schedule it shows as executed without errors however there is nothing that happens.  None of the data has changed.  Looking through the history I can see wehre every time it ran it says successfully completed.

Date            3/17/2012 12:50:00 AM
Log            Job History (TransferDataFeed)

Step ID            0
Server            MyCOMPUTERNAME-VAIO
Job Name            TransferDataFeed
Step Name            (Job outcome)
Duration            00:00:01
Sql Severity            0
Sql Message ID            0
Operator Emailed            
Operator Net sent            
Operator Paged            
Retries Attempted            0

Message
The job succeeded.  The Job was invoked by Schedule 9 (DailyRoutine).  The last step to run was step 1 (ExecutePackage).


This is running on SQL Server 2008R2 and the job is scheduled through Agent in Microsoft Studio 2008r2 Complete.
0
Comment
Question by:pskeens
1 Comment
 
LVL 2

Accepted Solution

by:
pskeens earned 0 total points
ID: 37733090
Solved!  I created server credentials for myself and then created a proxy for these credentials.  Then on the "Run As" in the job configuration selected the proxy user.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article I will describe the Backup & Restore method as one possible migration process and I will add the extra tasks needed for an upgrade when and where is applied so it will cover all.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example, show how to shrink a transaction log file down to a reasonable size.
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question