Windows 2000 sp 3, sql 7.0 sp 4. When I try to go into
odbc under Admin tools, I get the following error:
Unable to load sql server odbc driver resource dll. The
application cannot continue.
I am not seeing any error in event viewer.
ThanksThe error is generally due to either a missing .rll file -
file is sqlsrv32.rll - or a version mismatch with the
corresponding dll file (sqlsrv32.dll).
Try running the component checker tool to verify your mdac
installation. It will help in diagnosing installation
issues. You can download the tool from:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Mon, 24 May 2004 18:53:49 -0700, "Sue"
<anonymous@.discussions.microsoft.com> wrote:
>Windows 2000 sp 3, sql 7.0 sp 4. When I try to go into
>odbc under Admin tools, I get the following error:
>
>Unable to load sql server odbc driver resource dll. The
>application cannot continue.
>I am not seeing any error in event viewer.
>Thanks|||It listed Mdac 2.6 sp 2.
Sue
>--Original Message--
>The error is generally due to either a missing .rll
file -
>file is sqlsrv32.rll - or a version mismatch with the
>corresponding dll file (sqlsrv32.dll).
>Try running the component checker tool to verify your
mdac
>installation. It will help in diagnosing installation
>issues. You can download the tool from:
>http://msdn.microsoft.com/data/mdac/default.aspx
>-Sue
>On Mon, 24 May 2004 18:53:49 -0700, "Sue"
><anonymous@.discussions.microsoft.com> wrote:
>
The[vbcol=seagreen]
>.
>|||Mdac 2.8 fixed the problem.
>--Original Message--
>It listed Mdac 2.6 sp 2.
>Sue
>file -
>mdac
into[vbcol=seagreen]
>The
>.
>|||Thanks for posting back. Updating your version of MDAC is
probably easier than fixing the current installation
problems.
-Sue
On Tue, 25 May 2004 11:36:53 -0700,
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mdac 2.8 fixed the problem.
>
>into
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Friday, March 30, 2012
ODBC DSN for SQL Database
Hi,
I am trying to configure DSN for a remote SQL database using Windows authentication. When I logn with a user ID and configure the DSN, it's working fine. But when I logout and login with another user ID, DSN test is failing with the following message.
Connection Failed:
SQL state 28000
SQL Server Error 18456
Microsoft ODBC SQLServer Driver SQL Server Login failed
for user.
Can any one please let me know how can I configure DSN so that it should work irrespective of what domain account I use to logon to the server later?
Thanks in advance.
Srini.Hi Srini
It sounds like only the first windows account (User ID) has access to SQLServer?
You can also test connectivity by trying to connect using one of the command line tools. I like to try this with SQLCmd (for SQL Server 2005) or osql (for SQL Server 2000)
Try either
sqlcmd -S<your server name here> -E
or
osql -S<your server name here> -E
The -E option tells the tools to use Windows Authentication.
Regards
Steve|||
Hello Steve my name is Chris and i have the same problem with the SQL that Srini has had but when i tried to run the "osql -S <My Server> -E i get the error Cannot generate SSPI context message please help me and point me in the right direction.
Thanks
Chris....
ODBC DSN for SQL Database
Hi,
I am trying to configure DSN for a remote SQL database using Windows authentication. When I logn with a user ID and configure the DSN, it's working fine. But when I logout and login with another user ID, DSN test is failing with the following message.
Connection Failed:
SQL state 28000
SQL Server Error 18456
Microsoft ODBC SQLServer Driver SQL Server Login failed
for user.
Can any one please let me know how can I configure DSN so that it should work irrespective of what domain account I use to logon to the server later?
Thanks in advance.
Srini.Hi Srini
It sounds like only the first windows account (User ID) has access to SQLServer?
You can also test connectivity by trying to connect using one of the command line tools. I like to try this with SQLCmd (for SQL Server 2005) or osql (for SQL Server 2000)
Try either
sqlcmd -S<your server name here> -E
or
osql -S<your server name here> -E
The -E option tells the tools to use Windows Authentication.
Regards
Steve|||
Hello Steve my name is Chris and i have the same problem with the SQL that Srini has had but when i tried to run the "osql -S <My Server> -E i get the error Cannot generate SSPI context message please help me and point me in the right direction.
Thanks
Chris....
ODBC DSN for SQL Database
Hi,
I am trying to configure DSN for a remote SQL database using Windows authentication. When I logn with a user ID and configure the DSN, it's working fine. But when I logout and login with another user ID, DSN test is failing with the following message.
Connection Failed:
SQL state 28000
SQL Server Error 18456
Microsoft ODBC SQLServer Driver SQL Server Login failed
for user.
Can any one please let me know how can I configure DSN so that it should work irrespective of what domain account I use to logon to the server later?
Thanks in advance.
Srini.Hi Srini
It sounds like only the first windows account (User ID) has access to SQLServer?
You can also test connectivity by trying to connect using one of the command line tools. I like to try this with SQLCmd (for SQL Server 2005) or osql (for SQL Server 2000)
Try either
sqlcmd -S<your server name here> -E
or
osql -S<your server name here> -E
The -E option tells the tools to use Windows Authentication.
Regards
Steve|||
Hello Steve my name is Chris and i have the same problem with the SQL that Srini has had but when i tried to run the "osql -S <My Server> -E i get the error Cannot generate SSPI context message please help me and point me in the right direction.
Thanks
Chris....
ODBC Drivers error '80004005'
Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
Danny
It looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
Danny
It looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General network error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>
ODBC Drivers error '80004005'
Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network er
ror.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
DannyIt looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General netwo
rk error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>
that accessed a SQL server 2000 running on windows 2003 through DSN. Every
once in a while the webpage becomes inaccessable and gives the following
message:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB] General network er
ror.
Check your network documentation.
/direct/dbConn.asp, line 34
Line 34 of the asp file contains the line:
adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
The webpage doesn't just comeback after a few minutes but instead stays
inaccessible until the SQL Server is restarted.
The only way around this problem has been to restart the SQL server every 3
hours in order to decrease the webserver downtime.
Please help,
DannyIt looks like an upgrade to SQL Server 2000 Service Pack 4 solved the
problem.
Dannyb
"Dannyb" <dannyb@.alianza.com> wrote in message
news:uPpKjQqNGHA.740@.TK2MSFTNGP12.phx.gbl...
> Hello, I am running IIS 6.0 on a windows 2003 server. I have an asp page
> that accessed a SQL server 2000 running on windows 2003 through DSN.
> Every
> once in a while the webpage becomes inaccessable and gives the following
> message:
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] General netwo
rk error.
> Check your network documentation.
> /direct/dbConn.asp, line 34
> Line 34 of the asp file contains the line:
> adoCon.Open "dsn=DatabaseConnect;uid=login;pwd=test"
> The webpage doesn't just comeback after a few minutes but instead stays
> inaccessible until the SQL Server is restarted.
> The only way around this problem has been to restart the SQL server every
> 3
> hours in order to decrease the webserver downtime.
> Please help,
> Danny
>
>
ODBC driver for windows 2003 64bit
Hi All,
I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.
I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.
Thanks & Regards
Varian
An ODBC driver connects to a particular database backend server (Oracle, SQL Server, etc). What specific ODBC driver are you looking for?|||There is definitely a SQL Server driver for 64-bit. SQLSRV32.DLL ships with the OS, and SQLNCLI.DLL (used with SQL Server 2005) can be downloaded from the microsoft website.
I think you may be correct, though, about non-SQL Server drivers no being available on 64-bit clients.
|||I have the same problem. My company works with the windows server 2003 R2 64 bits and we can't use an Access DB in our Site because this version doesn't have the drivers for accessing Access Databases. Can someone help?
Thanks
|||Hi,
Can you help me with ODBC drivers for MS Excel and MS Access... My organisation needs the same.
Regards
Ramakrishnan M
|||Try looking at the post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1, which I believe answers your question. Here's a clip:
64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.
Pak-Ming Cheung,
MDAC Team, MSFT.
ODBC driver for windows 2003 64bit
Hi All,
I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.
I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.
Thanks & Regards
Varian
An ODBC driver connects to a particular database backend server (Oracle, SQL Server, etc). What specific ODBC driver are you looking for?|||There is definitely a SQL Server driver for 64-bit. SQLSRV32.DLL ships with the OS, and SQLNCLI.DLL (used with SQL Server 2005) can be downloaded from the microsoft website.
I think you may be correct, though, about non-SQL Server drivers no being available on 64-bit clients.
|||I have the same problem. My company works with the windows server 2003 R2 64 bits and we can't use an Access DB in our Site because this version doesn't have the drivers for accessing Access Databases. Can someone help?
Thanks
|||Hi,
Can you help me with ODBC drivers for MS Excel and MS Access... My organisation needs the same.
Regards
Ramakrishnan M
|||Try looking at the post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1, which I believe answers your question. Here's a clip:
64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.
Pak-Ming Cheung,
MDAC Team, MSFT.
Wednesday, March 28, 2012
ODBC driver for windows 2003 64bit
Hi All,
I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.
I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.
Thanks & Regards
Varian
An ODBC driver connects to a particular database backend server (Oracle, SQL Server, etc). What specific ODBC driver are you looking for?|||There is definitely a SQL Server driver for 64-bit. SQLSRV32.DLL ships with the OS, and SQLNCLI.DLL (used with SQL Server 2005) can be downloaded from the microsoft website.
I think you may be correct, though, about non-SQL Server drivers no being available on 64-bit clients.
|||I have the same problem. My company works with the windows server 2003 R2 64 bits and we can't use an Access DB in our Site because this version doesn't have the drivers for accessing Access Databases. Can someone help?
Thanks
|||Hi,
Can you help me with ODBC drivers for MS Excel and MS Access... My organisation needs the same.
Regards
Ramakrishnan M
|||Try looking at the post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1, which I believe answers your question. Here's a clip:
64-bit MSDASQL (both AMD64 and IA64) will be released in Windows Longhorn Server Beta 3 and Windows Vista SP1.
Pak-Ming Cheung,
MDAC Team, MSFT.
ODBC Driver development
Hi everybody,
I want to develop an ODBC driver to connect a normal windows application to
a middleware product.
I can't find any examples or hints with regard to ODBC driver development.
Here are the questions:
- Does anybody have experience with ODBC driver development?
- Can anybody provide me with an example of (rudimentary) ODBC driver code?
- Any hints / documentation tips / experiences?
Thanks already.
Kindest Regards,
Arthur.You may want to start by reviewing the ODBC Programmers Reference at:
http://msdn.microsoft.com/library/e...this_manual.asp
-Sue
On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Hi everybody,
>I want to develop an ODBC driver to connect a normal windows application to
>a middleware product.
>I can't find any examples or hints with regard to ODBC driver development.
>Here are the questions:
>- Does anybody have experience with ODBC driver development?
>- Can anybody provide me with an example of (rudimentary) ODBC driver code?
>- Any hints / documentation tips / experiences?
>Thanks already.
>Kindest Regards,
>Arthur.
>|||Thank you Sue.
I have been browsed through this documentation.
Gives some more insight.
I'm still interrested in sample code etc.
Cheers,
Arthur.
"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
news:k7hub09ev6ff65260iddc294f4h8k61ceq@.
4ax.com...
> You may want to start by reviewing the ODBC Programmers Reference at:
> http://msdn.microsoft.com/library/e...this_manual.asp
> -Sue
> On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
> <arthurvanrossum@.mail.com> wrote:
>
to[vbcol=seagreen]
development.[vbcol=seagreen]
code?[vbcol=seagreen]
>|||The ODBC SDK used to have samples - possibly the MDAC SDK
has some ODBC samples. The MDAC downloads and SDKs are
located at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Sat, 5 Jun 2004 17:40:23 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Thank you Sue.
>I have been browsed through this documentation.
>Gives some more insight.
>I'm still interrested in sample code etc.
>Cheers,
>Arthur.
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
> news:k7hub09ev6ff65260iddc294f4h8k61ceq@.
4ax.com...
>to
>development.
>code?
>
I want to develop an ODBC driver to connect a normal windows application to
a middleware product.
I can't find any examples or hints with regard to ODBC driver development.
Here are the questions:
- Does anybody have experience with ODBC driver development?
- Can anybody provide me with an example of (rudimentary) ODBC driver code?
- Any hints / documentation tips / experiences?
Thanks already.
Kindest Regards,
Arthur.You may want to start by reviewing the ODBC Programmers Reference at:
http://msdn.microsoft.com/library/e...this_manual.asp
-Sue
On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Hi everybody,
>I want to develop an ODBC driver to connect a normal windows application to
>a middleware product.
>I can't find any examples or hints with regard to ODBC driver development.
>Here are the questions:
>- Does anybody have experience with ODBC driver development?
>- Can anybody provide me with an example of (rudimentary) ODBC driver code?
>- Any hints / documentation tips / experiences?
>Thanks already.
>Kindest Regards,
>Arthur.
>|||Thank you Sue.
I have been browsed through this documentation.
Gives some more insight.
I'm still interrested in sample code etc.
Cheers,
Arthur.
"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
news:k7hub09ev6ff65260iddc294f4h8k61ceq@.
4ax.com...
> You may want to start by reviewing the ODBC Programmers Reference at:
> http://msdn.microsoft.com/library/e...this_manual.asp
> -Sue
> On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
> <arthurvanrossum@.mail.com> wrote:
>
to[vbcol=seagreen]
development.[vbcol=seagreen]
code?[vbcol=seagreen]
>|||The ODBC SDK used to have samples - possibly the MDAC SDK
has some ODBC samples. The MDAC downloads and SDKs are
located at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Sat, 5 Jun 2004 17:40:23 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Thank you Sue.
>I have been browsed through this documentation.
>Gives some more insight.
>I'm still interrested in sample code etc.
>Cheers,
>Arthur.
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
> news:k7hub09ev6ff65260iddc294f4h8k61ceq@.
4ax.com...
>to
>development.
>code?
>
ODBC Driver development
Hi everybody,
I want to develop an ODBC driver to connect a normal windows application to
a middleware product.
I can't find any examples or hints with regard to ODBC driver development.
Here are the questions:
- Does anybody have experience with ODBC driver development?
- Can anybody provide me with an example of (rudimentary) ODBC driver code?
- Any hints / documentation tips / experiences?
Thanks already.
Kindest Regards,
Arthur.
You may want to start by reviewing the ODBC Programmers Reference at:
http://msdn.microsoft.com/library/en...his_manual.asp
-Sue
On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Hi everybody,
>I want to develop an ODBC driver to connect a normal windows application to
>a middleware product.
>I can't find any examples or hints with regard to ODBC driver development.
>Here are the questions:
>- Does anybody have experience with ODBC driver development?
>- Can anybody provide me with an example of (rudimentary) ODBC driver code?
>- Any hints / documentation tips / experiences?
>Thanks already.
>Kindest Regards,
>Arthur.
>
|||Thank you Sue.
I have been browsed through this documentation.
Gives some more insight.
I'm still interrested in sample code etc.
Cheers,
Arthur.
"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
news:k7hub09ev6ff65260iddc294f4h8k61ceq@.4ax.com... [vbcol=seagreen]
> You may want to start by reviewing the ODBC Programmers Reference at:
> http://msdn.microsoft.com/library/en...his_manual.asp
> -Sue
> On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
> <arthurvanrossum@.mail.com> wrote:
to[vbcol=seagreen]
development.[vbcol=seagreen]
code?
>
|||The ODBC SDK used to have samples - possibly the MDAC SDK
has some ODBC samples. The MDAC downloads and SDKs are
located at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Sat, 5 Jun 2004 17:40:23 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Thank you Sue.
>I have been browsed through this documentation.
>Gives some more insight.
>I'm still interrested in sample code etc.
>Cheers,
>Arthur.
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
>news:k7hub09ev6ff65260iddc294f4h8k61ceq@.4ax.com.. .
>to
>development.
>code?
>
I want to develop an ODBC driver to connect a normal windows application to
a middleware product.
I can't find any examples or hints with regard to ODBC driver development.
Here are the questions:
- Does anybody have experience with ODBC driver development?
- Can anybody provide me with an example of (rudimentary) ODBC driver code?
- Any hints / documentation tips / experiences?
Thanks already.
Kindest Regards,
Arthur.
You may want to start by reviewing the ODBC Programmers Reference at:
http://msdn.microsoft.com/library/en...his_manual.asp
-Sue
On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Hi everybody,
>I want to develop an ODBC driver to connect a normal windows application to
>a middleware product.
>I can't find any examples or hints with regard to ODBC driver development.
>Here are the questions:
>- Does anybody have experience with ODBC driver development?
>- Can anybody provide me with an example of (rudimentary) ODBC driver code?
>- Any hints / documentation tips / experiences?
>Thanks already.
>Kindest Regards,
>Arthur.
>
|||Thank you Sue.
I have been browsed through this documentation.
Gives some more insight.
I'm still interrested in sample code etc.
Cheers,
Arthur.
"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
news:k7hub09ev6ff65260iddc294f4h8k61ceq@.4ax.com... [vbcol=seagreen]
> You may want to start by reviewing the ODBC Programmers Reference at:
> http://msdn.microsoft.com/library/en...his_manual.asp
> -Sue
> On Thu, 3 Jun 2004 15:57:00 +0200, "Arthur van Rossum"
> <arthurvanrossum@.mail.com> wrote:
to[vbcol=seagreen]
development.[vbcol=seagreen]
code?
>
|||The ODBC SDK used to have samples - possibly the MDAC SDK
has some ODBC samples. The MDAC downloads and SDKs are
located at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Sat, 5 Jun 2004 17:40:23 +0200, "Arthur van Rossum"
<arthurvanrossum@.mail.com> wrote:
>Thank you Sue.
>I have been browsed through this documentation.
>Gives some more insight.
>I'm still interrested in sample code etc.
>Cheers,
>Arthur.
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> schreef in bericht
>news:k7hub09ev6ff65260iddc294f4h8k61ceq@.4ax.com.. .
>to
>development.
>code?
>
Monday, March 26, 2012
odbc datagrida
Good Day,
I got a table with company details.I am using ODBC to conect to it.
OdbcCommand cmd = new OdbcCommand("use company", MyConnection);
The
ERROR [07002] [MySQL][ODBC 3.51 Driver][mysqld-5.0.27-community-nt]SQLBindParameter not used for all parameters
When line 3 is replaced by cmd.CommandText = "SELECT * FROM employee;"; the program works. fine.
I got a table with company details.I am using ODBC to conect to it.
I am writing a windows form application in C# 2005 express edition.The task is to search companies. my code is as below.
OdbcCommand cmd = new OdbcCommand("use company", MyConnection);
cmd.CommandText = "SELECT * FROM employee WHERE Name = ?;"; /****line 3*****/
cmd.Parameters.Add("@.Name", OdbcType.VarChar, 30);
cmd.Parameters["@.Name"].Value = textBox1.Text;
cmd.ExecuteNonQuery();
OdbcDataAdapter datadapter = new OdbcDataAdapter(cmd.CommandText, MyConnection);
DataSet dataset = new DataSet();
datadapter.Fill(dataset,"employee"); /**error line***/
dataGridView1.DataMember="employee";
dataGridView1.DataSource=dataset;
The
above code compiles cleanly but when you run it,it gives a error. the
error statemnet is as below and the line giving error is show above in
coment.
ERROR [07002] [MySQL][ODBC 3.51 Driver][mysqld-5.0.27-community-nt]SQLBindParameter not used for all parameters
When line 3 is replaced by cmd.CommandText = "SELECT * FROM employee;"; the program works. fine.
I can view all employees only.BUT not a specific employee.
the problem looks complex.If some-one can help me out,it would be much appreciated.
Thanx
Rahul SK
msn add:ar_kul@.hotmail.comDo you sure that 'Name' field is exists in this table?
odbc datagrida
Good Day,
I got a table with company details.I am using ODBC to conect to it.
OdbcCommand cmd = new OdbcCommand("use company", MyConnection);
The above code compiles cleanly but when you run it,it gives a error. the error statemnet is as below and the line giving error is show above in coment.
ERROR [07002] [MySQL][ODBC 3.51 Driver][mysqld-5.0.27-community-nt]SQLBindParameter not used for all parameters
When line 3 is replaced by cmd.CommandText = "SELECT * FROM employee;"; the program works. fine.
I got a table with company details.I am using ODBC to conect to it.
I am writing a windows form application in C# 2005 express edition.The task is to search companies. my code is as below.
OdbcCommand cmd = new OdbcCommand("use company", MyConnection);
cmd.CommandText = "SELECT * FROM employee WHERE Name = ?;"; /****line 3*****/
cmd.Parameters.Add("@.Name", OdbcType.VarChar, 30);
cmd.Parameters["@.Name"].Value = textBox1.Text;
cmd.ExecuteNonQuery();
OdbcDataAdapter datadapter = new OdbcDataAdapter(cmd.CommandText, MyConnection);
DataSet dataset = new DataSet();
datadapter.Fill(dataset,"employee"); /**error line***/
dataGridView1.DataMember="employee";
dataGridView1.DataSource=dataset;
The above code compiles cleanly but when you run it,it gives a error. the error statemnet is as below and the line giving error is show above in coment.
ERROR [07002] [MySQL][ODBC 3.51 Driver][mysqld-5.0.27-community-nt]SQLBindParameter not used for all parameters
When line 3 is replaced by cmd.CommandText = "SELECT * FROM employee;"; the program works. fine.
I can view all employees only.BUT not a specific employee.
the problem looks complex.If some-one can help me out,it would be much appreciated.
Thanx
Rahul SK
msn add:ar_kul@.hotmail.comDo you sure that 'Name' field is exists in this table?
sql
ODBC Create a new Data Souce to SQL not displaying
On a Windows XP PC, why doesn't the Create a new Data
Source to SQL Server window pop up when you select to add
a new system dsn from the ODBC data source
administrator? I have one particular PC where this won't
come up, not all XP PCs though. Anyone see this before!
Thanks.
.Did you try reinstalling MDAC? You'd want to at least check
the MDAC configuration on the PC using component checker.
You can download the latest MDAC as well as component
checker from:
http://msdn.microsoft.com/downloads/list/dataaccess.asp
-Sue
On Mon, 1 Dec 2003 08:06:15 -0800, "Nil"
<anonymous@.discussions.microsoft.com> wrote:
Source to SQL Server window pop up when you select to add
a new system dsn from the ODBC data source
administrator? I have one particular PC where this won't
come up, not all XP PCs though. Anyone see this before!
Thanks.
.Did you try reinstalling MDAC? You'd want to at least check
the MDAC configuration on the PC using component checker.
You can download the latest MDAC as well as component
checker from:
http://msdn.microsoft.com/downloads/list/dataaccess.asp
-Sue
On Mon, 1 Dec 2003 08:06:15 -0800, "Nil"
<anonymous@.discussions.microsoft.com> wrote:
quote:
>On a Windows XP PC, why doesn't the Create a new Data
>Source to SQL Server window pop up when you select to add
>a new system dsn from the ODBC data source
>administrator? I have one particular PC where this won't
>come up, not all XP PCs though. Anyone see this before!
>Thanks.
>.
>
ODBC Connectivity Issues
I have a windows 98 pc trying to connect to a sql server running on Windows Server 2003 via a frame relay. The 98 pc will connect to the domain and it is able to ping the server. However, when I try to use my MS Access program that connects to the sql server, I get this error message:
Connection Failed
SqlState: '01000'
Sql ServerError: 11001
[Microsoft][ODBC Sql Server Driver][TCP/IP Sockets] Connection Open (Connect ()).
Connection Failed
SqlState: '08001'
Sql ServerError: 6
[Microsoft][ODBC Sql Server Driver][TCP/IP Sockets] Specified Sql server not found.
I have other pcs that connect to the Sql Server fine but they are located locally in the same building as the server. I've tried connecting through named pipes but for some reason, I get the same error. I have downloaded and installed the new MDAC drivers for the 98 pc. Any suggestions?Just a couple of things to check:
1. Are all the DSN names the same on all machines (are you using linked tables into MSAccess?) Does a DSN name exist on the PC?
2. If they are linked tables into MSAccess, when you linked the table in MSAccess, did you check the "Save Password".
3. Does the user have permissions to the tables in SQL Server? Is their loginID or their domain group set up for permissions to the database?
Hope any of these helps.|||Yes, the DSN names are the same, and the user name and password are the same. There are multiple users that use the "generic" username and password and it works fine for them. I looked into the linked tables idea and this is what happened. When I link the tables in Access, it worked. However, when I exited the program and went back into it, it did not work anymore. Now when I try to link the tables again, it will not let me and the program will not work and I get that error message again. Any other ideas?
Connection Failed
SqlState: '01000'
Sql ServerError: 11001
[Microsoft][ODBC Sql Server Driver][TCP/IP Sockets] Connection Open (Connect ()).
Connection Failed
SqlState: '08001'
Sql ServerError: 6
[Microsoft][ODBC Sql Server Driver][TCP/IP Sockets] Specified Sql server not found.
I have other pcs that connect to the Sql Server fine but they are located locally in the same building as the server. I've tried connecting through named pipes but for some reason, I get the same error. I have downloaded and installed the new MDAC drivers for the 98 pc. Any suggestions?Just a couple of things to check:
1. Are all the DSN names the same on all machines (are you using linked tables into MSAccess?) Does a DSN name exist on the PC?
2. If they are linked tables into MSAccess, when you linked the table in MSAccess, did you check the "Save Password".
3. Does the user have permissions to the tables in SQL Server? Is their loginID or their domain group set up for permissions to the database?
Hope any of these helps.|||Yes, the DSN names are the same, and the user name and password are the same. There are multiple users that use the "generic" username and password and it works fine for them. I looked into the linked tables idea and this is what happened. When I link the tables in Access, it worked. However, when I exited the program and went back into it, it did not work anymore. Now when I try to link the tables again, it will not let me and the program will not work and I get that error message again. Any other ideas?
Friday, March 23, 2012
ODBC connection using NT authentication
I want to create an ODBC connection with windows NT authentication on two servers the domain are different and their operating
systems r also different.
(one is Windows 2K other is NT).
how can i have to go about if i have to do this.sorry i forgot to mention the version
im using SQL SERVER 7|||This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.
Regards,
hmscott|||My $0.02 ...
I think you could do a 'pass-through' if you cant get the domains to trust eachother. Create a user on the sql server and create the same user with the same password on the other server and you should be able to connect via windows authentication. Is it a good practice? I would say No. But a work aroud if you can't have the domains trust each other.
Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.
Regards,
hmscott|||Hi,
Thanks for ur reply. My client is not beliveing tht we need trust relationship, can u please provide any link
or url where it is mentioned.
Waiting for ur reply
TIA
Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.
Regards,
hmscott|||It is very unlikely that you will get two servers in different domains (NT&W2k) working without setting up a trust between the two domains. Windows authentication uses a SID (security identifier) each computer and each user has a unique SID and the authentication should use the SID not the username. It is true to say that NT4 could be fooled depending on what service pack you used, but W2k with Active Directory will require a trust.
I recently upgraded a whole network of users from NT4 to W2k with AD in a different domain. I researched this and it will only work with a trust relationship as HMScott says. In our original plan we were going to use replication and migrate the users one by one, in the end we moved every9one ov
The way we get around such problems is to use a Role, we have one SQL username in the Role and have our application use that username. Granting ODBC connections may be quick and easy but it leaves you a bit exposed to other issues of Security & Support.
Imagine if this was not the case, any old hacker could access you databases.sql
systems r also different.
(one is Windows 2K other is NT).
how can i have to go about if i have to do this.sorry i forgot to mention the version
im using SQL SERVER 7|||This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.
Regards,
hmscott|||My $0.02 ...
I think you could do a 'pass-through' if you cant get the domains to trust eachother. Create a user on the sql server and create the same user with the same password on the other server and you should be able to connect via windows authentication. Is it a good practice? I would say No. But a work aroud if you can't have the domains trust each other.
Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.
Regards,
hmscott|||Hi,
Thanks for ur reply. My client is not beliveing tht we need trust relationship, can u please provide any link
or url where it is mentioned.
Waiting for ur reply
TIA
Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.
Regards,
hmscott|||It is very unlikely that you will get two servers in different domains (NT&W2k) working without setting up a trust between the two domains. Windows authentication uses a SID (security identifier) each computer and each user has a unique SID and the authentication should use the SID not the username. It is true to say that NT4 could be fooled depending on what service pack you used, but W2k with Active Directory will require a trust.
I recently upgraded a whole network of users from NT4 to W2k with AD in a different domain. I researched this and it will only work with a trust relationship as HMScott says. In our original plan we were going to use replication and migrate the users one by one, in the end we moved every9one ov
The way we get around such problems is to use a Role, we have one SQL username in the Role and have our application use that username. Granting ODBC connections may be quick and easy but it leaves you a bit exposed to other issues of Security & Support.
Imagine if this was not the case, any old hacker could access you databases.sql
ODBC Connection using Alternate windows credentials
Hi,
We have a server in a workgroup that users in our active directory
will need to access.
How can we configure an odbc connection to use a different username
and password (windows not sql) than the one they are currently logged
on on as. (The application we are using only supports windows
authentication not sql)
example : I am logged onto my workstaion a 'Jane', but i Need to use
user id 'janey' to connect to the odbc, and i dont want to have to
log
on to the workstation as janey
Hi
Unless you are logged on as the user you wish to authenticate as I don't
think you can do this!
John
"zach" <neopotent@.gmail.com> wrote in message
news:5e0669bb-e86f-4610-8713-5bd06084daa1@.a23g2000hsc.googlegroups.com...
> Hi,
> We have a server in a workgroup that users in our active directory
> will need to access.
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to
> log
> on to the workstation as janey
>
We have a server in a workgroup that users in our active directory
will need to access.
How can we configure an odbc connection to use a different username
and password (windows not sql) than the one they are currently logged
on on as. (The application we are using only supports windows
authentication not sql)
example : I am logged onto my workstaion a 'Jane', but i Need to use
user id 'janey' to connect to the odbc, and i dont want to have to
log
on to the workstation as janey
Hi
Unless you are logged on as the user you wish to authenticate as I don't
think you can do this!
John
"zach" <neopotent@.gmail.com> wrote in message
news:5e0669bb-e86f-4610-8713-5bd06084daa1@.a23g2000hsc.googlegroups.com...
> Hi,
> We have a server in a workgroup that users in our active directory
> will need to access.
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to
> log
> on to the workstation as janey
>
ODBC Connection using Alternate windows credentials
Hi,
We have a server in a workgroup that users in our active directory
will need to access.
How can we configure an odbc connection to use a different username
and password (windows not sql) than the one they are currently logged
on on as. (The application we are using only supports windows
authentication not sql)
example : I am logged onto my workstaion a 'Jane', but i Need to use
user id 'janey' to connect to the odbc, and i dont want to have to
log
on to the workstation as janeyHi
Unless you are logged on as the user you wish to authenticate as I don't
think you can do this!
John
"zach" <neopotent@.gmail.com> wrote in message
news:5e0669bb-e86f-4610-8713-5bd06084daa1@.a23g2000hsc.googlegroups.com...
> Hi,
> We have a server in a workgroup that users in our active directory
> will need to access.
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to
> log
> on to the workstation as janey
>
We have a server in a workgroup that users in our active directory
will need to access.
How can we configure an odbc connection to use a different username
and password (windows not sql) than the one they are currently logged
on on as. (The application we are using only supports windows
authentication not sql)
example : I am logged onto my workstaion a 'Jane', but i Need to use
user id 'janey' to connect to the odbc, and i dont want to have to
log
on to the workstation as janeyHi
Unless you are logged on as the user you wish to authenticate as I don't
think you can do this!
John
"zach" <neopotent@.gmail.com> wrote in message
news:5e0669bb-e86f-4610-8713-5bd06084daa1@.a23g2000hsc.googlegroups.com...
> Hi,
> We have a server in a workgroup that users in our active directory
> will need to access.
>
> How can we configure an odbc connection to use a different username
> and password (windows not sql) than the one they are currently logged
> on on as. (The application we are using only supports windows
> authentication not sql)
>
> example : I am logged onto my workstaion a 'Jane', but i Need to use
> user id 'janey' to connect to the odbc, and i dont want to have to
> log
> on to the workstation as janey
>
ODBC Connection Problem
Hello,
I have a user who is attempting to connect to SQL Server Enterprise 2000 SP3a running on Windows 2000 Server. The client has WIndows NT 4.0 with MDAC 2.8. The problem is that when I attempt to create the ODBC link , I receive the following error:
"connection failed
sqlstate '01000'
sql server error 770
Microsoft odbc sqlserver driver tcp/ip socket connection write
secencrypt data
Connection failed
sql state '08S01'
Sql server error 18 security error
SSL/Encryption is not forced on the Server and I have many other clients who have no issues in connecting.
If anyone has any suggestions, I would appreciate it.
Thanks
Brent
I am having the exact same problem. If you ever solve it please let me know.
I have a user who is attempting to connect to SQL Server Enterprise 2000 SP3a running on Windows 2000 Server. The client has WIndows NT 4.0 with MDAC 2.8. The problem is that when I attempt to create the ODBC link , I receive the following error:
"connection failed
sqlstate '01000'
sql server error 770
Microsoft odbc sqlserver driver tcp/ip socket connection write
secencrypt data
Connection failed
sql state '08S01'
Sql server error 18 security error
SSL/Encryption is not forced on the Server and I have many other clients who have no issues in connecting.
If anyone has any suggestions, I would appreciate it.
Thanks
Brent
I am having the exact same problem. If you ever solve it please let me know.
ODBC Connection Problem
Hello,
I have an install of SQL that my users cannot connect to with an ODBC
connection. I have created Windows User logins on the SQL server through
Enterprise Manager, and have assigned them access to one specific database.
The specific user accounts have public, db_datareader and db_datawriter
permissions to the database. When the users attemtpt to create their ODBC
connections they receive an access denied message. What other permissions do
I need to give these users? Do they need any other permissions to the actual
server the SQL instance resides on?
Thanks,
JBaileyJBailey,
Please let me know the following:
- These accounts that you created to access that datbase, can they connect
and query the database from query analyser?
- Also, could you please created a UDL to test for connectivity (this gives
us a good idea if the odbc connection is ok). Also it could be that we
arent passing the correct 'connection string'?
Create a text file and name it <anything>.UDL. Rt-click the UDL file and
select Properties. The Connection tab contains all the fields exposed to
the application, and you choose the appropriate items to be filled in to
successfully "Test Connection" before you are able to use it. Once the Test
button works, click on OK and open up the UDL file in Notepad. Its just a
text file, and contains a provider string that you should be able to paste
into your application or whichever application is calling the sql server.
Cheers!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
I have an install of SQL that my users cannot connect to with an ODBC
connection. I have created Windows User logins on the SQL server through
Enterprise Manager, and have assigned them access to one specific database.
The specific user accounts have public, db_datareader and db_datawriter
permissions to the database. When the users attemtpt to create their ODBC
connections they receive an access denied message. What other permissions do
I need to give these users? Do they need any other permissions to the actual
server the SQL instance resides on?
Thanks,
JBaileyJBailey,
Please let me know the following:
- These accounts that you created to access that datbase, can they connect
and query the database from query analyser?
- Also, could you please created a UDL to test for connectivity (this gives
us a good idea if the odbc connection is ok). Also it could be that we
arent passing the correct 'connection string'?
Create a text file and name it <anything>.UDL. Rt-click the UDL file and
select Properties. The Connection tab contains all the fields exposed to
the application, and you choose the appropriate items to be filled in to
successfully "Test Connection" before you are able to use it. Once the Test
button works, click on OK and open up the UDL file in Notepad. Its just a
text file, and contains a provider string that you should be able to paste
into your application or whichever application is calling the sql server.
Cheers!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.sql
Subscribe to:
Posts (Atom)