![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Hello all, This is really driving me crazy, any help will be appreciated. We have a Windows 2003 Server (no SP1) with VB6 COM+ components installed on it. We have a Windows 2003 Server (no SP1) with MSSQL 2000SP3a on the other side. No firewall between the two of any kind and both sit under the same domain and see each other clearly. DTCPing utility shows 100% success in all its tests between the servers. DTC Network Access is enabled (via the Add/Remove programs). Non-transactional queries from the app server to the db work 100%. The same DB machine serves other machine that have identical components as the problematic machine has (both on 2000 and 2003) and works 100%. I tried to connect the problematic app server to a different DB machine to see if that would help, but with the same result. Whenever a component tries to open a transaction, the following error comes up immediatley : "-2147168246 New transaction cannot enlist in the specified transaction coordinator. " I have read all posts regarding this in the groups as well as in the MSFT KB and to no avail - All tests either perform perfectly, or have nothing to do with the problem at hand. Any help would be appreciated, as I am coming close to the point of re-installing the whole app-server from scratch, as I cannot find anything wrong with it and yet this does not work. Any ideas? TIA, Liran |
![]() |
| Thread Tools | |
| Display Modes | |
| |