Error opening socket

The incident involves two Windows Server 2003 based computers S and C. They
are hosted by two different hosting companies in two different countries.
They both have SQL Server 2000 SP3 installed and running.
The development is done on an XP Professional SP2 based desktop.
The objective is to make a SQL instance on C act as client of an instance on
S which listens on port TCP 1433. The registration of the S instance in SQL
Server Enterprise Manager on C has been successful. However the connection
fails.
Consequently I tried to use various diagnostic tools and hints given in
various KB articles.
PING works OK. FTP connection also works fine.
PortQry from C to S gives the following result:
==========================================
Starting portqry.exe -n <IPaddress of S>-e 1433 -p TCP ...
Querying target system called:
<IPaddress of S>-
Attempting to resolve IP address to a name...
IP address resolved to <correct computer name of S>
querying...
Error opening socket: 10065
No route to host.
portqry.exe -n <IPaddress of S>- -e 1433 -p TCP exits with return code
0x00000063.
===========================================
The same query from the development computer gives the result LISTENING.
Questions:
1. What exactly means Error opening socket: 10065? How should I fix the
problem?
2. Why does the result depend on the computer which makes the query?
Thanks, Dan
10065 equates to a Winsock Error, Host Unreachable.
This sounds like a tcp routing issue.
Try using tracert to the same host /IP address.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Error opening socket

The incident involves two Windows Server 2003 based computers S and C. They
are hosted by two different hosting companies in two different countries.
They both have SQL Server 2000 SP3 installed and running.
The development is done on an XP Professional SP2 based desktop.
The objective is to make a SQL instance on C act as client of an instance on
S which listens on port TCP 1433. The registration of the S instance in SQL
Server Enterprise Manager on C has been successful. However the connection
fails.
Consequently I tried to use various diagnostic tools and hints given in
various KB articles.
PING works OK. FTP connection also works fine.
PortQry from C to S gives the following result:
========================================
==
Starting portqry.exe -n <IPaddress of S>-e 1433 -p TCP ...
Querying target system called:
<IPaddress of S>-
Attempting to resolve IP address to a name...
IP address resolved to <correct computer name of S>
querying...
Error opening socket: 10065
No route to host.
portqry.exe -n <IPaddress of S>- -e 1433 -p TCP exits with return code
0x00000063.
========================================
===
The same query from the development computer gives the result LISTENING.
Questions:
1. What exactly means Error opening socket: 10065? How should I fix the
problem?
2. Why does the result depend on the computer which makes the query?
Thanks, Dan10065 equates to a Winsock Error, Host Unreachable.
This sounds like a tcp routing issue.
Try using tracert to the same host /IP address.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Error on Report based on Analysis Services

I've got most of my first stab at using Reporting Services. I am using the
Report Viewer control in VS 2005. When I point it at a report based on
standard TSQL it runs. My next query is based on Analysis Services. It runs
via the URL when I login as an Administrator but I get the following error
when I do it via the Report Viewer. The problem is the web server can't
"see" itself (i.e. typing the URL of the ASP.net page doesn't seem to work)-
something which I will get the network people to look at tomorrow so I can't
see a more detailed error. I am just starting trying to get an understanding
of roles etc but some pointers would be great. Regards, Chris.
a..
An error has occurred during report processing. a.. Query execution failed
for data set 'Analysis_Services_Project1'. a.. For more information about
this error navigate to the report server on the local server machine, or
enable remote errors a..I figured it out - I needed to add the IUSR as a role to the Analysis
Services DB.
"Fresno Bob" <nospam@.nospam.com> wrote in message
news:%23QvrOp98HHA.3940@.TK2MSFTNGP05.phx.gbl...
> I've got most of my first stab at using Reporting Services. I am using the
> Report Viewer control in VS 2005. When I point it at a report based on
> standard TSQL it runs. My next query is based on Analysis Services. It
> runs via the URL when I login as an Administrator but I get the following
> error when I do it via the Report Viewer. The problem is the web server
> can't "see" itself (i.e. typing the URL of the ASP.net page doesn't seem
> to work)- something which I will get the network people to look at
> tomorrow so I can't see a more detailed error. I am just starting trying
> to get an understanding of roles etc but some pointers would be great.
> Regards, Chris.
> a..
> An error has occurred during report processing. a.. Query execution failed
> for data set 'Analysis_Services_Project1'. a.. For more information about
> this error navigate to the report server on the local server machine, or
> enable remote errors a..
>

Error Number: -2147217900

