Objects related to DB: running

Showing posts with label running. Show all posts

Friday, March 30, 2012

ODBC drivers needed

My server is running with 2003R2 x64 with SQL 2005. Some of my client
computers are having some issues with ODBC errors while working in an
accounting package. I have been told that it is most likely a driver
compatibility issue between the XP pro versions on the clients and the 64
bit version on my server.
I suppose first does this seem plausible, and where might I find the updated
drivers for XP? I am not sure if this is the correct forum for this request,
but it seemed to be the closest.
Many thanks in advance.
David
David (David@.Fidia.com) writes:
> My server is running with 2003R2 x64 with SQL 2005. Some of my client
> computers are having some issues with ODBC errors while working in an
> accounting package. I have been told that it is most likely a driver
> compatibility issue between the XP pro versions on the clients and the 64
> bit version on my server.
> I suppose first does this seem plausible, and where might I find the
> updated drivers for XP? I am not sure if this is the correct forum for
> this request, but it seemed to be the closest.
http://www.microsoft.com/downloads/details.aspx?FamilyID=78cac895-efc2-4f8e-a9e0-3a1afbd5922e&DisplayLang=en
and
[url]http://www.microsoft.com/downloads/info.aspx?na=22&p=4&SrcDisplayLang=en&SrcCategoryI d=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFa milyID%3d7358da31-959c-4e3e-8115-51dc6d441365%26DisplayLang%3den[/url]
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

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
>
>

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
>
>

Monday, March 26, 2012

ODBC database slows down over time

Howdy,

I currently have an ODBC connection to a SQL server that exists on the other side of the country from me. I'm running queries in Access and I've found that over time, queries run slower and slower. If I create a new database and bring in the same tables, it runs quickly (relatively speaking) again. Why is this happening? Is there something I can do besides creating new databases all the time?

Thank you in advance.Is the problem that over time the query has more and more records to move through? Is the DB normalized?

ODBC data source + SQL 2000

quote:

>--Original Message--
>Hello,
>I'm running a SQL 2000 server on a win 2k3 machine.
>I'm not familiar with Win 2k3 so I'm having a hard time

looking for the

quote:

>correct information.
>I know my SQL server is up and running. I can connect to

it from my

quote:

>workstation through Enterprise Manager (EM) and the query

analyzer (QA).

quote:

>The funny thing is , when I login to the 2k3 machine and

open up the

quote:

>ODBC Data Source Administrator and try to create a system

DSN, the 2k3

quote:

>machine is not listed in the drop down menu.
>It reads,
>Which SQL Server do you wan tot connect to?
>Server: <Dropdown menu>
>I did just type the servername, winbox, and the test at

the end was

quote:

>sucessful. The reason I'm asking is because I'm having a

hard time

quote:

>getting my web app server (CF 5.0 on RH 9.0 w/Apache)

creating a DSN

quote:

>connection I can use to the SQL server.
>Thanks.
>.
>

|||I can't get my app server (MacroMedia CF server 5.0 running on RH 9) to
create an ODBC connection to SQL Server 2000 running on a 2k3 server.
I feel like I am taking crazy pills. I have done this config numerous
times with the same system architect. The only thing that is different
this time is that the SQL server is running on a 2k3 Machine.
CF server defaults the connection to 1433. I checked up the TCPIP
properties to make sure I did not close that port. It looks good.
Any ideas?
Linchi Shea wrote:

quote:

> So what's the issue?
> Linchi
>

sql

ODBC data source + SQL 2000

