What are the challenges you face when working across database platforms? Take the survey

Aardvark 2 Issues

Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
edited February 27, 2004 9:26AM in Aardvark
Hi Jason,

Welcome to wonderfully secure Windows Server 2003. I think I know what
the problem here is. By default, Windows 03 does not install the component
that allows COM+ to utilize DTC.

Under add/remove programs/windows components/application server/ enable
network COM+ and Enable Network DTC access.

Please let us know if this takes care of it.


Brian Doanhue
Red Gate Technical Support

"Jason" <jasons@advaoptical.com> wrote in message
> Hi,
> We tried to upgrade our SQL server from W2k to W2k3 over the weekend, but
> have had several problems getting the front end web app talking to the SQL
> server. Our web server is IIS5 running on W2k server. Our old SQL server
> on W2k, and the new server is W2k3.
> The problem seems to be related to the ODBC connection. All the settings
> correct, and the connection tests okay, however, when pointed to this
> server, Aardvark just refuses to run, "freezing" when you try log in.
> When I start the COM objects, I get the following message in the web
> server's event log:
> MS DTC is unable to communicate with MSDTC on a remote system. No common
> protocol is supported between the two systems. Please Ensure that one or
> more of the following RPC protocols are common to both systems: TCP/IP,
> or NetBEUI. Error Specifics: iomgrclt.cpp:203, CmdLine:
> c:winntsystem32msdtc.exe PID 544
> Both machines run ONLY TCP/IP, and both machines have the service started.
> The built in firewall on the SQL server is disabled.
> As a last resort, I have resorted to running everything under the domain
> admin account, which has full access to the Aardvark database, and has
> configured as you say in the tech document. When I changed the ODBC
> connection from the new server back to the old, Aardvark immediately
> working again.
> Any help would be greatly appreciated, as we need to remove the old SQL
> server as soon as we can.
> Thanks,
> Jason
This discussion has been closed.