Robert, Are you able to insert records in Query Analyzer while logged in as user ARAdmin? Try placing your INSERT commands in a Stored Procedure and test it in Query Analyzer. Then run the stored proc from workflow to see if it works. Here are a few posts that might be useful: "ROLLBACK - Distributed Transaction issues" Jan 2007 "Creating a View Form to Remote SQL Server" Mar 2006 "Im really lost!" Dec 2005 "Problem With Linked SQL database - ROLLBACK TRANACTION reques t with no corresponding BEGIN TRANSACTION" Nov 2005 "SQL View Form to a Linked DB" Nov 2005 "Remote Stored Procedure" Oct 2005 "Distributed Transaction Error" Jun 2005 HTH Stephen PS: If, after exhausting all other avenues, it still will not work here is an alternative - not a direct approach but it may get you going until you find a better solution: Insert records into a local SQL Server table. Then run a SQL Job every ## minutes that pushes any new records into the remote Oracle table.
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kern, Robert SBA Sent: Monday, March 12, 2007 12:02 PM To: arslist@ARSLIST.ORG Subject: MS SQL -> Oracle ... Distributed Transaction failed ? ** Hello list, we are running Remedy with an MS SQL Database ... we have established a linked server connection to an Oracle DB. This connection is running fine, and I am able to select and insert entries using the Query Analyzer. However, when trying the same with Direct SQL from a Remedy Escalation, we are then getting the error below: " The operation could not be performed because the OLE DB provider 'MSDAORA' was unable to begin a distributed transaction. (SQL Server 7391)OLE DB error trace [OLE/DB Provider 'MSDAORA' ITransactionJoin::JoinTransaction returned 0x8000d048]. " Question : has anyone ever run into that one, and might have an idea how to fix that ? - the Microsoft DTC service is running and configured - added the following to ar.cfg : SQL-Server-Set-ANSI:Defaults: T (and re-started the Remedy Service) - ardb.cfg has the following entry: DB-Options:SQL Server { name:XACT_ABORT value:ON } If anyone might have any suggestion or idea, that would be greatly appreciated ! Next step would be to maybe create a local MS SQL server view. Tested a little. Could create a Remedy view with that, but creating entries did not work. Thank you in advance ! Robert Germany __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