Hello,
I'm running a SQL 2000 server on a win 2k3 machine.
I'm not familiar with Win 2k3 so I'm having a hard time looking for the
correct information.
I know my SQL server is up and running. I can connect to it from my
workstation through Enterprise Manager (EM) and the query analyzer (QA).
The funny thing is , when I login to the 2k3 machine and open up the
ODBC Data Source Administrator and try to create a system DSN, the 2k3
machine is not listed in the drop down menu.
It reads,
Which SQL Server do you wan tot connect to?
Server: <Dropdown menu>
I did just type the servername, winbox, and the test at the end was
sucessful. The reason I'm asking is because I'm having a hard time
getting my web app server (CF 5.0 on RH 9.0 w/Apache) creating a DSN
connection I can use to the SQL server.
Thanks.So what's the issue?
Linchi
>--Original Message--
>Hello,
>I'm running a SQL 2000 server on a win 2k3 machine.
>I'm not familiar with Win 2k3 so I'm having a hard time
looking for the
>correct information.
>I know my SQL server is up and running. I can connect to
it from my
>workstation through Enterprise Manager (EM) and the query
analyzer (QA).
>The funny thing is , when I login to the 2k3 machine and
open up the
>ODBC Data Source Administrator and try to create a system
DSN, the 2k3
>machine is not listed in the drop down menu.
>It reads,
>Which SQL Server do you wan tot connect to?
>Server: <Dropdown menu>
>I did just type the servername, winbox, and the test at
the end was
>sucessful. The reason I'm asking is because I'm having a
hard time
>getting my web app server (CF 5.0 on RH 9.0 w/Apache)
creating a DSN
>connection I can use to the SQL server.
>Thanks.
>.
>|||I can't get my app server (MacroMedia CF server 5.0 running on RH 9) to
create an ODBC connection to SQL Server 2000 running on a 2k3 server.
I feel like I am taking crazy pills. I have done this config numerous
times with the same system architect. The only thing that is different
this time is that the SQL server is running on a 2k3 Machine.
CF server defaults the connection to 1433. I checked up the TCPIP
properties to make sure I did not close that port. It looks good.
Any ideas?
Linchi Shea wrote:
> So what's the issue?
> Linchi
>

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?

Friday, March 23, 2012

ODBC Connection Setup

I'm running SBS 2003 Premium SP1 and all is well. I've installed a new SQL
based application that requires a simple ODBC connection to the SQL database
.
I have about 50 PCs to setup this ODBC link to my SBS server and there must
be a faster way to do this via a script or through Group Policies.
Has anyone tried this and how? I've used GPs for simple things like folder
redirection, but I'm not that strong on it.
Thanks.
KenI've taken to using file-based DSNs placed in a server folder that everyone
can access. It's turned out to be the best solution in my case.
Randall Arnold
"shepcon" <shepcon@.discussions.microsoft.com> wrote in message
news:E02D79DC-D435-4C36-9FF8-4C541F6116D4@.microsoft.com...
> I'm running SBS 2003 Premium SP1 and all is well. I've installed a new
> SQL
> based application that requires a simple ODBC connection to the SQL
> database.
> I have about 50 PCs to setup this ODBC link to my SBS server and there
> must
> be a faster way to do this via a script or through Group Policies.
> Has anyone tried this and how? I've used GPs for simple things like
> folder
> redirection, but I'm not that strong on it.
> Thanks.
> Ken
>sql

ODBC Connection Setup

I'm running SBS 2003 Premium SP1 and all is well. I've installed a new SQL
based application that requires a simple ODBC connection to the SQL database.
I have about 50 PCs to setup this ODBC link to my SBS server and there must
be a faster way to do this via a script or through Group Policies.
Has anyone tried this and how? I've used GPs for simple things like folder
redirection, but I'm not that strong on it.
Thanks.
Ken
I've taken to using file-based DSNs placed in a server folder that everyone
can access. It's turned out to be the best solution in my case.
Randall Arnold
"shepcon" <shepcon@.discussions.microsoft.com> wrote in message
news:E02D79DC-D435-4C36-9FF8-4C541F6116D4@.microsoft.com...
> I'm running SBS 2003 Premium SP1 and all is well. I've installed a new
> SQL
> based application that requires a simple ODBC connection to the SQL
> database.
> I have about 50 PCs to setup this ODBC link to my SBS server and there
> must
> be a faster way to do this via a script or through Group Policies.
> Has anyone tried this and how? I've used GPs for simple things like
> folder
> redirection, but I'm not that strong on it.
> Thanks.
> Ken
>

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
Run cliconfg.exe. Is "force protocol encryption" checked?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Nope, not ticked.
-- Cindy Gross (MSFT) wrote: --
Run cliconfg.exe. Is "force protocol encryption" checked?
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
|||What's the EXACT error message you get and what are you doing when you get
it (secencrypt and 770 are not SQL messages)?
Are there messages in the SQL errorlog or any of the three Windows event
logs on the client or server?
Try each of the following to see if any succeed (if it's a default
instance, ignore the \InstanceName):
np:ServerName\InstanceName
tcp:ServerName\InstanceName
tcp:ServerName\InstanceName, port
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

ODBC Connection Problem

odbc connection multi domain no trust

