• Brandie Tarvin (1/12/2012)


    Evil Kraig F (1/11/2012)


    Brandie, do you have any extra information on what type of timeout it is? Is it a lock timeout, a remote query lockout, a network timeout, a login timeout?

    I think it's a remote query timeout.

    That did it. I can see what you see now. I created a secondary linked server and set the connection timeout and query timeouts to 1 and then built a passthrough proc to call the proc on the foreign server. Said foreign proc was nothing more than a waitfor delay '00:00:15'.

    Successful completion of a failure, but that's primarily because the proc doesn't actually fail, which is just... wierd. Try/Catch is also useless, as it's not an actual failure. Blasted strange. The workaround will not function. Hmmmmm.

    My Google Fu does fail me now.

    By chance, are you also connecting from a 2k8 machine running the agent and the local DB with the connection attached to a 2k5 machine like I am? I've reviewed some errors for this and it appears others have gotten an actual error to occur from this.


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA