Solved

SSIS scheduled job runs but nothing happens unless manually executed

Posted on 2012-03-17
1
931 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

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
unable to reinstall SCVMM 2012 R2 - SQL errors. 5 36
Need sql in string 2 28
the way to learn Microsoft BI 13 45
access to sql migration 5 23
Whether you've completed a degree in computer sciences or you're a self-taught programmer, writing your first lines of code in the real world is always a challenge. Here are some of the most common pitfalls for new programmers.
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.
Viewers will learn how to use the SELECT statement in SQL to return specific rows and columns, with various degrees of sorting and limits in place.

735 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