DTS gives error message

The problem is probably with the distributed transaction coordinator (DTC). The machine from which the data is coming from cannot see the machine to which you are transferring the data.

To remedy this:
Open up your hosts file
C:\WINNT\system32\drivers\etc\hosts
and add an entry into it that contains the name and IP of the target machine (i.e., the machine to which the data is sent).
Save the file, and try again.

These issues typically arise when the DNS entries in the domain that contains your database are not up to date, or some entries are missing.

Hope this helps,

Omri.

Hi:

Thanks for the quick reponse. I did make changes to the hosts but got the same error message. Do I need to reboot and try running the DTS packages?

sripri96

No. That should do it. Try to update the hosts file on both machines, and then do it.
Also - update the hosts file on both machines with the name and IP details of the machine at which you are managing the DTS (i.e., where Enterprise Manager is installed).

It can get a little tricky, based on your network domain configurations.
Do you have multiple domains? firewalls? Make sure that the adresses are correct by pinging (i.e., ping <MachineName>) or running telnet on port 1433 (i.e., telnet <MachineName> 1433) from all machines, to all machines involved in the distributed transaction.

I did ping the server and was able to do successfully. the other problem is when this job is run by job management tool, it runs fine but when we try to run from our machine it gives problem. we do have multiple domains and firewalls too.

The key here is to understand which addresses and machine names are visible by the machines that send/receive the DTS data. Lets denote by SExp and SImp the server that exports, and the server that imports the data, respectively.

It is possible that the machine that is running the job management tool is visible in the DNS server used by SInp and SExp, however the machine that you are running the DTS on (manually) is not.
Make sure that the addresses specified within each domain are the external addresses (i.e., you must be able to ping, or more correctly telnet over port 1433) from within the DB domain, to the machine that runs the Enterprise Manager used in the DTS process.

Please make sure that all machines can telnet and ping, using machine names (and not IPs!!!), and that all hosts files are updated for locally on all machines for which the telnet/ping is not successful.

There are several differences between the DTS and the job management tool:
DTS involves a 3rd machine that run the management of the DTS (i.e., I assume that in your setup, the box you are using Enterprise Manager to perform the DTS is neither SImp or SExp). This 3rd machine has to be properly defined in the DNS/hosts file, and must be visible from the SImp and SExp machines.
When you use the job management tool - The 3rd machine may not play any role in the DTS communication, therefore by the fact that SImp and SExp can resolve the IP of the job management machine, the DTS task will work fine, in spite of the fact that it does not work with the DTS in Enterprise Manager.

Please check all ping/telnet using machine names and not IP addresses, populate the hosts file on all the boxes for which the ping/telnet does not work, and post the outcome of the process.

We'll figure it out... just may take a little time :)

thanks a lot for the detailed information. So, does that mean that the each machine(box with Enterprise Manager) that tries to talk to SImp and SExp machines have to define the DNS/hosts file. Also, i pinged using machine name and was able to do successfully. This DTS works fine when I right click the DTS package, click properties, select advanced tab and uncheck the transactions option. This way I am able to run the DTS with needed results

i will try to do other steps you have mentioned and will post the updates.

Thanks once again!

 

Comment: When the transaction is not on, then the DTC is not activated, and the reverse lookup is not needed. That's why it works in that case.

i see...so, for each box(where enterprise manager exists) does the SImp and SExp machines have to define the DNS/hosts file and vice versa?

BTW - it is very simply to see whether a machine (within the same or another DMZ) is well defined in the DNS server. Simply run the following command on the command prompt:

nslookup <MachineName>

This command returns the DNS entries for that machine name, as seen in the DNS server used by the domain in which you run this command.

Hi:

I am unable to test some steps as discussed earlier. Thanks for all your help Obahat! May need some more time to test the steps.

Thanks,
sripri96