For at about one week, an SQL-Server 2008 Job which is startet by sheduler begins to run twice (at an interval of 3-4 secounds). Before everything works fine. Every day the jobs get new jobIds, so it could not be that one of the two jobs hang on a deadlook or something like that. If i start the job manual it starts only single! Do you have an idea? Thx Josef

Are you sure? Every time I try to start a job twice I get an error saying the job is already running.MCTS, MCITP - Please mark posts as answered where appropriate.

I'm realy sure! The problem is that the data sets are insertet twice and that couses a great problem! After that, i had to truncate the table and run the job manual.

Is this confirmed by the job history? It's not possible there's somewhere a bug in the package logic?MCTS, MCITP - Please mark posts as answered where appropriate.

In the job history i only see one starting point! But in the error log file all messages are twice and the data sets are insertet twice ... How can that occur?

RAISERROR('Erfolgreich: Import ...') is written twice to error log! Job is start by Sheduler daily!

What are you doing exactly in the package?MCTS, MCITP - Please mark posts as answered where appropriate.

The job imports txt-files to database. The files copied and importet to database. The activity is handled by an *.dtsx package which write log statement with RAISERROR(). Everything worked fine till last week. But since the Errorlog statements are twice and also the datasets in the table! Is this a bug? I don't know if it comes with an service pack installation, but perhaps .. ?!?!

After changing the job-start-time to 20:00 the job startet at 19:30 and 20:00. So it seems to have an daemon job, which cannot be administrated. In the job history i only see the start at 20:00 and in the Error-Log i can see both Job-messages! How can i remove the old job/shedule???

If you go to the properties of the job, and click on schedule, do you see multiple schedules or just one?MCTS, MCITP - Please mark posts as answered where appropriate.

I only see one shedule that runs from mon - fri (occur once at 20:00) Don't know what can happen to have such a problem or how to remove/stop a shedule which isn't existing ... ?? Did anybody have such a problem before ??

Can you share the Schedule Description?

Yes: Occurs every week on Monday, Tuesday, Wednesday, Thursday, Friday at 20:00:00. Schedule will be used starting on 03.07.2012.

Dig into the SQL Agent log to find out what is exactly happing: http://www.mssqltips.com/sqlservertip/2561/querying-sql-server-agent-job-information/ There are multiple scripts in this excellent article and they allow you to look at the jobs, the jobsteps and the schedules.MCTS, MCITP - Please mark posts as answered where appropriate.

I haven't seen any issue with the same, now try to recreate the job.

i have already recreated the job, nothing changed ...

Hi JJ-One, Have you delete the original job when you recreate the job? If possible please past the Job script for further investigation. Thanks, Eileen

Yes, i have already delete an recreated the job, but nothing changed! There is no Job script. The job starts one ssis package after the other, that's all! The first step is start twice, hundreds of millis past the other. Thx Josef

Nothing odd about the package itself? Something in the event handlers that might be executed without you knowing it?MCTS, MCITP - Please mark posts as answered where appropriate.

Nothing, it's the first step at the every first Task that gets executet twice. We have changed the starting time and now it is cold at the old time and at the new time. But i don't know how to kill the job at the old time?

When you rescheduled the package, did you create a new schedule or did you modify the old one? Did you look into the sql queries I linked to that examine the Agent log?MCTS, MCITP - Please mark posts as answered where appropriate.

In the job-history i also see only the start at the actual configured time. But in the ErrorLog i see the messages at both (old starting time and new starting time). Also in the msdb.dbo. ... (sysjobschedules) i only can find one job ... ??!!

I created a new Job with the schedule configuration?? Can i also schedule a ssis Package?? I don't know how??

Hi JJ-One, I faced a similar issue few days back where my uploaded file in production was getting overwrittten my some dummy file. On debugging I found that there was same job which was scheduled on QA server as well was causing it to be overwritten. Is something like this can be your case? madhur_ms

Yesterday we have delete the job and it start again at the old time, as expected. The Job cannot be configured over the Job Activity Monitor! Does anybody know how we can repair the problem, is there a work around or an administrative tool for diagnostic??

Madhur makes a good point. Do you have any other server (QA, DEV) which might accidentaly be pointing at your server?MCTS, MCITP - Please mark posts as answered where appropriate.

I don't think so .. ?! Which Server do you mean?? ... The server is running in a cluster!

The Problem is solved, somebody has startet the jobs from another server! It is nothing to do with our original sql server ... ! As mentioned above ... ;-)