Error message: OLE DB provider SQLOLEDB was unable to begin a distributed transaction
2005-01-27 13:40
609 查看
SYMPTOMS
When you try to use Microsoft SQL Server 2000 to start a distributed transaction between linked servers that are running Windows Server 2003, you may receive the following error message:OLE DB provider SQLOLEDB was unable to begin a distributed transactionThe following message may appear on the OLE DB provider computer:
New transaction cannot enlist in the specified transaction coordinator.
CAUSE
This behavior occurs because security features in Windows Server 2003 introduce changes that interfere with the way this program functions. By default, Microsoft Distributed Transaction Coordinator (MSDTC) is disabled in Windows Server 2003.WORKAROUND
To work around this behavior, install network DTC access on both servers:1. | Click Start, and then click Control Panel. |
2. | Click Add or Remove Programs, and then click Add/Remove Windows Components. |
3. | In the Components box, click Application Server, and then click Details. |
4. | Click to select the Enable network DTC access check box, and then click OK. |
5. | Click Next, and then follow the instructions that appear on the screen to complete the installation process. |
6. | Stop and then restart the Distributed Transaction Coordinator service. |
7. | Stop and then restart any resource manager services that participates in the distributed transaction (such as Microsoft SQL Server or Microsoft Message Queue Server). |
• | Microsoft Windows Server 2003, Web Edition |
• | Microsoft Windows Server 2003, Standard Edition |
• | Microsoft Windows Server 2003, Enterprise Edition |
• | Microsoft SQL Server 2000 Standard Edition |
• | Microsoft Windows Small Business Server 2003 Premium Edition |
• | Microsoft Windows Small Business Server 2003 Standard Edition |
相关文章推荐
- MS SQL 错误:The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "test" was unable to begin a distributed transaction.
- Linked server was unable to begin a distributed transaction----it works for me.
- OLE DB provider SQLOLEDB supplied inconsistent metadata. An extra column was supplied during execution that was not found at com
- A rowset based on the SQL command was not returned by the OLE DB provider
- A rowset based on the SQL command was not returned by the OLE DB provider
- linked server "XXX" was unable to begina distributed transaction.
- Unable to begin a distributed transaction
- 星外虚拟主机管理平台 开通数据库 出现Microsoft OLE DB Provider for SQL Server 错误 '8004' 从字符串向 datetime 转换失败
- Microsoft OLE DB Provider for SQL Server 错误 '80040e4d'
- Microsoft OLE DB Provider for SQL Server 错误 '80040e21'
- ORA-04031: unable to allocate 4096 bytes of shared memory ("shared pool","BEGIN :EXEC_STR := SYS.DBMS...","PL/SQL MPCODE","BAMIM
- Microsoft OLE DB Provider for SQL Server 错误 '80040e14' 列名 'xxx' 无效。
- Use Jet OLE DB Provider 4.0 to Connect to ISAM Databases (连接Excel, Text等数据库)
- oracle unable to load oraMTS , unable to enlist in a distributed transaction .
- How to build an OLE DB application for SQL Server CE in Visual Studio 2005
- System.InvalidCastException: Unable to cast object of type SqlDataProvider to type DataProvider
- Microsoft OLE DB Provider for SQL Server 错误 '80040e14' 全文操作运行失败。查询子句只包含被忽略的词。
- Microsoft OLE DB Provider for SQL Server (0x80004005)
- Microsoft OLE DB Provider for SQL Server 错误 '80040e2f'
- “Microsoft OLE DB Provider for SQL Server 错误 '80040e09',拒绝了对对象 'Art_Config' (数据库 'GY_SFJ',架构 'dbo')”