II. No MSDTC of the two machines is open. Third. MSDTC settings are correct. 1. Open the command prompt, run "Net Stop MSDTC", then run "Net Start MSDTC". 2. Go to "Component Service Management Tools". 3. Browse to the "Startup Management Tool". 4. Select Component Services. A. Expand the Component Service tree and expand "My Computer". B. Right-click My Computer, then select Properties. C. In the MSDTC tab, make sure the following options are selected: Network DTC Access Network Management Network Transaction XA Transaction E. In addition, "DTC Login Account" must be set to "NT Authority / NetworkService". 5. Click OK. This will prompt you "MS DTC will stop and restart. All dependencies will be stopped. Please press 'Yes' Continue". Click Yes to continue. 6. Click OK to close the "My Computer" property window. IV. MSDTC depends on the RPC, the port used by the RPC is 135, whether the 135 port is opened. Is there a firewall? If there is a firewall, the Telnet IP 135 is turned off. 5. Some machines Due to various reasons ), SQLOLDB cannot use distributed transactions, change to "MSDasql" ODBC mode join. Using RRAS instead of RAS. (Control Isolated - Management Tool - Remote Service Manager) Check WHether You Are Using Remote Access Server (RAS) ) To access Ras (ras). Linked Server Does Not Work On Ras Because Ras Allows Only One Way Communication...... Check it out in the same domain. If it is not in the same domain, whether to establish a trustful join. Eight. If it is Win2000, upgrade to SP4 9. Upgrade MDAC to 2.6 or more, preferably 2.8. Ten. To install SQL's latest patch: sp3a 'all patch Location http://www.microsoft.com/downloads/details.aspx?displaylang=zh-cn&familyid=9032f608-160a-4537-a2b6-4cb265b80766 'should be installed patch SQL 2000 SP3 http://download.microsoft.com/ Download / D / D / D / DDE427EB-0296-4EAC-A47C-D11A66B03816 / CHS_SQL2KSP3.EXE I think: 1, the environment is important. 2, tools are important. (1) Doubt is a 135-port, use a tool to check the port to see that there is no problem with the port. (2) Under http://download/complus/msdtc/1.7/nt45/en-us/dtcping.exe tool, test, read Me, said by three steps, first step validation name , The second step to verify the RPC, the third step DTC, well, I actually found that the name verification did not pass, and I found that the NetBIOS of TCP / IP was turned off, and the cough DTC actually must be named. No ip. I service HE. 3. Computer that appears in the distance can only access the name to IP address, I have encountered the following.
