Hey there,

I was wondering if you ever found an answer to this? I have two SQL Server 2000 SP3 (yeah I know - but there is a contractual reason for it) and I get the same error when executing sp_start_job. The job starts on the remote server, and completes OK, but the error mentioned in your post above is generated immediately and kinda breaks the logic of what we are doing.

Cheers,

Scott.