I'm experiencing some odd behaviour with a remote procedure call and was just wondering whether anyone could shed any light on it?
I have a job on ServerA that has a step which calls a proc on linked ServerB:
Occasionally this step fails with the error:
Could not relay results of procedure 'MyProc' from remote server 'ServerB'.
Whenever it fails the step has run for exactly 10mins. Obviously this is the default value for the "remote query timeout" config option and both servers have this set to the default value so it makes sense.
However, when the step runs successfully (which is most days) it actually runs for much longer than 10mins - usually around 45mins to an hour.
I don't understand how this is ever running successfully?! Surely it should be timing out every time?
--James
I have a job on ServerA that has a step which calls a proc on linked ServerB:
Code:
EXEC ServerB.MyDB.dbo.MyProcOccasionally this step fails with the error:
Could not relay results of procedure 'MyProc' from remote server 'ServerB'.
Whenever it fails the step has run for exactly 10mins. Obviously this is the default value for the "remote query timeout" config option and both servers have this set to the default value so it makes sense.
However, when the step runs successfully (which is most days) it actually runs for much longer than 10mins - usually around 45mins to an hour.
I don't understand how this is ever running successfully?! Surely it should be timing out every time?
--James
