|
|
You're in the
sql server connect
group:SQL 2005 64bit ODBC Connections to AS400
sql server connect:
The server is Windows 2003 R2 64 bit with SQL 2005 SP1 Standard Edition (64bit) Using the Iseries Access ODBC drivers I've created a system DSN called MSSQL_GACUPR01 (I have both 64 and 32 bit drivers from IBM and have each) From there i've created a Linked server using SQL Native client: EXEC master.dbo.sp_addlinkedserver @server = N'CTSACURITYINT', @srvproduct=N'DB2', @provider=N'SQLNCLI', @datasrc=N'MSSQL_GACUPR01' However I get the error: OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message "Login timeout expired". OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". Msg 53, Level 16, State 1, Line 0 Named Pipes Provider: Could not open a connection to SQL Server [53].
With Named pipes turned off I get the error,:
OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message "Login timeout expired". OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". Msg 11001, Level 16, State 1, Line 0 TCP Provider: No such host is known. [quoted text, click to view] "RichardT" wrote:
> I'm having problems setting up an ODBC Connection to AS400 > The server is Windows 2003 R2 64 bit with SQL 2005 SP1 Standard Edition > (64bit) > > Using the Iseries Access ODBC drivers I've created a system DSN called > MSSQL_GACUPR01 (I have both 64 and 32 bit drivers from IBM and have each) > > From there i've created a Linked server using SQL Native client: > > EXEC master.dbo.sp_addlinkedserver @server = N'CTSACURITYINT', > @srvproduct=N'DB2', @provider=N'SQLNCLI', @datasrc=N'MSSQL_GACUPR01' > > However I get the error: > > > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message > "Login timeout expired". > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message > "An error has occurred while establishing a connection to the server. When > connecting to SQL Server 2005, this failure may be caused by the fact that > under the default settings SQL Server does not allow remote connections.". > Msg 53, Level 16, State 1, Line 0 > Named Pipes Provider: Could not open a connection to SQL Server [53]. > >
The host DB2 machine can be pinged from the SQL 2005 server and name
resolution is working corrrectly [quoted text, click to view] "RichardT" wrote:
> With Named pipes turned off I get the error,: > > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message > "Login timeout expired". > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message > "An error has occurred while establishing a connection to the server. When > connecting to SQL Server 2005, this failure may be caused by the fact that > under the default settings SQL Server does not allow remote connections.". > Msg 11001, Level 16, State 1, Line 0 > TCP Provider: No such host is known. > > > "RichardT" wrote: > > > I'm having problems setting up an ODBC Connection to AS400 > > The server is Windows 2003 R2 64 bit with SQL 2005 SP1 Standard Edition > > (64bit) > > > > Using the Iseries Access ODBC drivers I've created a system DSN called > > MSSQL_GACUPR01 (I have both 64 and 32 bit drivers from IBM and have each) > > > > From there i've created a Linked server using SQL Native client: > > > > EXEC master.dbo.sp_addlinkedserver @server = N'CTSACURITYINT', > > @srvproduct=N'DB2', @provider=N'SQLNCLI', @datasrc=N'MSSQL_GACUPR01' > > > > However I get the error: > > > > > > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message > > "Login timeout expired". > > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned message > > "An error has occurred while establishing a connection to the server. When > > connecting to SQL Server 2005, this failure may be caused by the fact that > > under the default settings SQL Server does not allow remote connections.". > > Msg 53, Level 16, State 1, Line 0 > > Named Pipes Provider: Could not open a connection to SQL Server [53]. > > > >
Did the DSN test successfully. If yes, then go ahead and create the linked
server using Management studio and check the behavior. I guess we are missing some additional attributes in the linked server properties(if the DSN is successful). -- Bindesh Vijayan- SQL Developer Support [This posting is provided "AS IS" with no warranties, and confers no rights] [quoted text, click to view] "RichardT" <RichardT@discussions.microsoft.com> wrote in message
news:24E17ED6-B227-4A10-87CD-30C834FEBFDE@microsoft.com... > The host DB2 machine can be pinged from the SQL 2005 server and name > resolution is working corrrectly > > "RichardT" wrote: > >> With Named pipes turned off I get the error,: >> >> OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned >> message >> "Login timeout expired". >> OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned >> message >> "An error has occurred while establishing a connection to the server. >> When >> connecting to SQL Server 2005, this failure may be caused by the fact >> that >> under the default settings SQL Server does not allow remote >> connections.". >> Msg 11001, Level 16, State 1, Line 0 >> TCP Provider: No such host is known. >> >> >> "RichardT" wrote: >> >> > I'm having problems setting up an ODBC Connection to AS400 >> > The server is Windows 2003 R2 64 bit with SQL 2005 SP1 Standard Edition >> > (64bit) >> > >> > Using the Iseries Access ODBC drivers I've created a system DSN called >> > MSSQL_GACUPR01 (I have both 64 and 32 bit drivers from IBM and have >> > each) >> > >> > From there i've created a Linked server using SQL Native client: >> > >> > EXEC master.dbo.sp_addlinkedserver @server = N'CTSACURITYINT', >> > @srvproduct=N'DB2', @provider=N'SQLNCLI', @datasrc=N'MSSQL_GACUPR01' >> > >> > However I get the error: >> > >> > >> > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned >> > message >> > "Login timeout expired". >> > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned >> > message >> > "An error has occurred while establishing a connection to the server. >> > When >> > connecting to SQL Server 2005, this failure may be caused by the fact >> > that >> > under the default settings SQL Server does not allow remote >> > connections.". >> > Msg 53, Level 16, State 1, Line 0 >> > Named Pipes Provider: Could not open a connection to SQL Server [53]. >> > >> > >> > Can anybody assist?
Hi,
If I try it on a 32bit SQl 2005 instance on the same 64 bit windows server using the Microsoft OLE DB provider for ODBC Drivers for the linked server, it works correctly. I'm not sure how to test the DSN connection as the ISeries ODBC driver doesn't provide this functionality. Thanks, Richard [quoted text, click to view] "Bindesh Vijayan[MSFT]" wrote:
> Did the DSN test successfully. If yes, then go ahead and create the linked > server using Management studio and check the behavior. > I guess we are missing some additional attributes in the linked server > properties(if the DSN is successful). > > > -- > Bindesh Vijayan- SQL Developer Support > [This posting is provided "AS IS" with no warranties, and confers no rights] > > "RichardT" <RichardT@discussions.microsoft.com> wrote in message > news:24E17ED6-B227-4A10-87CD-30C834FEBFDE@microsoft.com... > > The host DB2 machine can be pinged from the SQL 2005 server and name > > resolution is working corrrectly > > > > "RichardT" wrote: > > > >> With Named pipes turned off I get the error,: > >> > >> OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > >> message > >> "Login timeout expired". > >> OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > >> message > >> "An error has occurred while establishing a connection to the server. > >> When > >> connecting to SQL Server 2005, this failure may be caused by the fact > >> that > >> under the default settings SQL Server does not allow remote > >> connections.". > >> Msg 11001, Level 16, State 1, Line 0 > >> TCP Provider: No such host is known. > >> > >> > >> "RichardT" wrote: > >> > >> > I'm having problems setting up an ODBC Connection to AS400 > >> > The server is Windows 2003 R2 64 bit with SQL 2005 SP1 Standard Edition > >> > (64bit) > >> > > >> > Using the Iseries Access ODBC drivers I've created a system DSN called > >> > MSSQL_GACUPR01 (I have both 64 and 32 bit drivers from IBM and have > >> > each) > >> > > >> > From there i've created a Linked server using SQL Native client: > >> > > >> > EXEC master.dbo.sp_addlinkedserver @server = N'CTSACURITYINT', > >> > @srvproduct=N'DB2', @provider=N'SQLNCLI', @datasrc=N'MSSQL_GACUPR01' > >> > > >> > However I get the error: > >> > > >> > > >> > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > >> > message > >> > "Login timeout expired". > >> > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > >> > message > >> > "An error has occurred while establishing a connection to the server. > >> > When > >> > connecting to SQL Server 2005, this failure may be caused by the fact > >> > that > >> > under the default settings SQL Server does not allow remote > >> > connections.". > >> > Msg 53, Level 16, State 1, Line 0 > >> > Named Pipes Provider: Could not open a connection to SQL Server [53]. > >> > > >> > > >> > Can anybody assist?
Finally had success using the ISeries OLE DB provider MSDASQL
however it did take a bit of work figuring Component services permissions for the OLE DB instance. [quoted text, click to view] "RichardT" wrote:
> Hi, > > If I try it on a 32bit SQl 2005 instance on the same 64 bit windows server > using the Microsoft OLE DB provider for ODBC Drivers for the linked server, > it works correctly. > > I'm not sure how to test the DSN connection as the ISeries ODBC driver > doesn't provide this functionality. > > Thanks, Richard > > > "Bindesh Vijayan[MSFT]" wrote: > > > Did the DSN test successfully. If yes, then go ahead and create the linked > > server using Management studio and check the behavior. > > I guess we are missing some additional attributes in the linked server > > properties(if the DSN is successful). > > > > > > -- > > Bindesh Vijayan- SQL Developer Support > > [This posting is provided "AS IS" with no warranties, and confers no rights] > > > > "RichardT" <RichardT@discussions.microsoft.com> wrote in message > > news:24E17ED6-B227-4A10-87CD-30C834FEBFDE@microsoft.com... > > > The host DB2 machine can be pinged from the SQL 2005 server and name > > > resolution is working corrrectly > > > > > > "RichardT" wrote: > > > > > >> With Named pipes turned off I get the error,: > > >> > > >> OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > > >> message > > >> "Login timeout expired". > > >> OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > > >> message > > >> "An error has occurred while establishing a connection to the server. > > >> When > > >> connecting to SQL Server 2005, this failure may be caused by the fact > > >> that > > >> under the default settings SQL Server does not allow remote > > >> connections.". > > >> Msg 11001, Level 16, State 1, Line 0 > > >> TCP Provider: No such host is known. > > >> > > >> > > >> "RichardT" wrote: > > >> > > >> > I'm having problems setting up an ODBC Connection to AS400 > > >> > The server is Windows 2003 R2 64 bit with SQL 2005 SP1 Standard Edition > > >> > (64bit) > > >> > > > >> > Using the Iseries Access ODBC drivers I've created a system DSN called > > >> > MSSQL_GACUPR01 (I have both 64 and 32 bit drivers from IBM and have > > >> > each) > > >> > > > >> > From there i've created a Linked server using SQL Native client: > > >> > > > >> > EXEC master.dbo.sp_addlinkedserver @server = N'CTSACURITYINT', > > >> > @srvproduct=N'DB2', @provider=N'SQLNCLI', @datasrc=N'MSSQL_GACUPR01' > > >> > > > >> > However I get the error: > > >> > > > >> > > > >> > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > > >> > message > > >> > "Login timeout expired". > > >> > OLE DB provider "SQLNCLI" for linked server "CTSACURITYINT" returned > > >> > message > > >> > "An error has occurred while establishing a connection to the server. > > >> > When > > >> > connecting to SQL Server 2005, this failure may be caused by the fact > > >> > that > > >> > under the default settings SQL Server does not allow remote > > >> > connections.". > > >> > Msg 53, Level 16, State 1, Line 0 > > >> > Named Pipes Provider: Could not open a connection to SQL Server [53]. > > >> > > > >> > > > >> > Can anybody assist?
Richard,
I am also facing the same issue. Did u got any solution for this? EggHeadCafe.com - .NET Developer Portal of Choice
Richard,
I am also facing the same issue. Have you got any fix for this? EggHeadCafe.com - .NET Developer Portal of Choice
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |