scheduled jobs not running properly 1

[swoodring]

I've been having a problem with our scheduled jobs locking up the last 2 mornings. The job that is locking up starts around 4 AM in the morning. When I come in around 8 AM it looks like its running. This job normally takes around 1 hour. The job is doing some DTS using our AS/4oo through ODBC connections. When I come in it looks like it running both on the As/400 side and on the server side but its not doing anything. Its still on the first step. So what I've done is stopped the job and then restarted it and it goes along fine. any ideas on what could be causing this?

On another note when I ran a package through the scheduler yesterday by saying only 1 step/1 package it did the same thing to me. I could see that it had actually finished the job but it was hung up. SO I stopped it and I checked it out and it had actually completed the entire package. Other times it seems to get hung up when I run this same package and I'll stop and start it and then it goes along fine. Other time its just fine. any idea on why this just stared happening? We haven't changd any configuration on our sql server 7.o or anything.

Stacy
Stacy

 

[TomSark]

I would check to ensure that the connection on the 400 hasn't been severed somehow. Could it be that someone manually fried it while performing some maintenance?

Also, when using the client access express driver, sometimes I have seen causes where the 400 severs the connection resulting in a 'communications link failure' message. Maybe this is happening?

In any case, are you logging the execution results in your package so you can ensure that everything is running OK? Tom Davis
tdavis@sark.com

http://www.sarkdallas.com

 

[swoodring]

I don't think I'm losing connectivity. This morning I ran a job through scheduler but just saying start job and it ran for 50 minutes , it normally take 15 minutes or less. I do have it logging to an error file. Wasn't much information in there other than saying that what steps suceeded. I was the only one on the server at the time. Not sure whats going on.