Post reply

Scheduled Job started bud nothing happens

  • February 21, 2006 at 8:36 am

    #622306

    Here's something strange to try: Set the SQL Server Agent to run with your account and see if you can get the scheduled job to run.

    -- J.T.

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

  • February 21, 2006 at 9:01 am

    #622325

    I tried this again, still with the same result, nothing happens ?

  • February 21, 2006 at 9:22 am

    #622341

    Ok, take the command in the scheduled job (it should be a DTSRun command) and try running it from the windows command line. This should give you some better insight to where it is hanging. You may then want to recreate that part of the DTS package in a different way to see if you can get past it.

    -- J.T.

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

  • February 22, 2006 at 12:54 am

    #622533

    See also my response early, the straign thing is on the command line it works perfectly. This is now the way we are working with.

    I put the command in a batch file and we schedule this with the task manager of windows it self, and this is working.

    But it doe not work as we schedule it from out of the Enterprice server mangar itself.

    I still think that it has somthing to do with the IBM Client ODBC driver, that it is here waiting for a new connection password or somthing like that. But all what we tried to change in this connection has not have any effect.

  • February 22, 2006 at 1:52 pm

    #622744

    Is the step in the scheduled job something like:

    DTSRUN /~Zr324923rfj29f4f3...

    or more like:

    cmd.exe dtsrun.exe /~Z49412341j...

    The reason I ask is that I believe only local system administrators can run cmd.exe in a scheduled job. If the account running SQL Server Agent isn't a local server administrator that could be an issue. If the job just has DTSRUN then this isn't the issue.

    Have you tried changing the account running the SQL Server Agent? I read back through the thread but cannot tell if you did. I've seen this fix issues on occasion because the permissions for an account were not configured correctly. If not, set the SQL Server Agent to run as Local System, restart it, then set it back to the domain account you want and try the job again. If you have tried this, I'm at a loss. Maybe a different ODBC driver?

    -- J.T.

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

  • February 23, 2006 at 1:35 am

    #622819

    Yes I have tried to change the account and the SQL Server Agent is running as the local server administrator.

    The step looks like DTSRUN /~Zr324923fj29f4f4f3

    But I have change the step in the cmd.exe dtsrun.exe /~Zrrdfifjisf

    Know for the first time I can see that he is doing in the logging the cmd.exe command because in the logging he writes:

    Microsoft Windows 2000 [Version 5.00.2195]

    (C) Copyright 1985-2000 Microsoft Corp.

    C:\WINNT\system32>

    An that's it : therefore I still think that it has somthing to do with the odbc driver, at the end of the week I got a new one.

    And I gonne trie this?

  • February 23, 2006 at 1:42 am

    #622823

    Can you try running the dts in the job with its proper name in stead of the guid ?

    dtsrun /Npackage_name

     

    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

  • February 23, 2006 at 2:41 am

    #622838

    Yes, with the same result.

    when I executing it on the command line, it starts and then makes a request for the Password to the AS400. And he is not taken the default in the package or the default from the client ODBC driver.

    And I think this is my problem, because the server agent is waiting also for input from this password, but this will never come.

  • February 23, 2006 at 2:49 am

    #622841

    Here's Freud again

    Aha-erlebness

     

    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

Viewing 9 posts - 16 through 23 (of 23 total)

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