The difference should be in the error handling. I'm sure about this but I think that the scheduled job uses it's own error handling as well which would be why...

You probably need to change a setting in the job.

There is a 'On failure action'. The standard setting is 'Quit the job reporting failure'. Change this to 'Goto the next...

Hi Hans,

I can't help you with the erratic behaviour but I can give you a solution. Set the tempdb on Restricted File Growth. Whenever the max size of the db...

The job owner is the logged on account. Could it be that the protocol we use is responsible? We make use of Named Pipes.

In that case I'll upgrade it again......

I did a full install... I also tried the downgrading of the MDAC to 2.7 but that also didn't change anything... could it be that a service doesn't have enough...

Thanks, but we have all updates (Win2003 server and SS2000) installed... so that doesn't seem to be the problem... thanks anyway!