I'm getting an error message I've never seen before when I installed my
application on a client's machine.
I've got seven machines at this location that all work fine, when I install
on a new machine, I can connect through ODBC Administrator; but, when I try
to connect through the program I get this error message:
[ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
[ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
I've looked on KB and have not been able to find anything specific on this
problem.
Any ideas?
Thanks in advance.This might be the same issue reported in the KB article at the link
http://support.microsoft.com/defaul...b;en-us;Q322144
Regards,
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Uwa Agbonile[MSFT]
"Dennis Powell" <dennis.powell@.monroe.XXXXXXXXX> wrote in message
news:OA6%23L0fYFHA.2128@.TK2MSFTNGP15.phx.gbl...
> I'm getting an error message I've never seen before when I installed my
> application on a client's machine.
> I've got seven machines at this location that all work fine, when I
install
> on a new machine, I can connect through ODBC Administrator; but, when I
try
> to connect through the program I get this error message:
> [ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
> [ODBC SQL Server Driver][TCP/IP
> Sockets]ConnectionOpen(SECDoClientHandsh
ake()).
> I've looked on KB and have not been able to find anything specific on
this
> problem.
> Any ideas?
> Thanks in advance.
>
Showing posts with label machine. Show all posts
Showing posts with label machine. Show all posts
Friday, March 30, 2012
ODBC DSN SQL Port settings
Hello
I need to create two DSN's on one machine, both pointing to different
SQL Databases (but housed on the same remote server). One runs on the
standard 1433 port and the other on port 1075.
I have both of these setup, but I cannot use a different port in both.
If I set it to 1433 in DSN 1, DSN 2 automatically uses that port. If I
set DSN 2 to 1075, DSN 1 reverts to 1075. Is there any way to use
different ports using the same SQL ODBC driver?
LeonOK, it looks like I've fixed this.
It appears to revert to the same port number if the Server Name in the
DSN is the same. A quick look through the registry confirmed this.
I'm now using a hostname for one of them and the server IP address for
the other. Not the ideal solution, but it works|||Leon...I read your post with interest. I've got a similar situation on the
server side that you do. I need to have two databases running on the same
server with different IP ports (a vendor has an app with a hard-coded IP
port). Up to now I thought I had to add a seperate instance on the server
for it to listen to two different ports.
I know your original email was talking about the DSN settings, but how did
you configure the server side to be listening to two ports?
Thanks for any information.
Bob
"leonvd@.gmail.com" wrote:
> OK, it looks like I've fixed this.
> It appears to revert to the same port number if the Server Name in the
> DSN is the same. A quick look through the registry confirmed this.
> I'm now using a hostname for one of them and the server IP address for
> the other. Not the ideal solution, but it works
>|||To listen on multiple ports, use the Server Network Utility
and enter the port numbers, separated by commas in the
TCP/IP properties. You need to restart the service for the
settings to take effect.
-Sue
On Wed, 23 Aug 2006 07:39:01 -0700, RL Coppedge
<RLCoppedge@.hotmail.com.(nospam)> wrote:
[vbcol=seagreen]
>Leon...I read your post with interest. I've got a similar situation on the
>server side that you do. I need to have two databases running on the same
>server with different IP ports (a vendor has an app with a hard-coded IP
>port). Up to now I thought I had to add a seperate instance on the server
>for it to listen to two different ports.
>I know your original email was talking about the DSN settings, but how did
>you configure the server side to be listening to two ports?
>Thanks for any information.
>Bob
>
>"leonvd@.gmail.com" wrote:
>|||Cool! Thanks for the fast reply!
Bob
"Sue Hoegemeier" wrote:
> To listen on multiple ports, use the Server Network Utility
> and enter the port numbers, separated by commas in the
> TCP/IP properties. You need to restart the service for the
> settings to take effect.
> -Sue
> On Wed, 23 Aug 2006 07:39:01 -0700, RL Coppedge
> <RLCoppedge@.hotmail.com.(nospam)> wrote:
>
>
I need to create two DSN's on one machine, both pointing to different
SQL Databases (but housed on the same remote server). One runs on the
standard 1433 port and the other on port 1075.
I have both of these setup, but I cannot use a different port in both.
If I set it to 1433 in DSN 1, DSN 2 automatically uses that port. If I
set DSN 2 to 1075, DSN 1 reverts to 1075. Is there any way to use
different ports using the same SQL ODBC driver?
LeonOK, it looks like I've fixed this.
It appears to revert to the same port number if the Server Name in the
DSN is the same. A quick look through the registry confirmed this.
I'm now using a hostname for one of them and the server IP address for
the other. Not the ideal solution, but it works|||Leon...I read your post with interest. I've got a similar situation on the
server side that you do. I need to have two databases running on the same
server with different IP ports (a vendor has an app with a hard-coded IP
port). Up to now I thought I had to add a seperate instance on the server
for it to listen to two different ports.
I know your original email was talking about the DSN settings, but how did
you configure the server side to be listening to two ports?
Thanks for any information.
Bob
"leonvd@.gmail.com" wrote:
> OK, it looks like I've fixed this.
> It appears to revert to the same port number if the Server Name in the
> DSN is the same. A quick look through the registry confirmed this.
> I'm now using a hostname for one of them and the server IP address for
> the other. Not the ideal solution, but it works
>|||To listen on multiple ports, use the Server Network Utility
and enter the port numbers, separated by commas in the
TCP/IP properties. You need to restart the service for the
settings to take effect.
-Sue
On Wed, 23 Aug 2006 07:39:01 -0700, RL Coppedge
<RLCoppedge@.hotmail.com.(nospam)> wrote:
[vbcol=seagreen]
>Leon...I read your post with interest. I've got a similar situation on the
>server side that you do. I need to have two databases running on the same
>server with different IP ports (a vendor has an app with a hard-coded IP
>port). Up to now I thought I had to add a seperate instance on the server
>for it to listen to two different ports.
>I know your original email was talking about the DSN settings, but how did
>you configure the server side to be listening to two ports?
>Thanks for any information.
>Bob
>
>"leonvd@.gmail.com" wrote:
>|||Cool! Thanks for the fast reply!
Bob
"Sue Hoegemeier" wrote:
> To listen on multiple ports, use the Server Network Utility
> and enter the port numbers, separated by commas in the
> TCP/IP properties. You need to restart the service for the
> settings to take effect.
> -Sue
> On Wed, 23 Aug 2006 07:39:01 -0700, RL Coppedge
> <RLCoppedge@.hotmail.com.(nospam)> wrote:
>
>
Wednesday, March 28, 2012
ODBC Driver Error - Timeout Expired
Very common error but wired scenario. Every client machine get this error in morning. VB application works fine until evening but when everyone goes home after shut down the machine and they come back again in morning and try to run the application they get this error. Application runs fine, It can access data, pull data, view data but It can not write any data. (Other words can not enter any data).
Application again starts working fine after I copy database on different SQL server. For temporary solution I swap database from one SQL Server to other one day and back to original SQL server next day. Every morning it takes about 2 hours to copy database. Im doing this from last few days as working solution. FYI, I have 2 different VB application, each has their own database. One working fine and other started giving me problem, the one I described above.
Few thing I want to let you know:
Recently I changed the SQL server. After I changed I started having this problem. But other application working fine. So I dont think that could be a problem. (Both application basically same in terms of development and tools they use. VB and SQL Server, ODBC connection, Crystal Reports).
In old SQL server both database had daily backup on third party backup built on different server using Client Network Backup. After I changed the SQL server I never modify backup setting. So after I moved SQL server , every night backup was trying to connect to old SQL server and but It couldnt take the backup cause I changed the machine. Again if thats the problem both application should not work but one working fine other is giving me problem.
One more thing I want to mention here is I started having this problem when I left the SQL server copying database overnight. Means, I started copying database and I left the machine ON when I came in the morning copying database was done and I just click on the OK and close the window. Basically It has finished copying database in around 2 hours after I started and I close the window when I came back next morning.
Thats the few things Im thinking about but I dont know what kind of database setting this might have changed and how to reset again. Any help will appreciated.
Dose any one know how to combine .mdf (Primary data file) and .ndf (secondary data file) ?To answer your direct question, use DBCC SHRINKFILE (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_dbcc_8b51.asp) to empty the NDF file, then use ALTER DATABASE (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_aa-az_4e5h.asp) to deactivate the NDF file. At that point, you can then simply delete the NDF file because it is no longer part of your database.
As a separate issue, I'd suspect that the third party backup is somehow causing your problem with users being unable to write data. I'm not sure how it is interfering. There are many third party backup solutions, with varying degrees of compatibility with SQL Server. Almost all of them work under their ideal conditions, almost all of them break down under other conditions.
Just as a point of curiousity, does the problem persist if you reboot NT on the machine that runs SQL Server? IF there is some problem with file locking, etc. that should clear up the problem for you a lot more quickly and simply than having to copy the database to another server. It would also give you some valuable information for trying to locate the real source of your problem.
-PatP|||Thanks for .ndf tip.
No, It wouldnt clear the problem if restart the NT machine. Just today I tried another solution, I dont know if its going to work but what I did is create the new database and import the data from the original database which already solved my .ndf file problem, now I have only one data file. I dont know if its going to work. I will find out tomorrow morning.
I also noticed one thing today someone created (there is couple of people have access to server) one more filegroup which is Primary_1. There was not any file in that group so I tried to delete that group but It would not delete It just kept freezing.
One question, If I created the new database with same name and import data using SQL server Import function where I choose Import all Objects. Is it going to have any problem in terms of data. I mean tables and views are all imported. It just changed 2 data file to one data file and also got rid of that Primary_1 file group. Just wondering if its going to make any difference in data. I mean I'm going to loose some data or anything like that. Application functions fine.
Thanks.sql
Application again starts working fine after I copy database on different SQL server. For temporary solution I swap database from one SQL Server to other one day and back to original SQL server next day. Every morning it takes about 2 hours to copy database. Im doing this from last few days as working solution. FYI, I have 2 different VB application, each has their own database. One working fine and other started giving me problem, the one I described above.
Few thing I want to let you know:
Recently I changed the SQL server. After I changed I started having this problem. But other application working fine. So I dont think that could be a problem. (Both application basically same in terms of development and tools they use. VB and SQL Server, ODBC connection, Crystal Reports).
In old SQL server both database had daily backup on third party backup built on different server using Client Network Backup. After I changed the SQL server I never modify backup setting. So after I moved SQL server , every night backup was trying to connect to old SQL server and but It couldnt take the backup cause I changed the machine. Again if thats the problem both application should not work but one working fine other is giving me problem.
One more thing I want to mention here is I started having this problem when I left the SQL server copying database overnight. Means, I started copying database and I left the machine ON when I came in the morning copying database was done and I just click on the OK and close the window. Basically It has finished copying database in around 2 hours after I started and I close the window when I came back next morning.
Thats the few things Im thinking about but I dont know what kind of database setting this might have changed and how to reset again. Any help will appreciated.
Dose any one know how to combine .mdf (Primary data file) and .ndf (secondary data file) ?To answer your direct question, use DBCC SHRINKFILE (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_dbcc_8b51.asp) to empty the NDF file, then use ALTER DATABASE (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_aa-az_4e5h.asp) to deactivate the NDF file. At that point, you can then simply delete the NDF file because it is no longer part of your database.
As a separate issue, I'd suspect that the third party backup is somehow causing your problem with users being unable to write data. I'm not sure how it is interfering. There are many third party backup solutions, with varying degrees of compatibility with SQL Server. Almost all of them work under their ideal conditions, almost all of them break down under other conditions.
Just as a point of curiousity, does the problem persist if you reboot NT on the machine that runs SQL Server? IF there is some problem with file locking, etc. that should clear up the problem for you a lot more quickly and simply than having to copy the database to another server. It would also give you some valuable information for trying to locate the real source of your problem.
-PatP|||Thanks for .ndf tip.
No, It wouldnt clear the problem if restart the NT machine. Just today I tried another solution, I dont know if its going to work but what I did is create the new database and import the data from the original database which already solved my .ndf file problem, now I have only one data file. I dont know if its going to work. I will find out tomorrow morning.
I also noticed one thing today someone created (there is couple of people have access to server) one more filegroup which is Primary_1. There was not any file in that group so I tried to delete that group but It would not delete It just kept freezing.
One question, If I created the new database with same name and import data using SQL server Import function where I choose Import all Objects. Is it going to have any problem in terms of data. I mean tables and views are all imported. It just changed 2 data file to one data file and also got rid of that Primary_1 file group. Just wondering if its going to make any difference in data. I mean I'm going to loose some data or anything like that. Application functions fine.
Thanks.sql
Monday, March 26, 2012
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
looking for the
it from my
analyzer (QA).
open up the
DSN, the 2k3
the end was
hard time
creating a DSN
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:
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
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:|||I can't get my app server (MacroMedia CF server 5.0 running on RH 9) to
>connection I can use to the SQL server.
>Thanks.
>.
>
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:sql
> So what's the issue?
> Linchi
>
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
>
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
>
Friday, March 23, 2012
ODBC connection to a seperate machine
I'm curious, can you set up a ODBC connection on one server, that points
to another computer on the network where the database is? I've tried
the computer name as //server2, but it doesn't seem to find it, yet, I
can get to it via the RDC within WinXP Pro.
Thanks,
Steve"Steve Grosz" <boise_bound@.hotmail.com> wrote in message
news:eZknx$7UEHA.2520@.TK2MSFTNGP10.phx.gbl...
> I'm curious, can you set up a ODBC connection on one server, that points
> to another computer on the network where the database is? I've tried
> the computer name as //server2, but it doesn't seem to find it, yet, I
> can get to it via the RDC within WinXP Pro.
I do not believe that is allowed as which security credentials would be used
from the ODBC connection from server1 to server2? There are work-arounds,
for example you could use a linked server from SQL Server (say on server1)
and access the database on server2 from server1.
Stevesql
to another computer on the network where the database is? I've tried
the computer name as //server2, but it doesn't seem to find it, yet, I
can get to it via the RDC within WinXP Pro.
Thanks,
Steve"Steve Grosz" <boise_bound@.hotmail.com> wrote in message
news:eZknx$7UEHA.2520@.TK2MSFTNGP10.phx.gbl...
> I'm curious, can you set up a ODBC connection on one server, that points
> to another computer on the network where the database is? I've tried
> the computer name as //server2, but it doesn't seem to find it, yet, I
> can get to it via the RDC within WinXP Pro.
I do not believe that is allowed as which security credentials would be used
from the ODBC connection from server1 to server2? There are work-arounds,
for example you could use a linked server from SQL Server (say on server1)
and access the database on server2 from server1.
Stevesql
ODBC connection to a seperate machine
I'm curious, can you set up a ODBC connection on one server, that points
to another computer on the network where the database is? I've tried
the computer name as //server2, but it doesn't seem to find it, yet, I
can get to it via the RDC within WinXP Pro.
Thanks,
Steve
"Steve Grosz" <boise_bound@.hotmail.com> wrote in message
news:eZknx$7UEHA.2520@.TK2MSFTNGP10.phx.gbl...
> I'm curious, can you set up a ODBC connection on one server, that points
> to another computer on the network where the database is? I've tried
> the computer name as //server2, but it doesn't seem to find it, yet, I
> can get to it via the RDC within WinXP Pro.
I do not believe that is allowed as which security credentials would be used
from the ODBC connection from server1 to server2? There are work-arounds,
for example you could use a linked server from SQL Server (say on server1)
and access the database on server2 from server1.
Steve
to another computer on the network where the database is? I've tried
the computer name as //server2, but it doesn't seem to find it, yet, I
can get to it via the RDC within WinXP Pro.
Thanks,
Steve
"Steve Grosz" <boise_bound@.hotmail.com> wrote in message
news:eZknx$7UEHA.2520@.TK2MSFTNGP10.phx.gbl...
> I'm curious, can you set up a ODBC connection on one server, that points
> to another computer on the network where the database is? I've tried
> the computer name as //server2, but it doesn't seem to find it, yet, I
> can get to it via the RDC within WinXP Pro.
I do not believe that is allowed as which security credentials would be used
from the ODBC connection from server1 to server2? There are work-arounds,
for example you could use a linked server from SQL Server (say on server1)
and access the database on server2 from server1.
Steve
Wednesday, March 21, 2012
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
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
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
sqlODBC 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
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
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
Monday, March 19, 2012
ODBC Components not loading
I am running SQL Express on a Server 2003 R2 machine. The application that uses the database needs to have the ODBC drivers installed. Everytime I try to add them, the installer looks like it does something, but when I go to the Data Source option under Administrative Tools, the only driver I see is the SQL Native Client. Any ideas?1) What ODBC driver are you expecting to install?
2) When you mentioned "Data Source", you meant that the drivers did not show up under the "drivers" tab of "ODBC Data Source Administrator", correct?|||
2) When you mentioned "Data Source", you meant that the drivers did not show up under the "drivers" tab of "ODBC Data Source Administrator", correct?|||
The SQL Native client is the ODBC driver for SQL Server. You just need to add a new DSN to connect to the right server and then use the DSN to connect. If that is not what you intend on doing, please describe exactly what you trying to do.
The following links talks more about it in detail.
http://blogs.msdn.com/sqlnativeclient/archive/2006/09/27/774287.aspx
HTH
Riyaz
ODBC call failed - weird behavior
Hello,
I have been working on updating an Access 2000 application that uses linked
ODBC tables to connect to an SQL Server 2000. My development machine is
connected to the server over a Microsoft LAN, at 100Mbits.
Both the Office 2000 on my development machine and the SQL server has all
the latest SP's
Everything worked fine for months until today. I am not aware of any changes
to ether machine since yesterday.
Now, there is one table that can not be opened any more.
I can access all the other tables ecxept that one. When I try to open it I
get the message "ODBC call failed". The table is displayed but with #Name?
in all columns for all records.
Once that has happened I get the same message for all tables. In addition to
"ODBC call failed" there is also
"[Microsoft][ODBC SQL Server Driver][Communication link failure
(#0)".
When I close down and reopen the app I can again access all tables except
the bad one.
At first, I thought the table had gotten corrupted, but I can open the table
just fine on the server. If I set up an ODBC on the server with the same
name I and run my application there. the problem table opens fine.
I removed the ODBC and set it up again with the same properties, client uses
TCP/IP network library, and I am using SQL Server authentication.
I am using MDAC 2.6 SP2, and I did a refresh, but it did not solve problem.
I ran
I am wondering if I should update to 2.8
If anyone has a suggestion I would appreciate it very much.
RagnarIt could be an MDAC issue. You could run the MDAC component
checker on a machine where the app works and another machine
where the app gets the ODBC error and see if there are any
differences in MDAC versions. You can get component checker
from:
http://msdn.microsoft.com/data/down...ls/default.aspx
You could also turn on ODBC tracing then reproduce your
error and then turn tracing off again. You could open up the
ODBC trace log, look for specifics of what's failing and try
to track down the issue from there.
-Sue
On Wed, 10 Mar 2004 19:05:29 -0500, "Ragnar Midtskogen"
<ragnar_ng@.optonline.net> wrote:
>Hello,
>I have been working on updating an Access 2000 application that uses linked
>ODBC tables to connect to an SQL Server 2000. My development machine is
>connected to the server over a Microsoft LAN, at 100Mbits.
>Both the Office 2000 on my development machine and the SQL server has all
>the latest SP's
>Everything worked fine for months until today. I am not aware of any change
s
>to ether machine since yesterday.
>Now, there is one table that can not be opened any more.
>I can access all the other tables ecxept that one. When I try to open it I
>get the message "ODBC call failed". The table is displayed but with #Name?
>in all columns for all records.
>Once that has happened I get the same message for all tables. In addition t
o
>"ODBC call failed" there is also
>"[Microsoft][ODBC SQL Server Driver][Communication link failure
(#0)".
>When I close down and reopen the app I can again access all tables except
>the bad one.
>At first, I thought the table had gotten corrupted, but I can open the tabl
e
>just fine on the server. If I set up an ODBC on the server with the same
>name I and run my application there. the problem table opens fine.
>I removed the ODBC and set it up again with the same properties, client use
s
>TCP/IP network library, and I am using SQL Server authentication.
>I am using MDAC 2.6 SP2, and I did a refresh, but it did not solve problem.
>I ran
>I am wondering if I should update to 2.8
>If anyone has a suggestion I would appreciate it very much.
>Ragnar
>|||Thank you Sue,
I had run ComponentChecker on my development machine and it now has 2.6 SP2
Refresh wih a couple of files being slightly newer than expected, ODBC32.dll
and ODBCCP32.dll.
The Server had 2.7 SP1 Refresh with about 8 files slightly newer than
expected, including the ODBC32.dll and ODBCCP32.dll.
I thought I had run a trace, but I did not realize I had to switch it on. I
ran a trace and found these error lines toward the end. This trace was only
running while I opened the problem table in the DB window.
MQ_CLEAN 878-58c EXIT SQLExecute with return code -1 (SQL_ERROR)
HSTMT 09022400
DIAG [01000] [Microsoft][ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionRead (recv()). (10054)
DIAG [08S01] [Microsoft][ODBC SQL Server Driver][TCP/IP Sock
ets]General
network error. Check your network documentation. (11)
I am not familiar with ODBC calls, but I see there were two error messages
I have done some more testing and found that I can open a form that displays
the contents of this table in a listbox with no errors. The RowSource for
the listbox is a select query that selects all fields of the table.
Yet, if I create a stand alone query that does the same, it fails.
I am beginning to suspect network problems, possibly the NIC on the server.
We had problems with that before and it was replaced. The connection into
the main network from my machine also goes through a switch, which could be
acting up.
I still think I am going to update MDAC to the same as the server, or do you
think 2.8 would be better?
Ragnar|||You'd definitely want to be on 2.7 SP1 at least due to all
of the bug fixes for it since 2.6 SP2. I'd try to go that
route first being that it works on your server.
2.8 has a lot of security changes and it should be tested in
another environment if possible before installing. It's the
base mdac version for Windows 2003 but I don't think
anything other products, service packs, etc are installing
it at this point.
The list box testing you did is odd, otherwise I'd suspect
network issues as well (or wouldn't rule them out anyway).
Were both of the connections, data source properties for the
list box and the stand alone query exactly the same?
-Sue
On Thu, 11 Mar 2004 13:13:12 -0500, "Ragnar Midtskogen"
<ragnar_ng@.optonline.net> wrote:
>Thank you Sue,
>I had run ComponentChecker on my development machine and it now has 2.6 SP2
>Refresh wih a couple of files being slightly newer than expected, ODBC32.dl
l
>and ODBCCP32.dll.
>The Server had 2.7 SP1 Refresh with about 8 files slightly newer than
>expected, including the ODBC32.dll and ODBCCP32.dll.
>I thought I had run a trace, but I did not realize I had to switch it on. I
>ran a trace and found these error lines toward the end. This trace was only
>running while I opened the problem table in the DB window.
>MQ_CLEAN 878-58c EXIT SQLExecute with return code -1 (SQL_ERROR)
> HSTMT 09022400
> DIAG [01000] [Microsoft][ODBC SQL Server Driver][TCP/IP
>Sockets]ConnectionRead (recv()). (10054)
> DIAG [08S01] [Microsoft][ODBC SQL Server Driver][TCP/IP S
ockets]General
>network error. Check your network documentation. (11)
>I am not familiar with ODBC calls, but I see there were two error messages
>I have done some more testing and found that I can open a form that display
s
>the contents of this table in a listbox with no errors. The RowSource for
>the listbox is a select query that selects all fields of the table.
>Yet, if I create a stand alone query that does the same, it fails.
>I am beginning to suspect network problems, possibly the NIC on the server.
>We had problems with that before and it was replaced. The connection into
>the main network from my machine also goes through a switch, which could be
>acting up.
>I still think I am going to update MDAC to the same as the server, or do yo
u
>think 2.8 would be better?
>Ragnar
>|||Thank you Sue,
> You'd definitely want to be on 2.7 SP1 at least due to all
> of the bug fixes for it since 2.6 SP2. I'd try to go that
> route first being that it works on your server.
That is what I did. Unfortunately the problem is still there.
> The list box testing you did is odd, otherwise I'd suspect
> network issues as well (or wouldn't rule them out anyway).
> Were both of the connections, data source properties for the
> list box and the stand alone query exactly the same?
They both use the same linked table.
I suspect the network connection now, I tried running my app on another
machine on the network and the problem disappeared.
Ragnar|||Hi, I had a similar issue with an Oracle database connection. I got around
it by removing the linked tables, compacting/repairing the Access database a
nd recreating the links. I suspect that Access is maintaining some informat
ion about the back-end tables that is not visible and is corrupt. If so, th
is information is removed by the repair if the link is gone. Anyway, hopefu
lly this will also work for you.
... Bob
I have been working on updating an Access 2000 application that uses linked
ODBC tables to connect to an SQL Server 2000. My development machine is
connected to the server over a Microsoft LAN, at 100Mbits.
Both the Office 2000 on my development machine and the SQL server has all
the latest SP's
Everything worked fine for months until today. I am not aware of any changes
to ether machine since yesterday.
Now, there is one table that can not be opened any more.
I can access all the other tables ecxept that one. When I try to open it I
get the message "ODBC call failed". The table is displayed but with #Name?
in all columns for all records.
Once that has happened I get the same message for all tables. In addition to
"ODBC call failed" there is also
"[Microsoft][ODBC SQL Server Driver][Communication link failure
(#0)".
When I close down and reopen the app I can again access all tables except
the bad one.
At first, I thought the table had gotten corrupted, but I can open the table
just fine on the server. If I set up an ODBC on the server with the same
name I and run my application there. the problem table opens fine.
I removed the ODBC and set it up again with the same properties, client uses
TCP/IP network library, and I am using SQL Server authentication.
I am using MDAC 2.6 SP2, and I did a refresh, but it did not solve problem.
I ran
I am wondering if I should update to 2.8
If anyone has a suggestion I would appreciate it very much.
RagnarIt could be an MDAC issue. You could run the MDAC component
checker on a machine where the app works and another machine
where the app gets the ODBC error and see if there are any
differences in MDAC versions. You can get component checker
from:
http://msdn.microsoft.com/data/down...ls/default.aspx
You could also turn on ODBC tracing then reproduce your
error and then turn tracing off again. You could open up the
ODBC trace log, look for specifics of what's failing and try
to track down the issue from there.
-Sue
On Wed, 10 Mar 2004 19:05:29 -0500, "Ragnar Midtskogen"
<ragnar_ng@.optonline.net> wrote:
>Hello,
>I have been working on updating an Access 2000 application that uses linked
>ODBC tables to connect to an SQL Server 2000. My development machine is
>connected to the server over a Microsoft LAN, at 100Mbits.
>Both the Office 2000 on my development machine and the SQL server has all
>the latest SP's
>Everything worked fine for months until today. I am not aware of any change
s
>to ether machine since yesterday.
>Now, there is one table that can not be opened any more.
>I can access all the other tables ecxept that one. When I try to open it I
>get the message "ODBC call failed". The table is displayed but with #Name?
>in all columns for all records.
>Once that has happened I get the same message for all tables. In addition t
o
>"ODBC call failed" there is also
>"[Microsoft][ODBC SQL Server Driver][Communication link failure
(#0)".
>When I close down and reopen the app I can again access all tables except
>the bad one.
>At first, I thought the table had gotten corrupted, but I can open the tabl
e
>just fine on the server. If I set up an ODBC on the server with the same
>name I and run my application there. the problem table opens fine.
>I removed the ODBC and set it up again with the same properties, client use
s
>TCP/IP network library, and I am using SQL Server authentication.
>I am using MDAC 2.6 SP2, and I did a refresh, but it did not solve problem.
>I ran
>I am wondering if I should update to 2.8
>If anyone has a suggestion I would appreciate it very much.
>Ragnar
>|||Thank you Sue,
I had run ComponentChecker on my development machine and it now has 2.6 SP2
Refresh wih a couple of files being slightly newer than expected, ODBC32.dll
and ODBCCP32.dll.
The Server had 2.7 SP1 Refresh with about 8 files slightly newer than
expected, including the ODBC32.dll and ODBCCP32.dll.
I thought I had run a trace, but I did not realize I had to switch it on. I
ran a trace and found these error lines toward the end. This trace was only
running while I opened the problem table in the DB window.
MQ_CLEAN 878-58c EXIT SQLExecute with return code -1 (SQL_ERROR)
HSTMT 09022400
DIAG [01000] [Microsoft][ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionRead (recv()). (10054)
DIAG [08S01] [Microsoft][ODBC SQL Server Driver][TCP/IP Sock
ets]General
network error. Check your network documentation. (11)
I am not familiar with ODBC calls, but I see there were two error messages
I have done some more testing and found that I can open a form that displays
the contents of this table in a listbox with no errors. The RowSource for
the listbox is a select query that selects all fields of the table.
Yet, if I create a stand alone query that does the same, it fails.
I am beginning to suspect network problems, possibly the NIC on the server.
We had problems with that before and it was replaced. The connection into
the main network from my machine also goes through a switch, which could be
acting up.
I still think I am going to update MDAC to the same as the server, or do you
think 2.8 would be better?
Ragnar|||You'd definitely want to be on 2.7 SP1 at least due to all
of the bug fixes for it since 2.6 SP2. I'd try to go that
route first being that it works on your server.
2.8 has a lot of security changes and it should be tested in
another environment if possible before installing. It's the
base mdac version for Windows 2003 but I don't think
anything other products, service packs, etc are installing
it at this point.
The list box testing you did is odd, otherwise I'd suspect
network issues as well (or wouldn't rule them out anyway).
Were both of the connections, data source properties for the
list box and the stand alone query exactly the same?
-Sue
On Thu, 11 Mar 2004 13:13:12 -0500, "Ragnar Midtskogen"
<ragnar_ng@.optonline.net> wrote:
>Thank you Sue,
>I had run ComponentChecker on my development machine and it now has 2.6 SP2
>Refresh wih a couple of files being slightly newer than expected, ODBC32.dl
l
>and ODBCCP32.dll.
>The Server had 2.7 SP1 Refresh with about 8 files slightly newer than
>expected, including the ODBC32.dll and ODBCCP32.dll.
>I thought I had run a trace, but I did not realize I had to switch it on. I
>ran a trace and found these error lines toward the end. This trace was only
>running while I opened the problem table in the DB window.
>MQ_CLEAN 878-58c EXIT SQLExecute with return code -1 (SQL_ERROR)
> HSTMT 09022400
> DIAG [01000] [Microsoft][ODBC SQL Server Driver][TCP/IP
>Sockets]ConnectionRead (recv()). (10054)
> DIAG [08S01] [Microsoft][ODBC SQL Server Driver][TCP/IP S
ockets]General
>network error. Check your network documentation. (11)
>I am not familiar with ODBC calls, but I see there were two error messages
>I have done some more testing and found that I can open a form that display
s
>the contents of this table in a listbox with no errors. The RowSource for
>the listbox is a select query that selects all fields of the table.
>Yet, if I create a stand alone query that does the same, it fails.
>I am beginning to suspect network problems, possibly the NIC on the server.
>We had problems with that before and it was replaced. The connection into
>the main network from my machine also goes through a switch, which could be
>acting up.
>I still think I am going to update MDAC to the same as the server, or do yo
u
>think 2.8 would be better?
>Ragnar
>|||Thank you Sue,
> You'd definitely want to be on 2.7 SP1 at least due to all
> of the bug fixes for it since 2.6 SP2. I'd try to go that
> route first being that it works on your server.
That is what I did. Unfortunately the problem is still there.
> The list box testing you did is odd, otherwise I'd suspect
> network issues as well (or wouldn't rule them out anyway).
> Were both of the connections, data source properties for the
> list box and the stand alone query exactly the same?
They both use the same linked table.
I suspect the network connection now, I tried running my app on another
machine on the network and the problem disappeared.
Ragnar|||Hi, I had a similar issue with an Oracle database connection. I got around
it by removing the linked tables, compacting/repairing the Access database a
nd recreating the links. I suspect that Access is maintaining some informat
ion about the back-end tables that is not visible and is corrupt. If so, th
is information is removed by the repair if the link is gone. Anyway, hopefu
lly this will also work for you.
... Bob
quote:
Originally posted by Ragnar Midtskogen
Thank you Sue,
> You'd definitely want to be on 2.7 SP1 at least due to all
> of the bug fixes for it since 2.6 SP2. I'd try to go that
> route first being that it works on your server.
That is what I did. Unfortunately the problem is still there.
> The list box testing you did is odd, otherwise I'd suspect
> network issues as well (or wouldn't rule them out anyway).
> Were both of the connections, data source properties for the
> list box and the stand alone query exactly the same?
They both use the same linked table.
I suspect the network connection now, I tried running my app on another
machine on the network and the problem disappeared.
Ragnar
ODBC and Windows 98
We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
connect to the W98 DB from a XP machine using an ODBC and a Windows
authentication. We get the following error when trying to test-connect the
DB:
SQL Server error 18452 : Login failed. Not associated with trusted SQL
server.
The machines are on the same workgroup, and we made the Windows logins and
passwords the same as the SQL logins and password. What is the issue, and
can it be solved?
Thanks,
Matt
I forgot to mention that the ODBC is in mixed mode.
Matt
"Matt" <mrocha@.camicro.com> wrote in message
news:uC8%23XqNKFHA.1540@.TK2MSFTNGP14.phx.gbl...
> We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
> connect to the W98 DB from a XP machine using an ODBC and a Windows
> authentication. We get the following error when trying to test-connect
the
> DB:
> SQL Server error 18452 : Login failed. Not associated with trusted SQL
> server.
> The machines are on the same workgroup, and we made the Windows logins and
> passwords the same as the SQL logins and password. What is the issue, and
> can it be solved?
> Thanks,
> Matt
>
connect to the W98 DB from a XP machine using an ODBC and a Windows
authentication. We get the following error when trying to test-connect the
DB:
SQL Server error 18452 : Login failed. Not associated with trusted SQL
server.
The machines are on the same workgroup, and we made the Windows logins and
passwords the same as the SQL logins and password. What is the issue, and
can it be solved?
Thanks,
Matt
I forgot to mention that the ODBC is in mixed mode.
Matt
"Matt" <mrocha@.camicro.com> wrote in message
news:uC8%23XqNKFHA.1540@.TK2MSFTNGP14.phx.gbl...
> We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
> connect to the W98 DB from a XP machine using an ODBC and a Windows
> authentication. We get the following error when trying to test-connect
the
> DB:
> SQL Server error 18452 : Login failed. Not associated with trusted SQL
> server.
> The machines are on the same workgroup, and we made the Windows logins and
> passwords the same as the SQL logins and password. What is the issue, and
> can it be solved?
> Thanks,
> Matt
>
ODBC and Windows 98
We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
connect to the W98 DB from a XP machine using an ODBC and a Windows
authentication. We get the following error when trying to test-connect the
DB:
SQL Server error 18452 : Login failed. Not associated with trusted SQL
server.
The machines are on the same workgroup, and we made the Windows logins and
passwords the same as the SQL logins and password. What is the issue, and
can it be solved?
Thanks,
MattI forgot to mention that the ODBC is in mixed mode.
Matt
"Matt" <mrocha@.camicro.com> wrote in message
news:uC8%23XqNKFHA.1540@.TK2MSFTNGP14.phx.gbl...
> We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
> connect to the W98 DB from a XP machine using an ODBC and a Windows
> authentication. We get the following error when trying to test-connect
the
> DB:
> SQL Server error 18452 : Login failed. Not associated with trusted SQL
> server.
> The machines are on the same workgroup, and we made the Windows logins and
> passwords the same as the SQL logins and password. What is the issue, and
> can it be solved?
> Thanks,
> Matt
>
connect to the W98 DB from a XP machine using an ODBC and a Windows
authentication. We get the following error when trying to test-connect the
DB:
SQL Server error 18452 : Login failed. Not associated with trusted SQL
server.
The machines are on the same workgroup, and we made the Windows logins and
passwords the same as the SQL logins and password. What is the issue, and
can it be solved?
Thanks,
MattI forgot to mention that the ODBC is in mixed mode.
Matt
"Matt" <mrocha@.camicro.com> wrote in message
news:uC8%23XqNKFHA.1540@.TK2MSFTNGP14.phx.gbl...
> We set up a MSDE 2000 database on a Windows 98 machine. We're trying to
> connect to the W98 DB from a XP machine using an ODBC and a Windows
> authentication. We get the following error when trying to test-connect
the
> DB:
> SQL Server error 18452 : Login failed. Not associated with trusted SQL
> server.
> The machines are on the same workgroup, and we made the Windows logins and
> passwords the same as the SQL logins and password. What is the issue, and
> can it be solved?
> Thanks,
> Matt
>
Monday, March 12, 2012
Odbc access
I have a DB and some tables that I'm moving to Sql2005 machine that just get
query access. People use ACCESS with ODBC link table.
What permissions other than datareader would allow them to only see USER
tables?
Thanks.
db_datareader is enough.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> I have a DB and some tables that I'm moving to Sql2005 machine that just get
> query access. People use ACCESS with ODBC link table.
> What permissions other than datareader would allow them to only see USER
> tables?
>
> Thanks.
>
>
|||That's what I gave but when linking the tables the user saw lot of sys
tables also.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...[vbcol=seagreen]
> db_datareader is enough.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
|||Do not worry about those tables, they are SQL Server catalog views.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> That's what I gave but when linking the tables the user saw lot of sys
> tables also.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
>
|||Thanks..
Just didn't want to clutter there view of valid tables...
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:410C1840-0476-4606-8BC9-70D2345EC6E2@.microsoft.com...[vbcol=seagreen]
> Do not worry about those tables, they are SQL Server catalog views.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
query access. People use ACCESS with ODBC link table.
What permissions other than datareader would allow them to only see USER
tables?
Thanks.
db_datareader is enough.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> I have a DB and some tables that I'm moving to Sql2005 machine that just get
> query access. People use ACCESS with ODBC link table.
> What permissions other than datareader would allow them to only see USER
> tables?
>
> Thanks.
>
>
|||That's what I gave but when linking the tables the user saw lot of sys
tables also.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...[vbcol=seagreen]
> db_datareader is enough.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
|||Do not worry about those tables, they are SQL Server catalog views.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> That's what I gave but when linking the tables the user saw lot of sys
> tables also.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
>
|||Thanks..
Just didn't want to clutter there view of valid tables...
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:410C1840-0476-4606-8BC9-70D2345EC6E2@.microsoft.com...[vbcol=seagreen]
> Do not worry about those tables, they are SQL Server catalog views.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
Odbc access
I have a DB and some tables that I'm moving to Sql2005 machine that just get
query access. People use ACCESS with ODBC link table.
What permissions other than datareader would allow them to only see USER
tables?
Thanks.db_datareader is enough.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> I have a DB and some tables that I'm moving to Sql2005 machine that just get
> query access. People use ACCESS with ODBC link table.
> What permissions other than datareader would allow them to only see USER
> tables?
>
> Thanks.
>
>|||That's what I gave but when linking the tables the user saw lot of sys
tables also.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
> db_datareader is enough.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>> I have a DB and some tables that I'm moving to Sql2005 machine that just
>> get
>> query access. People use ACCESS with ODBC link table.
>> What permissions other than datareader would allow them to only see USER
>> tables?
>>
>> Thanks.
>>|||Do not worry about those tables, they are SQL Server catalog views.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> That's what I gave but when linking the tables the user saw lot of sys
> tables also.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
> >
> > db_datareader is enough.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> >
> >
> > "AHartman" wrote:
> >
> >> I have a DB and some tables that I'm moving to Sql2005 machine that just
> >> get
> >> query access. People use ACCESS with ODBC link table.
> >> What permissions other than datareader would allow them to only see USER
> >> tables?
> >>
> >>
> >> Thanks.
> >>
> >>
> >>
>|||Thanks..
Just didn't want to clutter there view of valid tables...
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:410C1840-0476-4606-8BC9-70D2345EC6E2@.microsoft.com...
> Do not worry about those tables, they are SQL Server catalog views.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>> That's what I gave but when linking the tables the user saw lot of sys
>> tables also.
>>
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
>> >
>> > db_datareader is enough.
>> >
>> > Hope this helps,
>> >
>> > Ben Nevarez
>> > Senior Database Administrator
>> > AIG SunAmerica
>> >
>> >
>> >
>> > "AHartman" wrote:
>> >
>> >> I have a DB and some tables that I'm moving to Sql2005 machine that
>> >> just
>> >> get
>> >> query access. People use ACCESS with ODBC link table.
>> >> What permissions other than datareader would allow them to only see
>> >> USER
>> >> tables?
>> >>
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>>
query access. People use ACCESS with ODBC link table.
What permissions other than datareader would allow them to only see USER
tables?
Thanks.db_datareader is enough.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> I have a DB and some tables that I'm moving to Sql2005 machine that just get
> query access. People use ACCESS with ODBC link table.
> What permissions other than datareader would allow them to only see USER
> tables?
>
> Thanks.
>
>|||That's what I gave but when linking the tables the user saw lot of sys
tables also.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
> db_datareader is enough.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>> I have a DB and some tables that I'm moving to Sql2005 machine that just
>> get
>> query access. People use ACCESS with ODBC link table.
>> What permissions other than datareader would allow them to only see USER
>> tables?
>>
>> Thanks.
>>|||Do not worry about those tables, they are SQL Server catalog views.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> That's what I gave but when linking the tables the user saw lot of sys
> tables also.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
> >
> > db_datareader is enough.
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> >
> >
> > "AHartman" wrote:
> >
> >> I have a DB and some tables that I'm moving to Sql2005 machine that just
> >> get
> >> query access. People use ACCESS with ODBC link table.
> >> What permissions other than datareader would allow them to only see USER
> >> tables?
> >>
> >>
> >> Thanks.
> >>
> >>
> >>
>|||Thanks..
Just didn't want to clutter there view of valid tables...
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:410C1840-0476-4606-8BC9-70D2345EC6E2@.microsoft.com...
> Do not worry about those tables, they are SQL Server catalog views.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>> That's what I gave but when linking the tables the user saw lot of sys
>> tables also.
>>
>> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
>> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
>> >
>> > db_datareader is enough.
>> >
>> > Hope this helps,
>> >
>> > Ben Nevarez
>> > Senior Database Administrator
>> > AIG SunAmerica
>> >
>> >
>> >
>> > "AHartman" wrote:
>> >
>> >> I have a DB and some tables that I'm moving to Sql2005 machine that
>> >> just
>> >> get
>> >> query access. People use ACCESS with ODBC link table.
>> >> What permissions other than datareader would allow them to only see
>> >> USER
>> >> tables?
>> >>
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>>
Odbc access
I have a DB and some tables that I'm moving to Sql2005 machine that just get
query access. People use ACCESS with ODBC link table.
What permissions other than datareader would allow them to only see USER
tables?
Thanks.db_datareader is enough.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> I have a DB and some tables that I'm moving to Sql2005 machine that just g
et
> query access. People use ACCESS with ODBC link table.
> What permissions other than datareader would allow them to only see USER
> tables?
>
> Thanks.
>
>|||That's what I gave but when linking the tables the user saw lot of sys
tables also.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...[vbcol=seagreen]
> db_datareader is enough.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>|||Do not worry about those tables, they are SQL Server catalog views.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> That's what I gave but when linking the tables the user saw lot of sys
> tables also.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
>|||Thanks..
Just didn't want to clutter there view of valid tables...
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:410C1840-0476-4606-8BC9-70D2345EC6E2@.microsoft.com...[vbcol=seagreen]
> Do not worry about those tables, they are SQL Server catalog views.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>
query access. People use ACCESS with ODBC link table.
What permissions other than datareader would allow them to only see USER
tables?
Thanks.db_datareader is enough.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> I have a DB and some tables that I'm moving to Sql2005 machine that just g
et
> query access. People use ACCESS with ODBC link table.
> What permissions other than datareader would allow them to only see USER
> tables?
>
> Thanks.
>
>|||That's what I gave but when linking the tables the user saw lot of sys
tables also.
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...[vbcol=seagreen]
> db_datareader is enough.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>|||Do not worry about those tables, they are SQL Server catalog views.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"AHartman" wrote:
> That's what I gave but when linking the tables the user saw lot of sys
> tables also.
>
> "Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
> news:9602F1EB-8E2D-4B02-85FE-25FC2689E670@.microsoft.com...
>|||Thanks..
Just didn't want to clutter there view of valid tables...
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:410C1840-0476-4606-8BC9-70D2345EC6E2@.microsoft.com...[vbcol=seagreen]
> Do not worry about those tables, they are SQL Server catalog views.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "AHartman" wrote:
>
Subscribe to:
Posts (Atom)