If you have one domain of application servers running win2000 and seperate
user domains with no trust relationships accessing sql databases on the
application domain what needs to be done rights wise and is this possible
without connectivity issues. Currently these servers are standalone not in a
domain and users can currenlty access this through local logon sql rights on
the stand alone servers. Thanks.
If there is no domain trust then you will either need to use SQL
authentication or create NT accounts on the SQL Server machines that mirror
the accounts that the users logon to their client machines with. The
accounts will have to have the same name and password. Using this method
you can use NT authentication to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.

odbc connection multi domain no trust

If you have one domain of application servers running win2000 and seperate
user domains with no trust relationships accessing sql databases on the
application domain what needs to be done rights wise and is this possible
without connectivity issues. Currently these servers are standalone not in
a
domain and users can currenlty access this through local logon sql rights on
the stand alone servers. Thanks.If there is no domain trust then you will either need to use SQL
authentication or create NT accounts on the SQL Server machines that mirror
the accounts that the users logon to their client machines with. The
accounts will have to have the same name and password. Using this method
you can use NT authentication to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

Wednesday, March 21, 2012

ODBC connection fails

I'm running SQL 2000/SP3 on a W2k server. I have a database with a standard
user (dbo rights). From any of my workstations I can create an ODBC
connection using SQL authentication.
When I try to create an ODBC connection on the server itself with the same
credentials, I get an error msg "login failed, username is not associated
with a trusted server connection". Using Windows authentication with another
user that has access to the SQL server works fine.
This doesn't make sense to me. What am I overlooking here? Any help/hint
would be appreciated.
Thanks
Claus"cjobes" <cjobes@.nova-tech.org> wrote in message
news:O6t6OxyBEHA.3928@.TK2MSFTNGP11.phx.gbl...
> I'm running SQL 2000/SP3 on a W2k server. I have a database with a
standard
> user (dbo rights). From any of my workstations I can create an ODBC
> connection using SQL authentication.
> When I try to create an ODBC connection on the server itself with the same
> credentials, I get an error msg "login failed, username is not associated
> with a trusted server connection". Using Windows authentication with
another
> user that has access to the SQL server works fine.
> This doesn't make sense to me. What am I overlooking here? Any help/hint
> would be appreciated.
The user account itself needs to have access to the server running SQL
Server. One way to verify, temporarily enable (don't leave it that way ;)
the server GUEST account.
Steve|||Hello,
Define user id "sa" and set pwd for sa account on sql server and try to
login that account on odbc connection.
i hope it will working fine.
Thanks,
Warm Regards,
Ayaz Ahmed
Software Engineer & Web Developer
Creative Chaos (Pvt.) Ltd.
"Managing Your Digital Risk"
http://www.csquareonline.com
Karachi, Pakistan
Mobile +92 300 2280950
Office +92 21 455 2414
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Actually that is a not a good idea (at least as a permanent solution) as sql
security is sent over the network in clear text.
Steve
"Ayaz Ahmed" <ayaz@.csquareonline.com> wrote in message
news:e4EAqBkDEHA.2712@.TK2MSFTNGP10.phx.gbl...
> Hello,
> Define user id "sa" and set pwd for sa account on sql server and try to
> login that account on odbc connection.
> i hope it will working fine.
>
> Thanks,
> Warm Regards,
> Ayaz Ahmed
> Software Engineer & Web Developer
> Creative Chaos (Pvt.) Ltd.
> "Managing Your Digital Risk"
> http://www.csquareonline.com
> Karachi, Pakistan
> Mobile +92 300 2280950
> Office +92 21 455 2414
> *** Sent via Developersdex http://www.examnotes.net ***
> Don't just participate in USENET...get rewarded for it!

ODBC connection failing on 64 version of Windows 2003 server

I have an application that talks to a SQL backend using an ODBC DSN connection. It works fine when running on a 32bit machine but fails in the 64bit environment. The DSN is setup properly on the 64bit box and the Test Connection returns sucess. However when my application tries to use the DSN to connect to the database I recieve the following error.

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MyDSN'

and run a open-query in the SQL Management Studio to the linked server, i get error returns, - The OLE DB provider "MSDASQL" has not been registered. This error is because of SQL Native Client but when I created a LinkedServer with SQLNCLI, I get an error - OLE DB provider "SQLNCLI" for linked server "MAMSLS1" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "MAMSLS1" 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].

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

My system is Win2003 Enterprise 64bit running on Itenium and SQL 2005 server 64bit Enterprise edition. From this SQL server, I am trying to make a LinkedServer to InterBase database system. -- No problem with 32bit SQL 2005 (development) but this 64bit (production). Any insight would be appreciated.

Regards,

Sunny

|||

If you are setting up a linked server a connection is made from one SQL Server to another. If the first SQL Server is 64-bit then you need to create a 64-bit DSN. If it is 32-bit you need a 32-bit DSN.

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "The stored procedure required to complete this operation could not be found on the server. Please contact your system administrator.".

Msg 7311, Level 16, State 2, Line 3

Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03". The provider supports the interface, but returns a failure code when it is used.

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

When i install our application on the 64 bit operating systems, i am unable to connect to the 32 ODBC. Any one have idea how to call 32 bit ODBC from the 64 bit applications on the 64 bit operating systems

Please help in this.

regards

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver'MyLinkedSrv',' ','MSDASQL','MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

sql

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver'MyLinkedSrv',' ','MSDASQL','MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

ODBC connection failing on 64 version of Windows 2003 server

IM002 - Data source name not found and no default driver specified.

The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.

Any help would be appreciated.

Is your application 64-bit or 32-bit?

One possibility is that the Test Connection dialog uses 64-bit version of the driver and yoru application looks for a 32-bit version (or vice-versa).

|||Yeah, I thought of that too but both my application and MDAC are 32 bit.|||

DSN’s for 32bit and 64bit are stored separately in registry, those in HKLM/HKCR are for 64bit, 32bit DSN’s are stored in WOW registry.

You need to use the 32bit odbc admin tool (from windows\syswow64) to create 32bit DSN’s for your 32bit application.

|||thank you so muchhhhhhh|||Thank you, Thank you, Thank you, Thank you!|||

Question - after created System DSN using 32bit odbc, I created a linked server using the DSN,

sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MyDSN'

I am thinking because of the SQL management studio is 64bit, it won't use 32bit DSN.. Is there any way to run a query against to the linked server?

Regards,

Sunny

|||

did anyone succeed in this on this with a sql2005 EE x64 sp1 to sql2000sp3a ?

Or it states the is an NCLI problem

- connectiontimeout (again and again and ......)

- OLE DB provider "SQLNCLI" for linked server "MySQl2000sp3a_03" returned message "Unspecified error".

Msg 7311, Level 16, State 2, Line 3

or it says :
Msg 7403, Level 16, State 1, Line 3

The OLE DB provider "MSDASQL" has not been registered.

None of the folowing definitions work :

|||

I just discouvered this thread with a KB link that may do the trick : http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=62887&SiteID=1

kb906954 did the trick

|||

I'm having similar issues

There is no equivalent of MSDASQL within 64 bit SQL, and from what i've read SQL Native client is meant to be used.

However I can't get this to see the 64 bit IBM ISeries ODBC DSN that I've configured within the 64bit ODBC setup

Anybody else having these problems?

|||

YES !!!

And the solution is: Execute odbccad32.exe in WOW directory. That's it !

www.mcfly.dj

|||

Hi,

I'm running SQL 2005 64 bit on the windows 2003 (64 bit box)

I'm trying to create a linked server using an ODBC driver which has a corresponding DSN

Using odbccad32.exe will work if you are using a 32 bit install of SQL 2005 on Windows 2003 (64bit)

but this doesn't work with a 64 bit instance of SQL 2005 as there is no MSDASQL provider to work with.

Has anybody managed to get the SQL native client provider SQLNCLI

in 64 bit SQL 2005 connected through a DSN (32bit or 64bit)?

Thanks, Richard

|||

Richard...see the following thread.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1239339&SiteID=1

|||

hey guys,

i have C# windows application which calles ODBC 32 bit provider. it is working very well with the 32 bit operating systems. My application is compiled targetting to any operating system.

Please help in this.

regards

Friday, March 30, 2012

ODBC drivers needed

ODBC Drivers error '80004005'

ODBC Drivers error '80004005'

Monday, March 26, 2012

ODBC database slows down over time

ODBC data source + SQL 2000

ODBC data source + SQL 2000

ODBC Connectivity Issues

Friday, March 23, 2012

ODBC Connection Setup

ODBC Connection Setup

ODBC Connection Problem

ODBC Connection Problem

ODBC Connection Problem

odbc connection multi domain no trust

odbc connection multi domain no trust

Wednesday, March 21, 2012

ODBC connection fails

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

ODBC connection failing on 64 version of Windows 2003 server

Objects related to DB

Blog Archive

About Me