I have just moved several SQL Server databases from a SQL Server 7.0
with NT OS to a SQL Server 7.0 with Windows 2000 OS. Each of these
databases are accessed via web server. I have no problems connecting to
the db when I set up the ODBC connection and all of the databases are
functional.

I moved the databases by backing them up on the current system, creating
a blank database on the new server with the same db names and then
moving the backups to the new server and restoring db from file forcing
an overwrite.

My problem now is that when I try to do anything on the web server, I
get an error message dealing with the transaction coordinator.

The actual message that comes up on the screen is this:

*modMTSAppDO.GetConnection - Microsoft OLE DB Provider for SQL Server
Line #: 114 error '8004d00a'

New transaction cannot enlist in the specified transaction coordinator.

I am stuck and haven't had much luck searching the web for assistance.
Most of the assistance deals with firewall issues. I do not have a
firewall between the Web server and the SQL Server. Each server has the
latest upgrades and service packs.

I am still having issues. I read on Technet to download a program called
DTCPing on both systems. I did so and tried it. It stated that both
systems were communicating, however I am still getting errors when I
attempt to work from the web based system. Below is a copy of the error
message I receive.


Description: New transaction cannot enlist in the specified transaction
coordinator.

Any and all help is greatly appreciated. I'm dead in the water until I
get this resolved.

I am also getting this error in my error log.

*modMTSAppDO.GetConnection - Microsoft OLE DB Provider for SQL Server
Line #: 114 error '8004d01c'

MSDTC on server 'NC-37350-APP09' is unavailable.




Any and all help is appreciated.

Tod




*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Have you tried doing a ping {servername} from the web
server to the DB server?

I would use 'CLICONFG' and check your "Alias" section to ensure the proper connections are there. I can't guaranty that this is the solution, but I recall getting a similar error after doing some patches/updates. If nothing else you will have a new tool in your pouch.