SQL Server 2005 connection issues.

#1

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#2

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#3

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#4

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#5

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#6

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#7

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#8

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#9

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike

#10

What error do you get?
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mike Johnson" <poboy (AT) tampabay (DOT) rr.com> wrote

Quote:

I have a problem that has caused whatever hairs on my head that I had left
to disappear. I distributed an application in a pilot program to over 100
users on a corporate network using an OLEDB connection string to connect
to
a SQL Server 2005 database. Of the 100 plus installs, 10 were not able to
connect, even though all the computers involved are imaged the same. All
the
computers are IBM and they are either PC's or laptops but the same model
respectively.

After reading a bunch of KB articles on MSDN, it was decided that I use
SQL
Native Client drivers rather then ODBC. In the update process, the setup
utility installed the SQL Native Client drivers to the PC/laptops that
could
not connect using ODBC and after checking for a proper installation of the
drivers, the application still can't connect. Installing SQL Native Client
on the machines that can connect and changing the connection string to use
SQLNCLI as the Provider continues to allow them to connect. I have tested
the SQL Native Client drivers installation on the machines that can't
connect by creating a DSN using the Native Client drivers and the test
connection is successful. Any suggestions or solutions?

Thanks,
Mike