Distributed Transaction Completed. Either Enlist This Session In A New Transaction Or The NULL Transaction. (HELP)
Hi,
i am getting this error "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.".
my transations have been done using LINKED SERVER. when i manually call the store procedure from Server 1 it works but when i call it through Service broker it dosen't work and gives me this error.
Thanks in advance.
View Complete Forum Thread with Replies
Related Forum Messages:
Error 8525: Distributed Transaction Completed. Either Enlist This Session In A New Transaction Or The NULL Transaction.
Hi All I'm getting this when executing the code below. Going from W2K/SQL2k SP4 to XP/SQL2k SP4 over a dial-up link. If I take away the begin tran and commit it works, but of course, if one statement fails I want a rollback. I'm executing this from a Delphi app, but I get the same from Qry Analyser. I've tried both with and without the Set XACT . . ., and also tried with Set Implicit_Transactions off. set XACT_ABORT ON Begin distributed Tran update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.TRANSACTIONMAIN set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.TRANSACTIONMAIN set REPFLAG = 0 where REPFLAG = 1 and DONE = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.WBENTRY set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.WBENTRY set REPFLAG = 0 where REPFLAG = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.FIXED set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.FIXED set REPFLAG = 0 where REPFLAG = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.ALTCHARGE set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.ALTCHARGE set REPFLAG = 0 where REPFLAG = 1 update OPENDATASOURCE('SQLOLEDB','Data Source=10.10.10.171;User ID=*****;Password=****').TRANSFERSTN.TSADMIN.TSAUDIT set REPFLAG = 0 where REPFLAG = 1 update TSADMIN.TSAUDIT set REPFLAG = 0 where REPFLAG = 1 COMMIT TRAN It's got me stumped, so any ideas gratefully received.Thx
View Replies !
SSIS, Distributed Transaction Completed. Either Enlist This Session In A New Transaction Or The NULL Transaction.
I have a design a SSIS Package for ETL Process. In my package i have to read the data from the tables and then insert into the another table of same structure. for reading the data i have write the Dynamic TSQL based on some condition and based on that it is using 25 different function to populate the data into different 25 column. Tsql returning correct data and is working fine in Enterprise manager. But in my SSIS package it show me time out ERROR. I have increase and decrease the time to catch the error but it is still there i have tried to set 0 for commandout Properties. if i'm using the 0 for commandtime out then i'm getting the Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction. and Failed to open a fastload rowset for "[dbo].[P@@#$%$%%%]". Check that the object exists in the database. Please help me it's very urgent.
View Replies !
Distributed Transaction Completed. Either Enlist This Session In A New Transaction Or The NULL Transaction.
Hi all, I've already read the thread by the same topic, but I found Kevin Yu's comment a bit confusing. I don't know how to solve my problem. I have two stored procedures in sql server. First one inserts into a bunch of tables so it has Begin Transaction and Commit in it. Second one just inserts into one table so it doesn't have the begin transaction statement in it. From my data access class in c#.net, I have a function which calls both of these stored procedures from within a "using transactionscope" block. So when it makes the call to the first stored procedure, it returns fine, but when it calls the second one, I get the above error. I think it has something to do with me declaring transactionscope in my application code, and then calling a stored procedure which also has its own begin transaction. But I don't know how to fix this. Any ideas? Thanks
View Replies !
Distributed Transaction Completed. Either Enlist This Session In A New Transaction Or The NULL Transaction
I'm using TransactionScope object and it is giving me problems. The situation is like this. I've 2 tables in sql server express, say student and courses and other one studentcourse for courses a student has opted for. An aspx page displays list of users in listbox, when user chooses student, it fetches courses he has opted for and in the checkedlistbox (for courses) these courses are checked. Now when uses makes any changes to courses and clicks update button, i've two functions at backend first one removes the courses which were previously selected but now not selected in postback, next it inserts courses which was not selected first but now are in this postback. I use following code: protected void Update(object sender, EventArgs e) { /* get selections, existing courses etc. */ using(TransactionScope tscope=new TransactionScope()) { try { RemoveCourses(/*Student*/ s, /*IList*/ oldCourses, /*IList*/ newCourses); AddCourses(/*Student*/ s, /*IList*/ oldCourses, /*IList*/ newCourses); tscope.Complete(); } catch(Exception ex) { lblMessage.Text=ex.Message; } } } If any exception occurs during update and page is reload or I go to any other page where some data is fetched from sql server I get the exception: Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction Please help!
View Replies !
Distributed Transaction Completed. Either Enlist This Session In A New Transaction Or The NULL Transaction.
I am getting this error :Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.OleDb.OleDbException: Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.have anybody idea?!
View Replies !
How Do I Not Enlist A Statement In A Distributed Transaction (sql 2000)?
Hi! I have problem that I havn't been able to solve. I am trying to write a stored procedure that saves log entries in a specific table. This procedure is called by other procedures for debugging purposes. The problem is that when something fails in the calling procedure the entire transaction is rolled back, including any entries in the log table. My goal is obviously to be able to commit the insert statement for the log table, but rollback everything else. To do this I tried to use a loop back connection using OPENDATASOURCE. This way: INSERT INTO OPENDATASOURCE('SQLOLEDB', 'Data Source=BTJLU-SQL-2,1422;User ID=ex_epix;Password=ex_epix;Enlist=false').External_EPIX_Info.ex_epix.CallLog(Member, Param, [Time]) VALUES(@procOrFuncName, @parameters, GETDATE()) The problem is that I get the following error: "The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction." This only happens when the log-procedure is called from a trigger called when a row in a table is updated as a result of it being replicated from another server. I tried to solve the problem by addig "enlist=false" to the connection string, but it made no difference. I'm fumbling in the dark here. Can anyone please help me? Thanks!
View Replies !
Distributed Transaction Completed Error.
Hi, I have an ASP application which uses a COM object to read/write/delete/update data from a SQL Server 2000 (SP3). In the ASP page on the first line I have: <%@TRANSACTION=REQUIRED%> and for commiting or aborting the transactions I use ObjectContext.SetComplete or ObjectContext.SetAbort The application works fine but under heavy use it sometimes throws the error: [Microsoft][ODBC SQL Server Driver][SQL Server]Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction. The error code is -2147217900 If I do not use MS DTC in the ASP page, I don't get this error any more but also I don't have the transaction integrity (sometimes I have to update also some other database). Any help would be greatly appreciated. Sorin
View Replies !
Fix - Enlist Operation Failed: SQL Server Could Not Register With Microsoft Distributed Transaction Coordinator (MSDTC)
Distributed transactions were happily running between our SQL servers and then we installed Windows 2003 Server SP2 and all of a sudden we got this nice error message when attempting a remote data update via linked servers. I couldn't even run "BEGIN DISTRIBUTED TRANSACTION" without getting the error message. The full error message is: "Enlist operation failed: 0x8004d00e(XACT_E_NOTRANSACTION). SQL Server could not register with Microsoft Distributed Transaction Coordinator (MSDTC) as a resource manager for this transaction. The transaction may have been stopped by the client or the resource manager." Apparently, SP2 disables network DTC access (how nice, I feel more secure knowing that my data can't be updated remotely anymore). Solution: From Control Panel | Add or Remove Programs | Add Remove Windows Components Select "Application Server" and click the "Details" button Check "Enable network DTC access" and click OK for however many prompts it takes to apply the changes. ****NOTE**** this change WILL SHUT DOWN SQL SERVER so plan accordingly (this would have been handy to know in advance since I ran it in the middle of the workday and everyone got disconnected). Hope this helps!
View Replies !
New Transaction Cannot Enlist In The Specified Transaction Coordinator
I'm getting this error: The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ] OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a]. http://support.microsoft.com/kb/839279 this didn't help any suggestions?
View Replies !
New Transaction Cannot Enlist In The Specified Transaction Coordinator
Hi I am trying transfer data from Back Office Server to Head Office using DTS. It is failing in few stores, rest of the store it is OK Configuration Head office :Windows 2003 SP1 and Sql Server 2000 SP3 Failing Store:Windows 2003 SP2 and SQL SERVER 2005 Successful Store :Windows 2003 SP2 qnd SQL SERVER 2000 At Store: Setting for MSDTC Log on Account for MSDTC Service : Network Service Network DTC Access = True Allow Inbound = True Allow Outbound = True No Authentication Required = True TurnOffRPCSecurity = 1 port Ranges for RPC = 5000- 5100 The error Message is as follows: (Microsoft Data Transformation Services (DTS) Package (8004d00a): Connection 'Head Office SQL Server' for Task 'DTSTask_DTSDataPumpTask_1' does not support joining distributed transactions or failed when attempting to join. Unable to enlist in the transaction. ) (Microsoft OLE DB Provider for SQL Server (8004d00a): New transaction cannot enlist in the specified transaction coordinator. ) If any one can help me, that will be great!!! Thanks in advance Shiny
View Replies !
The Microsoft Distributed Transaction Coordinator (MS DTC) Has Cancelled The Distributed Transaction.
We have a test db, a staging db and a live db. I have a stored procedure that runs fine on test and staging, but throws the following error on live. The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction. The stored procedure uses linked servers and a transaction. We're using the following transaction code in the stored procedure BEGIN BEGIN TRANSACTION BEGIN TRY --- procedure stuff here --- COMMIT TRANSACTION END TRY BEGIN CATCH DECLARE @ErrorSeverity INT, @ErrorNumber INT, @ErrorMessage NVARCHAR(4000), @ErrorState INT SET @ErrorSeverity = ERROR_SEVERITY() SET @ErrorNumber = ERROR_NUMBER() SET @ErrorMessage = ERROR_MESSAGE() SET @ErrorState = ERROR_STATE() IF @ErrorState = 0 SET @ErrorState = 1 RAISERROR ('ERROR OCCURED:%d', @ErrorSeverity, @ErrorState, @ErrorNumber) IF XACT_STATE() < 0 ROLLBACK TRANSACTION END CATCH END I found the following link which seems to be the problem we're experiencinghttp://support.microsoft.com/kb/937517 The link includes a workaround which is the following: "To prevent the SQLNCLI provider from sending an attention signal to the server, use the SQLNCLI provider to consume fully any rowsets that the OLE DB consumer creates. " How do I use the SQLNCLI provider to fully consume any rowsets?
View Replies !
Why Transaction Gets Promoted To Distributed Transaction
Hi,On My local SQL server I have added a linked server to another SQLserver (remoteserver) in another Windows NT Domain.When I run this codeselect count(*) from remoteserver.mosaics.dbo.LocationThis works fine.However when I usebegin transactionselect count(*) from remoteserver.mosaics.dbo.LocationIt errors out saying thatThe operation could not be performed because the OLE DB provider'SQLOLEDB' was unable to begin a distributed transaction.New transaction cannot enlist in the specified transactioncoordinator. ]OLE DB error trace [OLE/DB Provider 'SQLOLEDB'ITransactionJoin::JoinTransaction returned 0x8004d00a].My question is even though I am just reading data from theremoteserver, why does the local transaction get promoted to adistributed transaction.Any help will be grately appreciated.TIA...Rohit
View Replies !
New Transaction Cannot Enlist In Transaction Coordinator (was &"Please Help...&")
Hi all, In my ASP application, I've been using this code: ---------------------------------------------- dim conn, connectionstring connectionstring= "Provider=SQLOLEDB.1; Data Source = blahblah; Initial Catalog = abc; User Id = osss; Password=xxx" set conn = server.CreateObject("adodb.connection") conn.open connectionstring ---------------------------------------------- It's just basically to set up the connection to the SQL server, it works on my other pages, but on a few pages, the last line (conn.open connectionstring) triggers this error: "Microsoft OLE DB Provider for SQL Server error '8004d00a' New transaction cannot enlist in the specified transaction coordinator. " I've never encountered this error before and I couldn't think of any solution... please help!!! Thanks so much, Annie
View Replies !
&<[OLE/DB Provider Returned Message: New Transaction Cannot Enlist In The Specified Tr
Hi, I'm new to this grp. when i come across the problem with linked server while running stored procedure saying "<[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]>" I googled that message and got the solution from msdn. All we have to do to get rid of that message is change security configuration of MSDTC of Win XPsp2 or Win2003 server and also we need to enable port 135 to allow dtc to work using RPC. Now it seems the problem is resolved. But still the problem is occuring once every a while. I'm scraching my brain wht could be the reason. i've tried all the ways but still the problem exists. Hope i'm clear in explaining my problem. Am i? Please help me Thanks Ramesh
View Replies !
The Transaction Active In This Session Has Been Committed Or Aborted By Another Session.
Greetings, I'm running a website that uses ASP.NET/SQL2005 and the SqlTableProfileProvider. Periodically, I get this error: ** Events ** --------------- Event code: 3005 Event message: An unhandled exception has occurred. Event time: 10/16/2007 9:25:36 PM Event time (UTC): 10/17/2007 1:25:36 AM Event ID: 1c7dc43403ef45f18df695e86401651d Event sequence: 167 Event occurrence: 7 Event detail code: 0 Process information: Process ID: 3748 Process name: aspnet_wp.exe Account name: A64ASPNET Exception information: Exception type: System.Data.SqlClient.SqlException Exception message: The server failed to resume the transaction. Desc:3900000011. The transaction active in this session has been committed or aborted by another session. I'm baffled as to why this is happening. I haven't written any explicit procedures that use transactions, so I'm wondering if it's something in the membership/profile provider that is starting and failing to close the transaction. How do you go about tracing this? I have all the tools available (sql profilier etc), just no idea where to start... Do you know if the ASP.NET Membership provider uses transactions? I am NOT explicitly calling Profile.Save() after I set values..do I have to?
View Replies !
DTC - Transaction Context In Use By Another Session
Hi I have a master package that executes a series of sub packages. The master package is run from a SQL Agent job. The packages are reading from and writing to two databases on the same instance of SQL Server 2005. If I set the Execute Package Tasks for the sub packages without any precedence constraints between them and set TransactionOption = Required at the master package level (and supported from there downwards) I get the following errors. The event log shows me: The SSIS Runtime has failed to enlist the OLE DB connection in a distributed transaction with error 0x8004D00A "Unable to enlist in the transaction.". Running a SQL Profiler trace shows me: Error: 3910, Severity: 16, State: 2 Transaction context in use by another session. This problem is well documented and seems to go back to DTS in SQL Server 7.0 . . . see http://support.microsoft.com/?scid=kb;en-us;279857&spid=2852&sid=150 I can get round it by setting precedence between the sub packages - making them run one at a time solves the problem. But then we don't get the performance benefits of running the packages concurrently. Does anyone have any other solutions. TIA . . . Ed
View Replies !
Transaction Context In Use By Another Session
Hello MSDN Forums, We've run into this problem regarding transactions and have been unable to resolve it after several hours of searching and troubleshooting. We're hoping someone here can help. We have a Sequence Container (IsolationLevel = ReadCommitted, TransactionOption = Required) containing several Data Flows. The final Data Flow (IsolationLevel = ReadCommitted, TransactionOption = Supported) in the Sequence Container has a few branches, and could potentially have multiple queries being run on the SQL server at once. All of the SQL connection tasks and Lookups in this Data Flow are using the same Connection Manager (Native OLE DBSQL Native Client), which connects to a SQL Server 2000 DB, which has DTC installed. We get the following messages when we attempt to run this package. Note that these errors only occur intermittently, and usually when processing large volumes of data. An OLE DB error has occurred. Error code: 0x80040E14. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E14 Description: "Transaction context in use by another session.". OLE DB error occurred while fetching parameterized rowset. Check SQLCommand and SqlCommandParam properties. The ProcessInput method on component "Lookup Task A" (3353) failed with error code 0xC0208253. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. The ProcessInput method on component "Lookup Task B" (3261) failed with error code 0xC0208253. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. After doing some additional testing in a very basic package, we found that we could not perform multiple concurrent Lookups within a Data Flow at all, with a SQL Server 2000 DB. When we performed the same test on a SQl Server 2005 DB, it seemed to work fine. However, switching our target DB over to SQL Server 2005 is not an option. We have read the article posted by Microsoft here: http://support.microsoft.com/kb/q279857/, but we are not sure if it applies.
View Replies !
Transaction Context In Use By Another Session.
I'm having a SP1 on server A. This procedure has a begin trans and a commit. In this procedure i'm inserting data into tables. This data is provided by an extrenal app in staging tables. On the tables i'm inserting data on i'm having triggers that again are starting a SP2. I'm using a cursor on the inserted table to achieve this. The SP2 only insert a record on a table that is on a linked server. For testing reasons at this moment this is my dev machine too. The error 'Trans ... ' pops up .... Any suggestions .. Kind Regards, Harry
View Replies !
Distributed Transaction....
I have the following error:Server: Msg 7391, Level 16, State 1, Line 1The operation could not be performed because the OLE DB provider'SQLOLEDB'was unable to begin a distributed transaction.[OLE/DB provider returned message: New transaction cannot enlist inthespecified transaction coordinator. ]I have DTC services running in both servers, SET XACT_ABORT clause, ipaddress in hosts file, there´s not a firewall between servers,The only difference is sql server version, server A have Personaledition, server B have Standard edition Sql 2000...what im doing wrong???sorry for my english, but its not my native language...
View Replies !
Distributed Transaction
Hi all, I am trying to merge data of 2 tables on different servers with an insert statement. INSERT INTO SERVER1.db.owner.table select s2.* from SERVER2.db.owner.table as s2 LEFT JOIN SERVER1.db.owner.table as s1 ON s1.key=s2.key where s1.key is null I got this error. The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ] OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a]. while the select query is giving the result. I have done simmilar inserts on some other tables which worked fine I have created sp_addlinkedserver. and DTC set on both servers. any help will be greatly appreciated
View Replies !
Distributed Transaction
Hi All, I am trying to use distributed transaction (using linked Server). But getting the folloing error.. Some one please help... following is the error... The operation could not be performed because the OLE DB provider 'MSDASQL' was unable to begin a distributed transaction. [OLE/DB provider returned message: [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction context in use by another session.] OLE DB error trace [OLE/DB Provider 'MSDASQL' ITransactionJoin::JoinTransaction returned 0x8004d00a].
View Replies !
Why A Distributed Transaction Here?
I want to execute a remote stored proc and put the results in a local table. MachineB is a linked server on MachineA. I can do this succesfully on MachineA.... EXEC [MachineB].master.dbo.sp_helpdb I can also do either of these without any trouble.... SELECT * INTO local_copy FROM [MachineB].master.dbo.sysdatabases or INSERT INTO local_copy(name, dbid) SELECT name, dbid FROM [MachineB].master.dbo.sysdatabases ...assuming in the 2nd case that table 'local copy' has the appropriate matching columns. But I CAN'T do this..... (and the target table is correct) INSERT INTO local_copy EXEC [MachineB].master.dbo.sp_helpdb I get the error ""The transaction manager has disabled its support for remote/network transactions." or sometimes "The partner transaction manager has disabled its support for remote/network transactions." Whether or not the word 'partner' appears may be OS-level dependent. I have SET IMPLICIT_TRANSACTION OFF set. What I don't get is why INSERT ... remote-SELECT is not a distributed transaction and INSERT ... remote-EXEC is It's probably not going to help to use component services to allow remote transactions, because I'm not going to be able to do inbound authentication. (different domains wo/trust) And inbound authentication WILL be set on some targets because it HAS to be set on clusters. I don't like this... it's Microsoft forcing Windows authentication down our throats, even that that's not practical in lots of scenarios - such as when some participating nodes are some OS other than Windows. So for me the solution seems to be for this NOT to be a distributed transaction. Why should it be, when INSERT...remote-select doesn't have to???? Besides, only one machine is getting updated. No need to coordinate changes on multiple machines.
View Replies !
Distributed Transaction
Hi, I have a quick question about distributed transaction. We currently use a stored procedure to insert data in two tables, one of the table is located on a SQL 2000 server and the other one on an Oracle server (Linked server). I would like to ensure data integrity between the two server. For some reason i'm not able to retreive an error code from oracle when the transaction fail... How could the SP Rollback the entire transaction on SQL and Oracle side? Here is an example of the SP we use: CREATE PROCEDURE PLB_1_sp (@Value1 INTEGER, @Value2 INTEGER) AS BEGIN SET XACT_ABORT ON BEGIN DISTRIBUTED TRANSACTION INSERT INTO SQL1 VALUES (@Value1,@Value2) IF (@@ERROR <> 0) GOTO ERROR_HANDLER INSERT INTO linkedSvr..ORACLE.Table1 VALUES (@Value1,@Value2) IF (@@ERROR <> 0) GOTO ERROR_HANDLER COMMIT TRANSACTION ERROR_HANDLER: ROLLBACK TRANSACTION SET XACT_ABORT OFF END Thanks for your help
View Replies !
Distributed Transaction
I got following error when i tried to run a procedure which has a distributed tran in it: The operation could not be performed because the OLE DB provider 'SQLOLEDB' does not support distributed transactions. [OLE/DB provider returned message: Distributed transaction error] both my local and linked server has DTC service running, sql7 with sp1 any idea why it still give me this error? Thanks!
View Replies !
Distributed Transaction
Hi again, I do not know when to use Distributed Transaction. Would you please give an example about its usage or give a tutorials about this ? Thanks
View Replies !
Transaction Context In Use By Another Session Error
I have written a stored procedure that calls a C# class. The sp is called by a trigger on table A. The class has 2 methods. Method 1 is the main call from the stored procedure. Inside it, it sets a connection to the db. Then it calls another private method which has it's own connection and returns a dataset so that I can close that connection by the end of the method. When I execute the sp from within sql management studio, it runs just fine. But when being called from the trigger, I get the "transaction context in use by another session error" error. I read that I needed to wrap my 2nd connection in ... using (new TransactionScope(TransactionScopeOption.Suppress)){ open conn here, do work, etc.} I've tried that and I still get the same error from the trigger. Anyone know what else I can try? Thanks.
View Replies !
Error: Transaction Context In Use By Another Session
I am programming in ASP and SQL server. I am using this tag <%Transaction=Required%> to do the transaction. And it woks well, but the problem is that sometimes I get this error: "transaction context in use by another session"... It's really weird because it only happens in the same row. If choose this row to be shown I get that message, but if choose another row I get result with no error. And if take out the tag <%Transaction... I don't get any error. I've searched in other forums about this error, and one guy claims that there is a bug in the MTS and there is no way to solve the problem.
View Replies !
Transaction Context In Use By Another Session. (Continued)
A while ago i opened a thread on this issue, the collegue who took over the app closed the issue but the problem was not solved. Now that i'm back in track on this i will open a new issue. On Database A we want to update a record. In the update trigger we want to log this update to another database. In the currect setup Database B is on the same server. The trigger on table aa calls this procedure ALTER PROCEDURE [dbo].[SYNC_SDW_OLAP] @COMP_ID VARCHAR(5), @COU_ID VARCHAR(3), @ZZ_CLASS VARCHAR(5), @ZZ_ORIGIN CHAR, @ZZ_DATE SMALLDATETIME, @ZZ_INT BIGINT, @ZZ_NVARCHAR NVARCHAR(MAX), @ZZ_FLOAT FLOAT AS BEGIN SET TRANSACTION ISOLATION LEVEL SERIALIZABLE; BEGIN DISTRIBUTED TRANSACTION TR_SYNC; INSERT INTO OLAPDB.SDW_OLAP.XX.UPLOADS (COMP_ID, COU_ID, ZZ_CLASS, ZZ_ORIGIN, ZZ_DATE, ZZ_INT, ZZ_NVARCHAR, ZZ_FLOAT) VALUES (@COMP_ID, @COU_ID, @ZZ_CLASS, @ZZ_ORIGIN, @ZZ_DATE, @ZZ_INT, @ZZ_NVARCHAR, @ZZ_FLOAT); COMMIT TRANSACTION TR_SYNC; END; Each time we try to update a record this error (Transaction co...) is raised. How can we avoind this ....
View Replies !
Transaction Context In User By Another Session
Im using SQL Server 2000 sp2 for ASP application on windows server 2003 sp2. Im getting an error 'Transaction context in user by another session'. I have not at all used BEGINTRANS / committrans , No Insert / Update statements. the kind of SQL statements that i was using in that page load is only "SELECT statements" Can any one give me answer how to get rid of this. I have used only one connection object. and result set as a loop containing few more result sets. But I m sure they are so complex statements to block the SQL server transactions. Awaiting for reply..................
View Replies !
BEGIN TRANSACTION Or BEGIN DISTRIBUTED TRANSACTION
Hi have have two linked SQL Servers and I am trying to get things workingsmootly/quickly.Should I be using 'BEGIN TRANSACTION' or 'BEGIN DISTRIBUTED TRANSACTION' ?Basicly, these SPs update a local table and a remote table in the sametransaction. I cant have one table updated and not the other. Please dontsay replicate the tables either as at this time, this is is not an option.I have for example a number of stored procedures that are based around thefollowing:where ACSMSM is a remote (linked) SQL Server.procedure [psm].ams_Update_VFE@strResult varchar(8) = 'Failure' output,@strErrorDesc varchar(512) = 'SP Not Executed' output,@strVFEID varchar(16),@strDescription varchar(64),@strVFEVirtualRoot varchar(255),@strVFEPhysicalRoot varchar(255),@strAuditPath varchar(255),@strDefaultBranding varchar(16),@strIPAddress varchar(23)asdeclare @strStep varchar(32)declare @trancount intSet XACT_ABORT ONset @trancount = @@trancountset @strStep = 'Start of Stored Proc'if (@trancount = 0)BEGIN TRANSACTION mytranelsesave tran mytran/* start insert sp code here */set @strStep = 'Write VFE to MSM'updateACSMSM.msmprim.msm.VFECONFIGsetDESCRIPTION = @strDescription,VFEVIRTUALROOT = @strVFEVirtualRoot,VFEPHYSICALROOT = @strVFEPhysicalRoot,AUDITPATH = @strAuditPath,DEFAULTBRANDING = @strDefaultBranding,IPADDRESS = @strIPAddresswhereVFEID = @strVFEID;set @strStep = 'Write VFE to PSM'updateACSPSM.psmprim.psm.VFECONFIGsetDESCRIPTION = @strDescription,VFEVIRTUALROOT = @strVFEVirtualRoot,VFEPHYSICALROOT = @strVFEPhysicalRoot,AUDITPATH = @strAuditPath,DEFAULTBRANDING = @strDefaultBranding,IPADDRESS = @strIPAddresswhereVFEID = @strVFEID/* end insert sp code here */if (@@error <> 0)beginrollback tran mytranset @strResult = 'Failure'set @strErrorDesc = 'Fail @ Step :' + @strStep + ' Error : ' + @@Errorreturn -1969endelsebeginset @strResult = 'Success'set @strErrorDesc = ''end-- commit tran if we started itif (@trancount = 0)commit tranreturn 0
View Replies !
TRANSACTIONS In SSIS (error: The ROLLBACK TRANSACTION Request Has No Corresponding BEGIN TRANSACTION.&&"
I'm receiving the below error when trying to implement Execute SQL Task. "The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION." This error also happens on COMMIT as well and there is a preceding Execute SQL Task with BEGIN TRANSACTION tranname WITH MARK 'tran' I know I can change the transaction option property from "supported" to "required" however I want to mark the transaction. I was copying the way Import/Export Wizard does it however I'm unable to figure out why it works and why mine doesn't work. Anyone know of the reason?
View Replies !
Unable To Shrink Transaction Log Under Transaction Replication With Sync With Backup Enabled On Distribution Db?
We have applied transaction replication servers with SQLServer2005 standard edition with SP1 running on them. Sync with backup is also enabled on distribution db. Now our transaction log is not shrinking using standard shrinking procedure(taking log backup with truncate option/shrinkfile). select name,log_reuse_wait, log_reuse_wait_desc from sys.databases it is showing dbname, 6, Replication respectively. declare @db int set @db=db_id('dbname') dbcc loginfo(@db) is showing 2 in status column. tried shrinking transaction file after removing sync with backup option from distribution db. still it failed. again tried shrinking after stopping log reader, it didn't worked. Regards, M. Abdullah Idris
View Replies !
SCOPE_IDENTITY( ) In Distributed Transaction [:S]
i am inserting new record in linked server and i need to get the id (which is of course autonumber) of newly added record. can't i get it using SCOPE_IDENTITY( ) ? SCOPE_IDENTITY( ) seems to be returning null. so SCOPE_IDENTITY( ) doesn't work in distributed transaction?
View Replies !
Distributed Transaction Problem ?
Hi,MSSQL 2000 booth servers. Booth running DTC.Now, the client application, is starting in DB1 a procedure.The connection open to db, is within the transation opened fromclient.In the SP, I'm starting the transaction as well, with savepoint.Unfortunately, I have to get data, from other linked server (DB2).While performing query, the client application is recieving followmessages:If the query on DB2 is after a savepoint------Cannot go remote while the session is enlisted in a distributedtransaction that has an active savepointIf the query, is before starting transaction in sp (save point aswell)-----The operation could not be performed because the OLE DB provider'SQLOLEDB' was unable to begin a distributed transactionNow ... I was trying to set xact_abort to on, before, and within thetransaction in SP.But doesynt matter, it will not do.While calling an SP from QA, it goes threw, with query on DB2 beforetransaction inside SP.For me, it is an information, that the problem which I get, is becausethe client, while connecting to DB, is using it's connection withintransaction.My question is: how can I, run this query on DB2, without affectingchanges on the client side ?Below, small layout of this transactions stackBEGIN TRANSACTION_1 (client side)BEGIN TRANSACTION_2 (inside SP)SAVE TRANSACTION_2COMMIT OR ROLLBACK _TRANSACTION_2COMMIT OR ROLLBACK _TRANSACTION_1 (client side)where and with what option, put this query ?Best regards - Matik
View Replies !
Distributed Transaction Issue
I have two database servers and I have a stored procedure which will do a distributed transaction. The procedure runs on serverA and gets the data from serverB onto serverA. But the procedure is getting failed and I am getting the following error. The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. [SQLSTATE 42000] (Error 7391) [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a]. [SQLSTATE 01000] (Error 7300). The step failed. So when I checked the properties of my serverA on the connections tab Enforce Distributed Transactions(MTS) is not checked. Is this causing the above error or do I need to anything else to run my SP successfully. Thanks.
View Replies !
Distributed Transaction Failure
I’m attempting to insert the result set from a remote query into a local table and I’m getting the following error: Msg 8501, Level 16, State 1, Line 1 MSDTC on server 'REMOTESVR' is unavailable. OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d01c]. Msg 7391, Level 16, State 1, Line 1 The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. MSDTC is running on both servers. Has anyone ever seen this or have any insight into the cause? The code that I’m trying to run is: create table msver ( [Index] int, [Name] varchar(30), Internal_Value varchar(20), Character_Value varchar(512) ) insert into msver exec ('exec [REMOTESVR].master.dbo.xp_msver') Note that the remote query works fine. Thanks! Eric
View Replies !
Distributed Transaction Error, Need Help Please!!
Hi, I have configured a linked server, and i have a procedure which makes an UPDATE in a local table using the data in the linked server. Specifically, I have a function which checks if a given code exists in a linked server's table. The UPDATE changes the value of a column in a local table, if the function returns 1. I've run the procedure and it gave an error after a few hours cause a simple conversion error inside the function. I solved the error. After this, the procedure did not work more. It gives me the following message: Server: Msg 7391, Level 16, State 1, Procedure EXISTEONC, Line 16 The operation could not be performed because the OLE DB provider 'MSDASQL' was unable to begin a distributed transaction. (EXISTEONC is the function, and in the line 16 there is an OPENQUERY) Im sure MSDTC is working... i'm lost because i dont know why it worked the first time and not now. Ive also wrote the function again as it was before, but it still doesent works. Thanks a lot...
View Replies !
Distributed Transaction Error
Hi all, I encountered this problem when tried to perform a distributed transaction using link server. My aim was to connect 2 data base servers using TCP/IP and transfer data. I was able to run single queris using "linkserver.catelog. owner.table". But this message was shown when i tried to execute a stored procedure. The message was "The operation could not be performed since OLEDB provider SQLOLEDB doesn't support distributed transactions. [OLE/DB distributed transaction error]" The documentations about the distributed transactions showed that SQLOLEDB do support distributed transactions. Please forward your valueble suggestions. Thanks in advance, Sabu
View Replies !
Problem With Distributed Transaction
A stored Procedure when used to insert data in one table runs fine but fails when used with different table giving the message below. It is using linked servers to get to the tables -------------------- the operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ] ----------------------------
View Replies !
Distributed Transaction Problem
Hello, I've got stuck trying to run distributed transaction on same machine with two SQL instances. () Running transaction from Query Analizer With SET XACT_ABORT ON it works fine. (Without that - it throws an error about unable to begin nested distributed transaction). But from Application (C++, ODBC) it waits for a while and throus an error: 'unable to begin distributed transaction' even SET XACT_ABORT ON is applied before issuing transaction in Stored Procedure. What's happening here ? Thanks in advance.
View Replies !
Msg 7391 With Distributed Transaction....
Hi: When I tried to run a remote proc (with one parameter of date to return a set of records (no problem in return records) and to insert to the local database table A, with following errors: Server: Msg 7391, Level 16, State 1, Line 1 The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. [OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ] OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a]. SET XACT_ABORT ON BEGIN DISTRIBUTED TRAN insert tblA(column1, column2, column3) exec [remoteServerB].DBX.dbo.usp_XYZ '03/28/2006 ' COMMIT TRAN Both remote SQL and Local SQL are SQL2000 with sp4 and both Distributed Transaction Coordinator are on. Any idea? :rolleyes: thanks David
View Replies !
BEGIN DISTRIBUTED TRANSACTION
Hi I am using MSDTC and RPC to transfer data from one server to other. It was working fine since last day but today my procedure is getting stuck at BEGIN DISTRIBUTION TRANSACTION command. Any idea why? Manish
View Replies !
Distributed Transaction Problem
Hi! I am working on a distributed system managed from a particular server. I am getting a problem when using a particular database server. The error in the event viewer is- MS DTC is unable to communicate with MS DTC on a remote system. MS DTC on the primary system established an RPC binding with MS DTC on the secondary system. However, the secondary system did not create the reverse RPC binding to the primary MS DTC system before the timeout period expired. Please ensure that there is network connectivity between the two systems. Error Specifics:.cso.cpp:1841, CmdLine: C:WINNTSystem32msdtc.exe, Pid: 540 This error doesn't come when I use some other database server. I looked at all possible configuration parameters I could think of but there doesn't seem to be anything wrong with this server. Could someone please suggest what could be going wrong or where can I look for the problem. Thanks! - Manoj
View Replies !
DTC ... Distributed Transaction Update.... Help
Hello. I am trying to update a table on another server which is configured as a linked server on the server issueing the update. I can select data from the linked server no problem. But when I issue the update statement within the begin distributed tranaction I get the following. I am getting the following message Server: Msg 7392, Level 16, State 2, Line 1 Could not start a transaction for OLE DB provider 'SQLOLEDB'. [OLE/DB provider returned message: Cannot start more transactions on this session.] Has anyone had any similar problems with DTC.... I am getting ready to call Microsoft. But wanted to avoid the charge. Thanks John
View Replies !
Distributed Transaction Error
Hi All, I am getting the following error when I execute a Stored Procedure which has some distributed transactions in it. The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction. OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a]. I have enables the MSDTC serveices on both the SQL servers according to the steps given in this site http://support.microsoft.com/default.aspx?scid=kb;en-us;839279#appliesto But, the same stored procedure is working fine from one SQL server and it is not working on the other SQL server. Can any one help me in resolving this issue? thanks in advance. Regards, Vijay
View Replies !
|
TRACKER
