Scheduled Job started bud nothing happens

  • When we schedule a Job for a DTS-package, then the SQL server agent starts the JOB. The Job status turns into Executing Job Step 1’ . But after this statement nothing happen and it will turn into this state forever and never finish.

     

    The DTS-package is using multiple connections because we want to connect to an AS400 machine to collect some data en store this data into the SQL server database.

     

    The DTS-packages work as it supposes to be.

    The job that we created for the DTS-package has only one step that should be fired off with a CMDExe command. As we do this also manually on the command line it work also as suppose to be.

     

    But scheduled it hung.

     

    Can anybody tell me how I can fix this problem?

  • Is your sqlagent running using a windows-domain-account ?

    When you run the package yourself, it's using your account to get network or share rights.

    If it runs using localsystem, is has no rights to go onto the network !

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • Yes, the SQL agent is running on a windows-domain account on the server. I tried a number of user with a windows domain, with a local window domain and in every case I can start the DTS package or the Cmdexe job (directly on the server with several users with admin rights) but when we startup the Job it starts and hung

  • so you can login and execute using _that_ (sqlagent) domain-account ?

    Can you enable the jobstep's outputfile to capture windows output ?

    jobstep\advanced outputfile

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • I activated the jobstep's output file and started again the job, waited 5 minutes (because the hole transaction should be over in a couple of minutes) and then stopped the job again. The output file for the job step is generated but is completely empty.

     

     

  • just to be sure ...

    - you know EM does _not_ refresh automaticaly. You have top position on the lefthand pain at SQLAgent \jobs and hit F5 when you want the new situation.

    - What's the job's history ?

     

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • I Know, It starts with: Executing JOB 1'DQ REPORTS CH'

    And it stays in here until I force to stop the Job manually

    For the Job history, nothing happens, until I stop the Job manually, than it shows the message:

    The job was stopped prior to completion by User NLLOSQ01\Administrator.  The Job was invoked by User NLLOSQ01\Administrator.  The last step to run was step 1 (DQ REPORTS CH).

    I did not mentioned yet, but we using the schedule mechanism to backup the database, and this works.

     

  • did you put the jobowner to SA (and not a windows account) ?

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • The Jobowner was a windows account, I changed it to SA, but it still does not work.

  • Wim,

    You run a DTS Package, right? You can turn on DTS Logging and then check if the package runs in first place. (Or change the DTS Package, add a step that sends an email message, or creates a tempfile or record somewhere to check that the package is started).

    Regards

    JP

  • Hi,

    This is one of the problems you mention. The DTS Package is working, because we can execute it directly on the server or on the command line copying the CmdExe command from the Job/Step. All the logging is on and is working. But on the moment that we start the Job from out of the Enterprise Manager or we schedule the Job. It starts with executing step 1 and than nothing happen, no log, no step log no execution, nothing. Until I cancel the Job, and than I have my logging Job canceled by User.

  • Is this package password protected ?

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • No

  • A few quick questions:

    You mention multiple connections. Are any of these to oracle servers or do any of them require a client be installed on the SQL server to make the connection? The reason I ask this is I have come across a strange Oracle connection problem where the user installing the Oracle client is the only one who can connect to the Oracle databases. We had to uninstall the client and reinstall it while logged on as the account that would run the jobs.

    When you run the DTS package via schedule are you able to look at the other systems to see if a login is even attempted from the SQL server? This might give you a hint as to which connection is failing or hanging.

    Lastly, have you tried logging on to the SQL server as the account that is running SQL Server Agent and running the DTS package that way? if that works, try setting up the scheduled job.

    -- J.T.

    "I may not always know what I'm talking about, and you may not either."

  • Hi,

    The connection is to an AS400 machine via odbc driver of IBM. We logged also the intress to this client odbc driver, but we see no entry in this driver.

    I am working directly on the server with or without the same user as the SQL Server Agent it has every time the same result. It is waiting for somthing, but I can not find out what.

    All the loggings stay empty. Until I force to cancel the Job. And than I can see in all my logging that this Job is canceled. Nothing else

Viewing 15 posts - 1 through 15 (of 23 total)

You must be logged in to reply to this topic. Login to reply