Today we installed on MS Cluster (W2k3) and SQL Server 2000 a MSDTC Service. The installation was succesfull, but wenn we try to move the group, then it failed. Because we have only 2 Disks on the cluster one for the Quorum, the other for the Sql Server. We installed the MSDTC as a Resource on the Quorum Disk. The other Thing, wenn we start the firts node all is running on the first node, but we cannot move. Wenn we start the second node all is running on the second node, but we cannot move the Group which contain the Msdtc resource.
We are trying to setup a Windows Server 2003 Cluster with 2 systems and a DAV. We intend to install SQL 2005 on this Cluster. We purchased a DAV with 3 physical disk arrays as follows.
73GB RAID 1 (our plan is to use this to store sql transaction logs) 146GB RAID 1 (sql backups, temp database & other temp files) 420GB RAID 10 (sql databases)
Now as we are setting all this up we find out we need a shared physical drive on the DAV to store the Quorom. It is my understanding we cannot partition the physical drives and use one of the partitions to store the Quorum because when you create the resource for the Quorum the resource is the phsyical disk not the partition.
So my question is, is it in our best interest to buy a seperate physical disk for the Quorom?
My next question is, with regards to the MSDTC, is it in our best interest to buy a seperate physical disk for the MSDTC or can we store it on the 146GB RAID 1 and still use the drive for its original purpose?
More often than not, I typically don't touch DTC on clusters anymore; however on a project where the vendor states that it's required. So a couple things here.
1) Do you really need DTC per instance or one for all? 2) Should DTC be in its own resource group or within the instance's group? 2a) If in it's own resource group, how do you tie an instance to an outside resource group? tmMappingSet right?
Is it possible to install and configure the MSDTC resource in a SQL Server 2000 cluster after SQL is installed and running?
When I recently went through a rebuild of my cluster, I forgot to install the resource before installing SQL Server. Now, if I install and bring online the MSDTC resource the SQL disk groups will not fail over correctly. The SQL Server resource will not come online.
Thanks in advance for any help. I would really like to avoid rebuilding again.
I need some instuctions about how to move a Microsoft cluster server from one network to the other.
I spent a few hours in Microsoft website and trie to find any document regarding reconfiguration of MSCS in different network, change IP address and any helpful procedures. I did not get anything. Would you please to give me any help document link, your experience or any workable procedures to move a MSCS from different network.
I found instructions on msdn for moving the system databases. However I am worried that in a cluster which is active/passive, when I shut down the instance the other instance will take over. Is there a way to take the other server off line to do the move and then bring it back online after we've moved everything? Has anyone done this before?
I have a SQL 2008 R2 2 node cluster. For DR testing, I need to restore an instance on a new server (completely isolated). The existing instance runs on what I would call an alias. The actual cluster host name is SQLPROD (cluster nodes are SQL01 and SQL02). The instance runs on server SQLPROD-APPLE. The instance is called APPLE. In production, I use SQL Management Studio and I connect to SQLPROD-APPLEAPPLE.
I've setup a new VM to run SQL. Not a cluster. Host name is SQLREC. The new Vm has all the IP addresses that were on the cluster and the DNS for all the aliases are correct. I've installed instance APPLE. I created an alias called SQLPROD-APPLE. When I try to open SQL Management Studio and connect, I can't connect to SQLPROD-APPLEAPPLE. I can connect to localhostAPPLE, SQLRECAPPLE, 192.168.168.50APPLE.
When I attempt to connect to the alias I get error 18452. Pinging the alias resolves correctly. I haven't gotten to the database restore yet, so that's not a concern. I'm just trying to validate the connection first with the correct server and instance names.
A Microsoft cluster, (SQL Failover cluster) with one node as the domain controller. The cluster was built off site and the domain name used is the same as our existing domain where we eventually need to install this cluster.
We need: (At least I think we need:)
To remove node 2 from the "cluster domain", DCPROMO node 1 and eliminate the "cluster domain". We then need to join the cluster (nodes) to the existing domain. We also need to recreate the accounts/groups used during installation.
Questions:
1) What adverse impact will the removal of the "cluster domain" have on the security groups/accounts used in the installation?
2) Will I have to re-install SQL 2005?
3) Is my paranoia real or imagined? (Will Elvis live?) Am I on the right track or totally off base?
Any prior experience with this would be greatly appreciated. In fact, a WAG is appreciated too.
During the installation of Adding node to a SQL Server failover cluster(On passive node) getting error like.. The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.We run the below commands but didn’t get any resolution & got the same above error .
1<sup>st</sup> Method…
1. Open console command (Run->CMD with administrator privileges).
2. net stop winmgmt
3. Rename folder %windir%System32WbemRepository to other one, for backup purposes (for example _Repository).
I am in the process of moving databases from a SQL 2005 Standard version to a 2-node 2014 cluster.All of my 2005 databases back up successfully.They all restore without issue except for one database that has a full text catalog. I get this message
Msg 7610, Level 16, State 1, Line 2 Access is denied to "fileStoragedataMSSQLSERVERFullTextCatalog", or the path is invalid. Msg 3156, Level 16, State 50, Line 2 File 'sysft_FTCatalog' cannot be restored to 'fileStoragedataMSSQLSERVERFullTextCatalog'. Use WITH MOVE to identify a valid location for the file. Msg 3119, Level 16, State 1, Line 2 Problems were identified while planning for the RESTORE statement. Previous messages provide details. Msg 3013, Level 16, State 1, Line 2 RESTORE DATABASE is terminating abnormally.
[code]....
I went as far as giving the folder full access to everyone temporarily and received the same error.
Can I build a cluster by adding the cluster service, then the SQL instances, then add the other nodes and their passive SQL instances?I would lean to building the cluster first, the add the SQL instances.
Trying to locate information on MSDTC. Is this "needed" to run SQL Server? That is, if this part of the installation is deleted, will SQL Server still function? Also, does anyone know if this is a crucial tool needed by Veritas Volume Manager or Windows Disk Manager?
If anyone knows of a link to this information, I'd appreciate it. My searches come up with lots on information on MSDTC, but nothing that answers my specific questions.
When i do a BEGIN TRAN to a SQL server sitting on Windows 2003 Server from a SQL Server Sitting on Windows 2000 Server, the Transaction hangs and if I try o kill it the Transaction is in ROLLBACK State.
I tried setting the Properties for the MSDTC and restarted the Windows 2003 Server but in vain
I keep getting this error on my application server...what does it mean?The description for Event ID ( 0 ) in Source ( ODBC ) cannot be found.The local computer may not have the necessary registry information ormessage DLL files to display messages from a remote computer. Thefollowing information is part of the event: Failed to enlist in DTC:SQL state 37000, native error 8501, error message [Microsoft][ODBC SQLServer Driver][SQL Server]MSDTC on server 'PROSQL' is unavailable..any help would be appreciated...thanks-Jim
I'm using msde. On the little icon in task tray, you have under currentservice, a choice of mssqlserver, and another choice is msdtc. What ismsdtc? And what is sqlserver agent?
The resource msdtc is down. Every time, it works pretty well , after we restart the servers(node1 and node2). But, about half a hour later, the problem is there. We reintalled msdtc. It didn't work out too. msdtc and sql server is on a cluster. Can anyone help me out?
I am running SQl 7.0 (SP4) on Windows XP Professional (SP2). Whenever I try an insert/update type of activity, the System returns the following message :
Server: Msg 8501, Level 16, State 3, Line 2 MSDTC on server 'SERVER' is unavailable.
However, all the required services including MSDTC are running on the System.
I have following script which i am planning to run to drop all non-clustered primary keys on a database and then created as clustered. I am using someone else's script so don't know how to modify this. Some of primary key columns are used in references in other tables.
is there anyway i can drop the existing primary keys and using their original script then create again as clustered including restoring all foreign and reference keys and unique or no unique.
DECLARE @table NVARCHAR(512), @tablename NVARCHAR(512), @sql NVARCHAR(MAX), @sql2 NVARCHAR(MAX), @sql3 NVARCHAR(MAX), @column NVARCHAR(MAX); DECLARE @indexname NVARCHAR(512); SELECT name As 'Table'
We are planning to change all IPs of PRODUCTION Failover Cluster Setup. In my cluster setup ... we have 2 Physical Nodes with windows-2008, Roles are MSDTC and SQL-2008R2.
IP change for:
1. Both Nodes(Physical) 2. MSDTC 3. SQL Server 4. windows Cluster
So Almost... All IPs are going to change.
Im DBA here, I need to take care of SQL cluster and MSDTC. But I haven't performed this activity before.So I'm worrying about Impacts and consequences of this change. steps how should I perform this activity.
I have a class that use a TransactionScope object for make make two operations into a database. The problem is that in a computer works well but in another I receive a error message: "MSDTC is not running in .SQLEXPRESS". I had watched the services in the computer and the "Microsoft Distributed Transaction Coordinator" is running. Does somebody know what is happening? Thankyou and sorry for my English.
I am selectively insert data from serverA databaseX to serverB databaseX. (serverA is linked server on B.)
I could insert parent and child tables. But get error when insert to grand-child tables: Server: Msg 8501, Level 16, State 3, Line1 MSDTC on server B is unavailable.
Don't think I need to turn on MSDTC on B. But I could copy and paste from source A server to target B server. Confusing on some table could insert while others with error....
I have an ugent situation. Due to a failure we had to build a new db server for an application and this was done succuessfully. The application requires DTC and it was not intalled when we install SQL on the server.
How do I install DTC? Did I miss an obscure option during SQL install?
I recently moved & upgraded a database from 7.0 to 2000 that makes use of linked servers. After upgrading, a number of queries started failing with the error below. These linked servers with this problem either had a stopped MSDTC or were behind a firewall. I've read the articles on how to configure MSDTC to work through a firewall, but before I do this I'm wondering why this is even happening. There were no problems when the database was at SQL 7.0. Does anyone know why sql 2000 would need to use MSDTC, but SQL7.0 would not? I don't need to use a distributed transaction, so ideally I'd like to somehow tell SQL not to use MSDTC at all. Any ideas?
Thanks
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].
The following code:DECLARE @tsql varchar(1000)CREATE TABLE #Test (...)SET @tsql = 'SELECT * FROM OPENQUERY(MyDataSource, ...)'INSERT INTO #Test EXEC(@tsql)generates the following error message at the insert statement:Server: Msg 8501, Level 16, State 3, Line 4MSDTC on server 'MyComputer' is unavailable.Why?Thanks,Tony PerovicCompumation, Inc.
I have a SSIS package in which there are lot of Sequence Containers. Each sequence container has two Execute Sql tasks which brings 2 values, and if the comparison of the value is true, it runs a data flow task. Comparison is done using Expression.
If any of the sequence container fails the comparison, I wanted whole package to rollback so I had to use Transactions. I set "Required Transaction" on the package and "Supports Transaction" on each Sequence Container and Tasks respectively.
Now that I am trying to run the package, it runs few sequence containers fine and on few it gives this error.
[Execute SQL Task] Error: Executing the query "SELECT ISNULL(MAX(ClaimBillTypeKey), -1) ClaimBillTypeKey FROM dbo.Dim_ClaimBillType" failed with the following error: "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Also, this is not consistent, one time one Seq. Cont will fail and next time it will run fine but something else will fail. What is going on????
I have set up two server and also created linked server between server1 to server2
I could select from there just fine but when i try to run tirgger on table server1 which updates in server2 it gives me error following: OLE DB provider "SQLNCLI" for linked server "Server2" return message "No Transaction is active" MSG 7391, level 16, state 2, Procedure servertrigger, line 34 the operation could not be performed because OLE DB provider "SQLNCLI" for linked sever "SErver2" was unbale to begin a distributed transaction.
I have configured on both server exactly same: with all the option: MSDTC > Security Configuration: Network DTC Access > TRUE Allow Remote Clients > TRUE Allow Remote Administration > TRUE Allow Inbound > TRUE Allow Outbound > TRUE Mutual Authentication Required > TRUE Enable Transaction Internet Protocol (TIP) Transactions > TRUE Enable XA Transactions > TRUE Account: NT AuthorityNetworkService on both server..
On server2 i tried remote proc trans to on and off but it did not help.
INSERT TABLE1 -- ran at SERVER1 EXEC [SERVER2].DB2.dbo.spInformation @VR_STARTSHIFT = '10/10/2006 06:00:00', @VR_INCDATE = '10/10/2006 14:00:00', @VR_STATION_ID = 221
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].
Server1 has a linked server to Server2 (this linked server is working because i can run the SP without the insert). The Server1 is under WIN2K Server and Sever2 is under WIN2003 The MSDTC is installed and is running in both servers.
