Econnect / XP SP2 / issues

Hello there,

We'd been using the econnect client on a computer running Windows XP Pro SP1 
for quite sometime with no trouble at all. But ever since the operating 
system was upgraded to SP2, the econnect stopped working.
We think that the Windows XP SP2 firewall might have something to do with 
this trouble; but even though we turned it off, the error remains.
We're using the econnect sending utility to connect to a SQL Server 2000 SP4 
server running on Windows 2K SP4 via a DSN.
We get the following error:

Error number = -2147168246
Error description = New transaction cannot enlist in the specified 
transaction coordinator.
Error source = Microsoft OLE DB Provider for SQL Server

After some research, we found that this error could be related to the MS DTC 
service; but given that this worked before installing the Windows XP SP2 on 
the client, we think that this isn't the real issue.

Is there any technical article on how to configure the econnect on Windows 
XP Pro and the issues that may arise after installing the SP2?
Perhaps an article on extra settings that we most consider when using the 
econnect on Win XP Pro SP2 ?

Thanks in advance,
Cesar
0
Cesar (59)
6/6/2006 10:20:02 PM
greatplains 29623 articles. 6 followers. Follow

3 Replies
376 Views

Similar Articles

[PageSpeed] 8

Hi there,

We just solved it !!!!  =)
Thanks anyway.
Cesar

"Cesar" wrote:

> Hello there,
> 
> We'd been using the econnect client on a computer running Windows XP Pro SP1 
> for quite sometime with no trouble at all. But ever since the operating 
> system was upgraded to SP2, the econnect stopped working.
> We think that the Windows XP SP2 firewall might have something to do with 
> this trouble; but even though we turned it off, the error remains.
> We're using the econnect sending utility to connect to a SQL Server 2000 SP4 
> server running on Windows 2K SP4 via a DSN.
> We get the following error:
> 
> Error number = -2147168246
> Error description = New transaction cannot enlist in the specified 
> transaction coordinator.
> Error source = Microsoft OLE DB Provider for SQL Server
> 
> After some research, we found that this error could be related to the MS DTC 
> service; but given that this worked before installing the Windows XP SP2 on 
> the client, we think that this isn't the real issue.
> 
> Is there any technical article on how to configure the econnect on Windows 
> XP Pro and the issues that may arise after installing the SP2?
> Perhaps an article on extra settings that we most consider when using the 
> econnect on Win XP Pro SP2 ?
> 
> Thanks in advance,
> Cesar
0
Cesar (59)
6/7/2006 4:05:01 PM
what was the issue?
"Cesar" <Cesar@discussions.microsoft.com> wrote in message 
news:ECFF8A9D-F138-4D47-BA87-1E4D4F4D91DC@microsoft.com...
> Hi there,
>
> We just solved it !!!!  =)
> Thanks anyway.
> Cesar
>
> "Cesar" wrote:
>
>> Hello there,
>>
>> We'd been using the econnect client on a computer running Windows XP Pro 
>> SP1
>> for quite sometime with no trouble at all. But ever since the operating
>> system was upgraded to SP2, the econnect stopped working.
>> We think that the Windows XP SP2 firewall might have something to do with
>> this trouble; but even though we turned it off, the error remains.
>> We're using the econnect sending utility to connect to a SQL Server 2000 
>> SP4
>> server running on Windows 2K SP4 via a DSN.
>> We get the following error:
>>
>> Error number = -2147168246
>> Error description = New transaction cannot enlist in the specified
>> transaction coordinator.
>> Error source = Microsoft OLE DB Provider for SQL Server
>>
>> After some research, we found that this error could be related to the MS 
>> DTC
>> service; but given that this worked before installing the Windows XP SP2 
>> on
>> the client, we think that this isn't the real issue.
>>
>> Is there any technical article on how to configure the econnect on 
>> Windows
>> XP Pro and the issues that may arise after installing the SP2?
>> Perhaps an article on extra settings that we most consider when using the
>> econnect on Win XP Pro SP2 ?
>>
>> Thanks in advance,
>> Cesar 


0
jacktundra (359)
6/7/2006 4:13:45 PM
the XP SP2 firewall blocks the MSDTC service.

"Jack Tundra" wrote:

> what was the issue?
> "Cesar" <Cesar@discussions.microsoft.com> wrote in message 
> news:ECFF8A9D-F138-4D47-BA87-1E4D4F4D91DC@microsoft.com...
> > Hi there,
> >
> > We just solved it !!!!  =)
> > Thanks anyway.
> > Cesar
> >
> > "Cesar" wrote:
> >
> >> Hello there,
> >>
> >> We'd been using the econnect client on a computer running Windows XP Pro 
> >> SP1
> >> for quite sometime with no trouble at all. But ever since the operating
> >> system was upgraded to SP2, the econnect stopped working.
> >> We think that the Windows XP SP2 firewall might have something to do with
> >> this trouble; but even though we turned it off, the error remains.
> >> We're using the econnect sending utility to connect to a SQL Server 2000 
> >> SP4
> >> server running on Windows 2K SP4 via a DSN.
> >> We get the following error:
> >>
> >> Error number = -2147168246
> >> Error description = New transaction cannot enlist in the specified
> >> transaction coordinator.
> >> Error source = Microsoft OLE DB Provider for SQL Server
> >>
> >> After some research, we found that this error could be related to the MS 
> >> DTC
> >> service; but given that this worked before installing the Windows XP SP2 
> >> on
> >> the client, we think that this isn't the real issue.
> >>
> >> Is there any technical article on how to configure the econnect on 
> >> Windows
> >> XP Pro and the issues that may arise after installing the SP2?
> >> Perhaps an article on extra settings that we most consider when using the
> >> econnect on Win XP Pro SP2 ?
> >>
> >> Thanks in advance,
> >> Cesar 
> 
> 
> 
0
Cesar (59)
6/9/2006 10:51:23 PM
Reply:

Similar Artilces: