SQL Server 2005 Connection Issue

#1

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#2

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#3

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#4

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#5

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#6

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#7

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#8

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#9

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.

#10

What's the error message you get? Have you checked out the error logs
(Windows and SQL) to find something related to this issue?

--
Ekrem Önsoy

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

Quote:

Group,

I have a application that is distributed to a large corporation with close
to 1000 users that will be connecting to a SQL Server 2005 database. We
initiated a pilot program of the application with around 210 users as our
beta test group. The application is installed on Windows 2000/SP 4 and
Windows XP/SP 2 machines only. Of these installs, 9 users could not
connect
to SQL Server using a SQLOLEDB connection string. All of the clients have
the same version of MDAC (2.8) as it is installed by the installer if the
version is less than 2.8. Also, using the ODBC manager and creating a test
connection does connect to the databases on the failed clients.

On these 9 units, we installed SQL Native Client drivers and then the
application with the new connection string. We were able to get 2 of the 9
users connected but the others still can't connect via the application.
Again, if using the ODBC manager and creating a test connection using the
SQL Native Client drivers, we can connect with no problems when using the
identical connection string.

Does anyone have any idea of why we can connect via the ODBC manager
applet
but not with the application. I have even placed code in the installer to
test for a connection using SQL Native Client and it fails the connection
as
well. I have even un-installed and reinstalled SQL Native Client on the
clients that could not connect and that does nothing. We are pretty much
at
a stand still since we can't release the application to the remaining
users
until we figure out this problem.

Any help would be greatly appreciated.