I get the following error in the SQL ErrorLog file and in the Event Viewer when using a J2EE web application deployed on BEA WLS 8.1sp5 using the Weblogic JDBC Type4 XA driver with MSSQL Server 2000 SP4
Enlist of MSDTC transaction failed: XACT_E_NOTRANSACTION.
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!
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
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.
Hi All, I am using the CSLA framework for the data access with SQL Server 2005 and we are not using distributed transaction. When we are using this architecture for our local machine it is working fine and our DB is in local machine itself.
But I am getting the following error in our development server and our DB is in the Network. " DataPortal.Fetch failed
(DataPortal.Fetch failed (DataPortal.Fetch failed (Network access for
Distributed Transaction Manager (MSDTC) has been disabled. Please enable DTC for
network access in the security configuration for MSDTC using the Component
Services Administrative tool.))) ---> DataPortal_Fetch method call failed
---> DataPortal.Fetch failed (DataPortal.Fetch failed (Network access for
Distributed Transaction Manager (MSDT... Procedure Script call failed." Please help me out to get rid of it. Your help would be appreciated.
RegardsGomaz
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?!
i have a sequence container in my my sequence container i have a script task for drop the existing tables. This seq. container connected to another seq. container. all these are in for each loop container when i run the package it's work fine for 1st looop but it gives me error for second execution.
Message is like this:
Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.
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.
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?
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
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
I am trying to do something simple to test TransactionOption. I have a ScriptTask (out of the box), which runs fine. To test TransactionOption, I set the Package Properties TransactionOption = Required. Straight away the package fails with the following message
Error: The SSIS Runtime has failed to start the distributed transaction due to error 0x8004D01B "The Transaction Manager is not available.". The DTC transaction failed to start. This could occur because the MSDTC Service is not running.
I am running this on my Laoptop, which has XP Pro with SP2.
I checked the services and MSDTC and it is running fine. I have checked the Event Viewer and saw the following messages... One is Information and the other is Error
Information (Disk - Event ID 2444)
----------------------------------------------
MSDTC started with the following settings:
Security Configuration (OFF = 0 and ON = 1):
Network Administration of Transactions = 0,
Network Clients = 0,
Inbound Distributed Transactions using Native MSDTC Protocol = 1,
Outbound Distributed Transactions using Native MSDTC Protocol = 1,
Transaction Internet Protocol (TIP) = 0,
XA Transactions = 0
Error (Devices - Event ID 4437)
------------------------------------------------
The account that the MS DTC service is running under is invalid. This can happen if the service account information has been changed using the Services snap-in in Microsoft Management Console (MMC). MS DTC service will continue to start. Please make sure that the MS DTC service account information is updated using the Component Services Explorer.
I have checked Component Services. All looks fine from what I can see.
Anyone else came across this?
Thanks
Sutha
Server 1: Win2003, Clustered Environment, SQL 2005sp2
Server 2: Win2003, no cluster, SQL 2000sp3a
Server 3 (aka, client): Win2003, using ODBC (sql native client) to connect to server 1
I'm attempting to run an SQR that connects to server 1, yet updates server 2. Right now, all I'm doing is the statement
delete from <server2>.<database>.dbo.table
and am getting the error (DUL41 is server 2):
SQR 5528) ODBC SQL dbexec: SQLExecute error 7412 in cursor 1:
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB provider "SQLNCLI" for linked server "DUL41" returned message "No transaction is active.".
(SQR 5528) ODBC SQL dbexec: SQLExecute error 7391 in cursor 1:
[Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "DUL41" was unable to begin a distributed transaction.
If I use query analyzer (or whatever we're calling it now) to connect to server 1 and run the statement, it works fine. But, SQR is connecting via ODBC (that's different) and also is SQR.
I'm also not 100% sure all of the new MSDTC aspects are configured correctly, but I've gone through the settings a few times. Right now, I pretty much have everything set about as open as possible (these are test servers on the same network) and am still getting the error.
Any help, or ideas I could try, would be great. Thanks.
In this article http://download.microsoft.com/download/f/1/0/f10c4f60-630e-4153-bd53-c3010e4c513b/ReadmeSQLEXP2005.htm , it explains that you must fully enable the security settings to allow use of transaction processing for a SqlExpress database. Is there a way to set these option in a setup? Or is there another way to use transaction processing without setting these options?
Thanks
Dave T
I have a sql job which has to pull some data from a remote server. This job is running fine last few days and suddenly failing to execute with the following error. The same job is running fine in other servers.
Executed as user: NT AUTHORITYNETWORK SERVICE. The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction. [SQLSTATE 42000] (Error 1206). The step failed.
Note: The steps I have already done :
1. Verified the MSDTC configurations and restarted the MS DTC
2. Restarted the Sql Server
3. Restarted the machine.
Any help will be highly appreciated.
Hi,
I am using SQL server 2000 and I created a maintenance plan. I started the jobs manually for the first time to see if everything will do as it's supposed to do before the scheduel takes place.
The DB backup are successful. When I start the Transaction Log backup job it returns failed. But when I look on the actual server ine the default directory the transaction logs are there with the current date and time.
Why do I always get a failed message. It says in the job history - The job failed. The job was invoved by user xxxxx. The last step to run was step 1(step 1).
Does anyone have an idea why I get this message. Also it says that is notified me by net send and it never does.
I'm getting the following stack trace when trying to use TransactionScope with multiple newly created connections. The exact same code works perfectly in MSSQL 2005. Is there something that I'm missing, or (hopefully) is this going to be fixed for release? Thanks much.
System.InvalidOperationException: The connection object can not be enlisted in transaction scope.
at System.Data.SqlServerCe.SqlCeConnection.Enlist(Transaction tx)
at System.Data.SqlServerCe.SqlCeConnection.Open()
at TransactionScopeBugs.DAO.get_Connection() in DAO.cs:line 35
at TransactionScopeBugs.DAO.Insert(String query) in DAO.cs:line 51
at TransactionScopeBugs.Class1.InsertRecord() in Class1.cs:line 38
at TransactionScopeBugs.Class1.TestTxScope() in Class1.cs:line 54
Class1
Code Block
[TestFixture]
public class Class1
{
protected TransactionScope scope;
[SetUp]
public void Initialize()
{
scope = new TransactionScope();
}
[TearDown]
public void TearDown()
{
scope.Dispose();
}
private int GetRowCount(DAO d)
{
using (DbCommand cmd = d.NewCommand("SELECT COUNT(*) FROM TxScope", d.Connection))
{
return (int)cmd.ExecuteScalar();
}
}
private void InsertRecord()
{
DAO d = new DAO();
int num1 = GetRowCount(d);
string id = d.Insert("INSERT INTO TxScope (name) values ('txscope')");
Assert.IsNotNull(id);
Console.WriteLine(id);
int num2 = GetRowCount(d);
Assert.AreEqual(num1 + 1, num2);
}
[Test]
public void TestTxScope()
{
InsertRecord();
}
}
DAO
Code Block
public class DAO
{
private static readonly DbProviderFactory providerFactory;
static DAO()
{
providerFactory = DbProviderFactories.GetFactory("System.Data.SqlServerCe.3.5");
}
public DbConnection Connection
{
get
{
DbConnection conn = providerFactory.CreateConnection();
if (conn.State == ConnectionState.Closed)
{
conn.ConnectionString = "DataSource="txscope.sdf"";
conn.Open();
}
return conn;
}
}
public DbCommand NewCommand(String query, DbConnection conn)
{
DbCommand cmd = providerFactory.CreateCommand();
cmd.CommandText = query;
cmd.Connection = conn;
return cmd;
}
public string Insert(String query)
{
using (DbConnection con = Connection)
{
using (DbCommand cmd = NewCommand(query, con))
{
cmd.ExecuteNonQuery();
cmd.CommandText = "SELECT @@IDENTITY";
object val = cmd.ExecuteScalar();
return val.ToString();
}
}
}
}
SQL 7 SP1 NT 4.0 SP5
I created a backup plan for transaction logs only to run every 30 minutes. It works great for all databases except the Master and my main database scdb_v2.
The routine backups up the other 3 databases with no issue.
Why is this happening ?
Thanks,
Craig Somberg
mailto:csomberg@stageone.com
Hi all,
SQl server 7
I have a job to run every six hours to take the transaction log backup.
but the job has failed.
when viewed through view job history its giving the below error msg.
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
I tried starting the job but its failing with the same error msg.
pls help.
TIA
Hi All,
Greetings,
SQL Server 7,
I have scheduled transaction log backup for every 6 hours.
the scheduled job ran as per scheldue at 12pm but its giving error
The job failed. The Job was invoked by User comcreation. The last step to run was step 1 (Step 1).
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
there is enough space in the drive where transaction log backup
is stored
Please help me.
Hi
Had a weird error yesterday, can anybody shed any light on it.
I got the following error in a SQL 7(sp2) database.
'The log file for database 'IT2PROD' is full. Back up the transaction log for the database to free up some log space..
Error: 9002, Severity: 17, State: 2'
The Transaction Log has unrestricted file growth and auto grow file set and the disk has over 20gb of free space.
The only explanation I can think of is that the Log tried to extend during the hourly backup. Would this cause the above error ??? The backup file is usually about 80mb but was over 300mb when this happened.
Any ideas ????
Thanks in advance
Gary
Hi Greeting,
Sql sever7
OS winNT
We have scheduled transaction log backup for user database to run every one hour. Now the transaction has failed. it gives out put
[12] Database oas: Delete Old Backup Files...
Unable to delete file E:mssql7 logsoasoas_tlog_200608111300.TRN. 0 file(s) deleted.
When we try to delete the file manully, we get alert message "can not delelte the file as it is in use."
Please suggest how to solve this.
Awating for reply
Thanks in Advance
Adil
Any thoughts as to why I get this error, every hour. How do I fix it?
Be gentle I'm a SQL novice.
Error reported in the Application Event Log.
Package "Hourly Transaction Log" failed.
OS: Windows Ser_2003_sp1
Source: SQLISPackage
Category: None
Type: Error
Event ID: 12291
File Name dtsmsg.rll
File Version: 2005.90.3042.0
Product Name: Mic SQL Server.
Product Version: 9.0.3042.
Time 3:00:01 PM
Type: Error
Hi,
My application returns the following error when a SQL call is made during a transaction log backup.
Cannot open database requested in login 'login_name'. Login fails.
Has anyone come accross this problem before? or maybe worked around it?
Cheers
Luke
I have a publication on Sql Server 2012 that uses transactional replication to 7 subscribers (these are a mix of Sql Server 2008R2 and Sql Server 2012). Last night I scheduled the Snapshot job to run to "re-publish" the database to the subscribers. I had a few new table to push down. Unfortunately the snapshot job became the deadlock victim. Now updates to the publisher are not being sent to the subscribers.
Short of rerunning the snapshot job, is there a way to repair the replication so the updates to the publisher are pushed to the subscribers? The "re-publish" can only be run overnight when there is very little impact to users.
Bill Soranno
MCP, MCTS, MCITP DBA
Database Administrator
Winona State University
Maxwell 143
"Quality, like Success, is a Journey, not a Destination" - William Soranno '92
Hello-
A customer has reported getting the following excpetion in our logs, and I have never seen it before and wanted to see if there was any insight you could provide to understand when you throw this exception.
The process is a "purging" process- it just executes a sequence of DELETE statements that should be fairly simple (delete a number of records from a table and CHECK some constraints, no cascading), after the sequence it commits. All of this occurs on the same connection. We use c3p0 for connection pooling.
Here is the exception:
2008-03-22 08:30:08,699 WARN impl.NewPooledConnection : [c3p0] A PooledConnection that has already signalled a Connection error is still in use!
2008-03-22 08:30:08,699 WARN impl.NewPooledConnection : [c3p0] Another error has occurred [ com.microsoft.sqlserver.jdbc.SQLServerException: The server failed to resume the transaction. Desc:9f00000002. ] which will not be reported to listeners!
com.microsoft.sqlserver.jdbc.SQLServerException: The server failed to resume the transaction. Desc:9f00000002.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.doConnectionCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection$ConnectionCommandRequest.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectionCommand(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.rollback(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyConnection.rollback(NewProxyConnection.java:855)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.hibernate.jdbc.BorrowedConnectionProxy.invoke(BorrowedConnectionProxy.java:50)
at $Proxy15.rollback(Unknown Source)
at
In a high load asp.net environment, I am getting an error. The transation active in this session has been committed or aborted by another session.Here is the code , I am getting error. 1 object returnObject = null;
2 SqlTransaction sqlTrans = null;
3 try
4 {
5 //Getting new SqlConnection
6 comm.Connection = GetConnection();
7 //Opening connection
8 OpenConn(comm.Connection);
9 //beginning transaction
10 sqlTrans = comm.Connection.BeginTransaction( IsolationLevel.ReadCommitted );
11 //setting transaction to SqlCommand object
12 comm.Transaction = sqlTrans;
13 //executing operation
14 returnObject = comm.ExecuteScalar();
15 //trying to commit.
16 sqlTrans.Commit();
17
18
19 }
20 catch (SqlException sex)
21 {
22 if (sqlTrans != null)
23 {
24 sqlTrans.Rollback();
25 }
26 }
27 finally
28 {
29 comm.Connection.Close();
30 }
Could you please explain , am I doing smthg wrong ?
I want to use Transaction(MS DTC) in SSIS package across domain. It's working fine if both the servers are in Corpnet microsoft domain but failing it one of the server at extranet microsoft domain. I did all the required settings for MS DTC service to run for distrubuted transaction and in SSIS package did the "TransactionOption" property for the container object to "Required" and for all inner tasks to "Supported". Is it possible or a Security voilation which won't allow to do through SSIS package.
Example: I have a database on Extranet server and a database at Corpnet Server.
Sql Job will pull the data from Extranet Database to Corpnet database through SSIS package and update back to Extranet database. Job will reside on Corpnet server.
SSIS package is failing with the error message: The AcquireConnection method call to the connection manager "<Connection Manager name>" failed with error code 0xC0202009.
Any special setting do we require for this. I did the following setting on both the servers:
Ø MS DTC should run on both the servers under €œNetwork Service€?
Ø Set the following on both the servers(ExtranetCoptnet) to run on a Distributed Transaction:
§ Go to "Administrative Tools > Component Services"
§ On the left navigation tree, go to "Component Services > Computers
§ €œMy Computer" (you may need to double click and wait as some nodes
need time to expand)
§ Right click on "My Computer", select "Properties"
§ Select "MSDTC" tab
§ Click "Security Configuration"
§ Make sure you check "Network DTC Access", "Allow Remote Client",
"Allow Inbound/Outbound", "Enable TIP"
§ The service will restart
Note: If I will chage the Extranet server to Corpnet then it's working file for me.
Does anybody know what it means?
The context is: a package with a single Data Flow finishes with this error: [Connection manager "xxx"] Error: The connection manager failed to defect from the transaction.
All components inside the data flow reports a successfull green status, however the DataFlow Task remains yellow for a long time, when suddenly the package stops with the above message. Another information is that the table remains locked during package execution (a select on that table does not complete...). This is a serious issue, and I couldnt find any relevant information about that. Thanks in advance.
Hi,
We recently migrated our application from SQL Server 2000 to SQL Server 2005 and we also migrated from WAS5 to WAS6.
We are getting the following exception when we call any of the stored procedures.
The server failed to resume the transaction. Desc200000003.
Basically we call these stored procedures frequently using the Java thread scheduler.
We didnt face any problem when we use IBM drivers
I guess this is the problem with the drivers.We use JDBC 2005 driver Version 1.1.
But we didnt face this problems when we use JDBC 2000 driver when we used to connect to SQL Server 2000
The Microsoft says that it has fixed the date problems as well as the transaction problems in the version 1.1.But still are facing the issues.
Can anyone of you please help me in getting the solution for the same?
We had a siutation last night in our production environment that forced us to revert back to an earlier version of the database (before a major code rollout that failed). After restoring the days full backup (with NORECOVERY), and then restoring a DIFF backup (FULL RECOVERY and had checked Preserve Replication Settings)...the transaction replication failed.
Message #1
The replication agent has been successfully started. See the Replication Monitor for more information.
Message #2
2011-03-04 15:07:17.566 Copyright (c) 2008 Microsoft Corporation
2011-03-04 15:07:17.566 Microsoft SQL Server Replication Agent: logread
2011-03-04 15:07:17.566
2011-03-04 15:07:17.566 The timestamps prepended to the output lines are expressed in terms of UTC time.
2011-03-04 15:07:17.566 User-specified agent parameter values:
[code]....
I've tried reinitializing the publication/subscription and while that took brand new snapshots and copied it over to the replicated data server, it did not fix the problem.I read from a different post that I could try running "sp_replrestart" but that ran for about a half an hour and didn't appear to do anything but fill up our log files...did I not wait long enough?
The only thing I know to do at this point is to drop the publication on the production server and rebuild it completely (and with all the tables we're replicating that would take quite a bit of time.
Hi all,I am trying to setup a VB.Net development environment on my desktop for one of the application which was already in the production for couple of years (some unknown contractor(s) developed and maintained it so far). The application works fine on the web.Visual Studio 2005, .Net 2.0, SQL 2000, SQL Server 2005 were installed on my desktop. When I try to build the entire application/solution in the debug mode (i.e., with http://localhost/), build succeeds and I could get to the login.aspx. When I try to login, I am getting an error in the Visual Studio at the following code;connection = New SqlConnection(connectionString)
connection.Open()
saying "Communication with the underlying transaction manager has failed", "System.Transactions.TransactionManagerCommunicationException was unhandled by user code". And the web browser displays the following error "Error HRESULT E_FAIL has been returned from a call to a COM component". When I try to connect the SQL Server 2005 with the same ConnectionString attributes by going to Tools>Connect to Database, it works fine. But, through application connection.Open() giving above errors. I have set the MSDTC properties (i.e., under Component Services>MyComputer Properties>Security Configuration) as below:-Enabled Network DTC Access, Allow Remote Clients, Allow Remote Administration, Allow Inbound, Allow Outbound, No Authentication required - selected, Enabled XA Transactions...& DTC Logon Account is "NT AUTHORITYNetworkService".Please help.Thanks in advance,Chandra
I have a simple SSIS package with three "Execute SQL Tasks". I am using ADO.Net Connection to execute SPs on a DB server.
When I execute this package It works fine. So far so good.
Now, I need to implement transation on this package. And problem starts now onwards. When I try to execute package after setting TransationOption = Required for the Sequence container which contains all the tasks, I get following error.
[Execute SQL Task] Error: Failed to acquire connection "NYCDB0008.Export". Connection may not be configured correctly or you may not have the right permissions on this connection.
"NYCDB0008.Export" is the name of the ADO.Net connection. I have been hunting for any solution but all in vain. I have tried changing all DTC settings on the dev as well as Database server.
Please respond if anyone has any solution.
Thanks!
Anand