ABORT_XACT

Hi!
One of db_batch processes that was running localy on the server, failed on
our production MSSQL server, without any error neither in sql server errorlog
or job log. Using lumigent I was able to extract following information about
failed transaction:
2005-07-27
01:27:37.120|0000:004bceca|ABORT_XACT|NULL|.|.|.|0 |64|0|0|0|0000141b:00000a52:041c|user_transaction|
Server is MSSQL2000 with SP3a on W2000.
What might be the reason for this failure?
Thanks
I would try running profiler and capture all errors and warnings and
recreate. What you supplied is not much info. You may need to filter on the
dbid of the database you are having problems with.
"kimi" wrote:

> Hi!
> One of db_batch processes that was running localy on the server, failed on
> our production MSSQL server, without any error neither in sql server errorlog
> or job log. Using lumigent I was able to extract following information about
> failed transaction:
> 2005-07-27
> 01:27:37.120|0000:004bceca|ABORT_XACT|NULL|.|.|.|0 |64|0|0|0|0000141b:00000a52:041c|user_transaction|
> Server is MSSQL2000 with SP3a on W2000.
> What might be the reason for this failure?
> Thanks
sql

ABORT_XACT

Hi!
One of db_batch processes that was running localy on the server, failed on
our production MSSQL server, without any error neither in sql server errorlo
g
or job log. Using lumigent I was able to extract following information about
failed transaction:
2005-07-27
01:27:37.120|0000:004bceca|ABORT_XACT|NULL|.|.|.|0|64|0|0|0|0000141b:00000a5
2:041c|user_transaction|
Server is MSSQL2000 with SP3a on W2000.
What might be the reason for this failure?
ThanksI would try running profiler and capture all errors and warnings and
recreate. What you supplied is not much info. You may need to filter on the
dbid of the database you are having problems with.
"kimi" wrote:

> Hi!
> One of db_batch processes that was running localy on the server, failed on
> our production MSSQL server, without any error neither in sql server error
log
> or job log. Using lumigent I was able to extract following information abo
ut
> failed transaction:
> 2005-07-27
> 01:27:37.120|0000:004bceca|ABORT_XACT|NULL|.|.|.|0|64|0|0|0|0000141b:00000
a52:041c|user_transaction|
> Server is MSSQL2000 with SP3a on W2000.
> What might be the reason for this failure?
> Thanks

ABORT_XACT

Hi!
One of db_batch processes that was running localy on the server, failed on
our production MSSQL server, without any error neither in sql server errorlog
or job log. Using lumigent I was able to extract following information about
failed transaction:
2005-07-27
01:27:37.120|0000:004bceca|ABORT_XACT|NULL|.|.|.|0|64|0|0|0|0000141b:00000a52:041c|user_transaction|
Server is MSSQL2000 with SP3a on W2000.
What might be the reason for this failure?
ThanksI would try running profiler and capture all errors and warnings and
recreate. What you supplied is not much info. You may need to filter on the
dbid of the database you are having problems with.
"kimi" wrote:
> Hi!
> One of db_batch processes that was running localy on the server, failed on
> our production MSSQL server, without any error neither in sql server errorlog
> or job log. Using lumigent I was able to extract following information about
> failed transaction:
> 2005-07-27
> 01:27:37.120|0000:004bceca|ABORT_XACT|NULL|.|.|.|0|64|0|0|0|0000141b:00000a52:041c|user_transaction|
> Server is MSSQL2000 with SP3a on W2000.
> What might be the reason for this failure?
> Thanks