we have an ASP based intranet application that creates a job, adds the steps
and starts the job all using ASP script. This is working for many years
without any issue. The reason we went this route is to see the activities of
this job from another ASP page in an asynchronized way. But lately we ran
into the following error. Any help/clu on this is appreciated.
Error Creating SQL Job failed
Error information:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Number: -2147217900
Error Description: Distributed transaction completed. Either enlist this
session in a new transaction or the NULL transaction.
Can anyone lend some help on this please?
"MSFT Developer" <MSFTDeveloper@.DeveloperNet.Net> wrote in message
news:O9CZhqukFHA.3336@.tk2msftngp13.phx.gbl...
> we have an ASP based intranet application that creates a job, adds the
> steps and starts the job all using ASP script. This is working for many
> years without any issue. The reason we went this route is to see the
> activities of this job from another ASP page in an asynchronized way. But
> lately we ran into the following error. Any help/clu on this is
> appreciated.
> Error Creating SQL Job failed
> Error information:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Number: -2147217900
> Error Description: Distributed transaction completed. Either enlist this
> session in a new transaction or the NULL transaction.
>
>
>

Error Number: -2147217900

we have an ASP based intranet application that creates a job, adds the steps
and starts the job all using ASP script. This is working for many years
without any issue. The reason we went this route is to see the activities of
this job from another ASP page in an asynchronized way. But lately we ran
into the following error. Any help/clu on this is appreciated.
Error Creating SQL Job failed
Error information:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Number: -2147217900
Error Description: Distributed transaction completed. Either enlist this
session in a new transaction or the NULL transaction.Can anyone lend some help on this please?
"MSFT Developer" <MSFTDeveloper@.DeveloperNet.Net> wrote in message
news:O9CZhqukFHA.3336@.tk2msftngp13.phx.gbl...
> we have an ASP based intranet application that creates a job, adds the
> steps and starts the job all using ASP script. This is working for many
> years without any issue. The reason we went this route is to see the
> activities of this job from another ASP page in an asynchronized way. But
> lately we ran into the following error. Any help/clu on this is
> appreciated.
> Error Creating SQL Job failed
> Error information:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Number: -2147217900
> Error Description: Distributed transaction completed. Either enlist this
> session in a new transaction or the NULL transaction.
>
>
>|||Go to MSDTC time out settings and increase the Transaction timeout to
some appropriate value(greater then what it was before). if the error
was caused due to tranaction timeouts then this is the solution. Other
wise NO CLUE :-(
maicalal
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1757334.html|||Go to MSDTC time out settings and increase the Transaction timeout to
some appropriate value(greater then what it was before). if the error
was caused due to tranaction timeouts then this is the solution. Other
wise NO CLUE :-(
maicalal
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1757334.html

Error Number: -2147217900

we have an ASP based intranet application that creates a job, adds the steps
and starts the job all using ASP script. This is working for many years
without any issue. The reason we went this route is to see the activities of
this job from another ASP page in an asynchronized way. But lately we ran
into the following error. Any help/clu on this is appreciated.
Error Creating SQL Job failed
Error information:
Error Source: Microsoft OLE DB Provider for SQL Server
Error Number: -2147217900
Error Description: Distributed transaction completed. Either enlist this
session in a new transaction or the NULL transaction.Can anyone lend some help on this please?
"MSFT Developer" <MSFTDeveloper@.DeveloperNet.Net> wrote in message
news:O9CZhqukFHA.3336@.tk2msftngp13.phx.gbl...
> we have an ASP based intranet application that creates a job, adds the
> steps and starts the job all using ASP script. This is working for many
> years without any issue. The reason we went this route is to see the
> activities of this job from another ASP page in an asynchronized way. But
> lately we ran into the following error. Any help/clu on this is
> appreciated.
> Error Creating SQL Job failed
> Error information:
> Error Source: Microsoft OLE DB Provider for SQL Server
> Error Number: -2147217900
> Error Description: Distributed transaction completed. Either enlist this
> session in a new transaction or the NULL transaction.
>
>
>

Error Msg 7391 in distributed transaction

I have a procedure which is trying to insert data into a table on Server A.
This insert is done based ona return value from a select statement from
Server B . A linked server has been set up for Server B on server A. The
error when populating table by inserting data is
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB'
was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the
specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a].
Is there any other way to get thsi work. TIA
Message posted via http://www.webservertalk.comYou want to start with this kb for your troubleshooting.
http://support.microsoft.com/kb/306212
-oj
"ishaan99 via webservertalk.com" <forum@.webservertalk.com> wrote in message
news:e4a371938b9f454d851da07f5c672039@.SQ
webservertalk.com...
>I have a procedure which is trying to insert data into a table on Server A.
> This insert is done based ona return value from a select statement from
> Server B . A linked server has been set up for Server B on server A. The
> error when populating table by inserting data is
> Server: Msg 7391, Level 16, State 1, Line 1
> The operation could not be performed because the OLE DB provider
> 'SQLOLEDB'
> was unable to begin a distributed transaction.
> [OLE/DB provider returned message: New transaction cannot enlist in the
> specified transaction coordinator. ]
> OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a].
> Is there any other way to get thsi work. TIA
> --
> Message posted via http://www.webservertalk.com