Network DTC/Transaction from 2000 to 2005 problems

Hello,

I am attempting to run a transaction via linked server from a 2000 instance to 2005 and receiving the 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].

When I run the same query over a linked server from a 2005 instance to the same 2005 instance mentioned above, it works fine.

Now, what's even more odd is that from the same 2000 instance mentioned above, I can hit other 2005 instances without error. This leads me to believe I have a network issues of sorts.

Summary:
- 2000 to 2005 transactions do not work to this specific 2005 instance
- 2000 to 2000 and all other 2005's work fine
- 2005 to 2005 transaction works fine
- Network DTC is enabled on both sides (inbound and outbound) with no authentication required

This specific 2005 instance is in it's own subnet meaning that there are of course some network limitations. I recently had port 1433 (SQL) opened in attempts to resolve this, but that has not helped. What other ports if any would be involved for DTC? I've heard 3372 and 135 (RPC).

Also, I have another server in that subnet that I just attempted the same thing on and I had the same results. I can hit the box fine from 2005 but not from 2000.

The fact that I can hit all other 2005 instances from 2000 without error and that I can hit this 2005 instance from 2005 and not 2000 has me baffled. Network? DTC? SQL2000 configuration?

Any help is greatly appreciated.

Thank you
MrBeanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MrBeanAuthor Commented:
That has already been completed.
0
rboyd56Commented:
Download DTCPing form this location:

http://www.microsoft.com/downloads/details.aspx?FamilyID=5e325025-4dcd-4658-a549-1d549ac17644&displaylang=en

It can be used to trouble shoot DTC problems
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

MrBeanAuthor Commented:
I think I have resolved it by allowing remote proc trans from the 2000 machine.
0
MrBeanAuthor Commented:
I lied, it's not working.
0
MrBeanAuthor Commented:
I used that DTCPing and received the following:

++++++++++++Validating Remote Computer Name++++++++++++
Please refer to following log file for details:
      C:\temp\DEVSQL3752.log
Invoking RPC method on SDVDB1
Problem:fail to invoke remote RPC method
Error(0x6D9) at dtcping.cpp @303
-->RPC pinging exception
-->1753(There are no more endpoints available from the endpoint mapper.)
RPC test failed

What is this telling me? I was told by the Network Admin that RPC is open between the two. As stated, I can Link Server Transaction query this server from any other 2005 machine without issue, it's only from 2000 that I can not perform this transaction. Yet any 2000 instance to any other 2000 or 2005 work just fine.
0
MrBeanAuthor Commented:
Hmmm, what is this all about when starting DTCPing?

"Please Start Partner DTCping before pinging"
0
MrBeanAuthor Commented:
Answered my own question. Installed and started it on the destination server then reran it from the source.

Now it looks better:

++++++++++++Validating Remote Computer Name++++++++++++
Please refer to following log file for details:
      C:\temp\DEVSQL6000.log
Invoking RPC method on SDVDB1
RPC test is successful
++++++++++++RPC test completed+++++++++++++++
++++++++++++Start DTC Binding Test +++++++++++++
Trying Bind to SDVDB1
0
MrBeanAuthor Commented:
Bind was successful as well.

I just ran it going the other way (2005 in its own network back to the 2000 in the main domain) and got the following:

++++++++++++Validating Remote Computer Name++++++++++++
Please refer to following log file for details:
      C:\Temp\SDVDB15716.log
Invoking RPC method on DEVSQL
Problem:fail to invoke remote RPC method
Error(0x6D9) at dtcping.cpp @303
-->RPC pinging exception
-->1753(There are no more endpoints available from the endpoint mapper.)
RPC test failed

But that is not the way the transaction is going ... still though, what is this telling me? Hopefully this help as I'm running out of ideas.
0
MrBeanAuthor Commented:
We temporarily allowed access between the networks and it worked perfectly, so this is definitely a port issue.

We have RCP (135) and SQL (1433) opened. Anything else I can check?
0
rboyd56Commented:
Not that I know of.
0
MrBeanAuthor Commented:
Was able to successfully resolve issue with this article: http://support.microsoft.com/default.aspx?scid=kb;en-us;250367
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.