Cross Server Error Handling

We are having trouble with cross server error handling.
From what we've seen, if we run a query on Server X that
goes cross server to Server Y and then errors on Server Y,
the error number (@.@.error) doesn't get passed back to
Server X. How do we handle error handling then? How can
we get that error code back?"Bodel" <anonymous@.discussions.microsoft.com> wrote in message
news:0d7301c46e9e$728edd30$a601280a@.phx.gbl...
> We are having trouble with cross server error handling.
> From what we've seen, if we run a query on Server X that
> goes cross server to Server Y and then errors on Server Y,
> the error number (@.@.error) doesn't get passed back to
> Server X. How do we handle error handling then? How can
> we get that error code back?
I'm not completely sure on this, but...
Have you tried running it as part of a Distributed Transaction
Rick Sawtell
MCT, MCSD, MCDBA|||I have tried a variety of things including trapping the
error msg in the output parameter of a stored proc on
Server Y and then execute that on Server X. But that
doesn't work either. I can't find any way to bring it
back using just T-SQL. But maybe I don't understand what
you mean?
>--Original Message--
>"Bodel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0d7301c46e9e$728edd30$a601280a@.phx.gbl...
>> We are having trouble with cross server error handling.
>> From what we've seen, if we run a query on Server X that
>> goes cross server to Server Y and then errors on Server
Y,
>> the error number (@.@.error) doesn't get passed back to
>> Server X. How do we handle error handling then? How
can
>> we get that error code back?
>
>I'm not completely sure on this, but...
>Have you tried running it as part of a Distributed
Transaction
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>.
>

Cross Server Error Handling

We are having trouble with cross server error handling.
From what we've seen, if we run a query on Server X that
goes cross server to Server Y and then errors on Server Y,
the error number (@.@.error) doesn't get passed back to
Server X. How do we handle error handling then? How can
we get that error code back?
"Bodel" <anonymous@.discussions.microsoft.com> wrote in message
news:0d7301c46e9e$728edd30$a601280a@.phx.gbl...
> We are having trouble with cross server error handling.
> From what we've seen, if we run a query on Server X that
> goes cross server to Server Y and then errors on Server Y,
> the error number (@.@.error) doesn't get passed back to
> Server X. How do we handle error handling then? How can
> we get that error code back?
I'm not completely sure on this, but...
Have you tried running it as part of a Distributed Transaction
Rick Sawtell
MCT, MCSD, MCDBA
|||I have tried a variety of things including trapping the
error msg in the output parameter of a stored proc on
Server Y and then execute that on Server X. But that
doesn't work either. I can't find any way to bring it
back using just T-SQL. But maybe I don't understand what
you mean?

>--Original Message--
>"Bodel" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:0d7301c46e9e$728edd30$a601280a@.phx.gbl...
Y,[vbcol=seagreen]
can
>
>I'm not completely sure on this, but...
>Have you tried running it as part of a Distributed
Transaction
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>.
>

Cross Server Error Handling

We are having trouble with cross server error handling.
From what we've seen, if we run a query on Server X that
goes cross server to Server Y and then errors on Server Y,
the error number (@.@.error) doesn't get passed back to
Server X. How do we handle error handling then? How can
we get that error code back?"Bodel" <anonymous@.discussions.microsoft.com> wrote in message
news:0d7301c46e9e$728edd30$a601280a@.phx.gbl...
> We are having trouble with cross server error handling.
> From what we've seen, if we run a query on Server X that
> goes cross server to Server Y and then errors on Server Y,
> the error number (@.@.error) doesn't get passed back to
> Server X. How do we handle error handling then? How can
> we get that error code back?
I'm not completely sure on this, but...
Have you tried running it as part of a Distributed Transaction
Rick Sawtell
MCT, MCSD, MCDBA|||I have tried a variety of things including trapping the
error msg in the output parameter of a stored proc on
Server Y and then execute that on Server X. But that
doesn't work either. I can't find any way to bring it
back using just T-SQL. But maybe I don't understand what
you mean?

>--Original Message--
>"Bodel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:0d7301c46e9e$728edd30$a601280a@.phx.gbl...
Y,[vbcol=seagreen]
can[vbcol=seagreen]
>
>I'm not completely sure on this, but...
>Have you tried running it as part of a Distributed
Transaction
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>.
>