Topic Options
Rate This Topic
#141645 - 02/17/11 11:12 AM Unchartered Territory
Mansell_R5 Offline
Stealth Member

Registered: 07/14/06
Posts: 16
Loc: North West, United Kingdon
For me at least. Any help appreciated as this has been driving me mad for a few days now.

On my test environment I have an active link attached to a button where the first action is a Push Fields to a View Form - the form it's a view of is a table on another server (not Remedy). However, when the button is used, I get the following error:

ARERR [552] Failure during SQL operation to the database : Unable to start a nested transaction for OLE DB provider 'SQLOLEDB'. A nested transaction was required because the XACT_ABORT option was set to OFF. (SQL Server 7395)OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionLocal::StartTransaction retur

If I use the SQL Query Analyser on the Remedy server, it works fine so it does work, just not when it's initiated by the active link.

The production environment workflow is set up the same and works without any problems. So far I've been unable to find any difference between the two environments which could cause this, so if anyone has any ideas that could point me in the right direction?

The server is on Windows NT5.2 running Remedy version 6.3 patch 013 and the database is SQL Server 2000. The other server is also running SQL Server 2000.

Thanks!...
_________________________
ARServer v6.3 patch 13
Windows NT 5.2
SQLServer

Top
#141648 - 02/21/11 05:37 AM Re: Unchartered Territory [Re: Mansell_R5]
Mansell_R5 Offline
Stealth Member

Registered: 07/14/06
Posts: 16
Loc: North West, United Kingdon
A quick update:

I set up an active link that ran the direct SQL: SET XACT_ABORT ON as the first action, followed by the original Push Fields action and then direct SQL to SET XACT_ABORT OFF>

but I still get the same error.
_________________________
ARServer v6.3 patch 13
Windows NT 5.2
SQLServer

Top
#141650 - 02/21/11 09:59 AM Re: Unchartered Territory [Re: Mansell_R5]
Mansell_R5 Offline
Stealth Member

Registered: 07/14/06
Posts: 16
Loc: North West, United Kingdon
Woooo hoooooo!

It's sorted now, all thanks to agrams and a post on here back in March 2004:

http://www.mattreinfeldt.com/forums/ubbthreads.php/ubb/showflat/Number/93887/site_id/1#import

The crucial part of the post in my case was:

The solution is to set the default user options in SQL server to XACTABORT on. This was accomplished using stored procedure spconfigure

USE master
EXEC sp_configure 'user options', '16384'
RECONFIGURE WITH OVERRIDE

You have to restart SQL Server after this change.

The 'user options' value is a bit mask value, where the default value is 0. 16384 is the bit mask value for XACTABORT. This allows SQL Server to process distributed transactions using a method ARS understands.
_________________________
ARServer v6.3 patch 13
Windows NT 5.2
SQLServer

Top