|
|
You're in the
sql server odbc
group:SQL Server does not exist or Access Denied
sql server odbc:
I am very new to SQL server. I have successfully installed it on a =
server. But when I try to setup an ODBC connection from my client = machine I get the "SQL Server does not exist or Access Denied. " There are two computers on the LAN connecting through a hub. Its probably something basic that I am missing.=20 Thanks
Ping the sql server to make sure that it can be seen on
the network. If necessary try using the sql server ip address instead of the server name in your ODBC parameters. Also make sure the user account that you're using for the ODBC connection exist on the sql db with the appropriate access rights. [quoted text, click to view] >-----Original Message----- installed it on a server. But when I try to setup an ODBC >I am very new to SQL server. I have successfully connection from my client machine I get the "SQL Server does not exist or Access Denied. " [quoted text, click to view] >
>There are two computers on the LAN connecting through a hub. > >Its probably something basic that I am missing. > >Thanks >Lance >
Hello,
I have a similar problem: I try to connect from a Windows 2000 Workstation to MS SQL Server 2000 via ODBC, but I can't. :-( When I try to create a Server DSN connection to the server, I get the following error message (I have to translate some words to english, so it may read a little different for others): Error on connection: SQL State: '01000' SQL Server Error 10061 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()) Error on connection: SQL State: '08001' SQL Server Error 17 [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied - I can ping the SQL Server by name and IP address - I have tried the name and the IP address in the ODBC driver - I am using SQL Server authentication and sa as user - I have tried to install different MDACs: - first I had the MDAC 2.6 (which seems to come with W2k sp4) - I downloaded and installed the newest update of MDAC 2.6 - I then installed MDAC 2.7 (SQL Server ODBC Version 2000.81.9001.00) (Connecting to MS SQL Server 7 on another server poses no problem) Has anyone a suggestion what I still can do? Thanks for listening. Regards,
Hello,
I have found an embarrasingly simple solution for my problem: installating the newest Service Pack (sp3a) for SQL Server 2000 helped - I can now access the server via ODBC, if I also install the newest MDAC version on the client computer. I still don't understand the error codes, but now it works! Regards, Garrit [quoted text, click to view] truco@gmx.de (Garrit Fleischmann) wrote in message news:<c089de1a.0401190603.4290d389@posting.google.com>...
> Hello, > > I have a similar problem: > I try to connect from a Windows 2000 Workstation to > MS SQL Server 2000 via ODBC, but I can't. :-( > > > > When I try to create a Server DSN connection to > the server, I get the following error message > (I have to translate some words to english, so it > may read a little different for others): > > Error on connection: > SQL State: '01000' > SQL Server Error 10061 > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()) > Error on connection: > SQL State: '08001' > SQL Server Error 17 > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist > or access denied > > - I can ping the SQL Server by name and IP address > - I have tried the name and the IP address in the ODBC driver > - I am using SQL Server authentication and sa as user > - I have tried to install different MDACs: > - first I had the MDAC 2.6 (which seems to come with W2k sp4) > - I downloaded and installed the newest update of MDAC 2.6 > - I then installed MDAC 2.7 (SQL Server ODBC Version 2000.81.9001.00) > > (Connecting to MS SQL Server 7 on another server poses no problem) > > Has anyone a suggestion what I still can do? > Thanks for listening. > > Regards,
I'm having the same problem with a client using MSDE on a 2000 server with service pack 4 trying to connect from a 2000 workstation.
[quoted text, click to view] =?Utf-8?B?SkI=?= wrote: > *I'm having the same problem with a client using MSDE on a 2000 > server with service pack 4 trying to connect from a 2000 > workstation. > > Did you apply service pack 3a to the server or a SQL Server service > pack. * I'm having a similar problem. First some facts: -i've got a Windows 2000 Domain -with 2 DC's , both W2K Srv SP4 -one of them with SQL2000 Std/SP3a. -There are about 20 Clients in the Domain, all W2K Pro SP4. -There are (much) more than enough CAL's, SQL- as well as ServerCal's. I can see in the License Administration, that there is a sufficiant count of unused licenses. -The existing workstations run well, but need to be replaced because they're weak. I've set up a sample/"image"-system to be copied by TrueImage. The machine is set up equal, is in the same domain, has the same software installed, is in the same Network/ Segment, gets a valid DHCP-Lease and so on. Nameresolution / DNS Works, but in ODBC, neither Servername nor IPAdress in work. It cannot be a matter of missing rights because i'm setting this up with domain administrators right, and use the "sa" for the odbc-connection. And as i've written, it works on the old machines with exactly the same accounts, but not on the new ones. Garrits Solution doesn't work for me as this sqlserver already runs on SP3a. thanks for all Hints -- Deubi ------------------------------------------------------------------------ Posted via http://www.webservertalk.com ------------------------------------------------------------------------ View this thread: http://www.webservertalk.com/message92511.html
Does anyone have a resolution to this problem? I have the exact same problem and errors on ODBC. It was working before but not now..... Error on connection: [quoted text, click to view] > SQL State: '01000' > SQL Server Error 10061 > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()) > Error on connection: > SQL State: '08001' > SQL Server Error 17 > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist > or access denied Cheers Graeme -- gromits ------------------------------------------------------------------------ Posted via http://www.webservertalk.com ------------------------------------------------------------------------ View this thread: http://www.webservertalk.com/message92511.html
[quoted text, click to view] gromits wrote: > *Does anyone have a resolution to this problem? > I have the exact same problem and errors on ODBC. It was working > before but not now..... > > Error on connection: > > SQL State: '01000' > > SQL Server Error 10061 > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen > (Connect()) > > Error on connection: > > SQL State: '08001' > > SQL Server Error 17 > > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does > not exist > > or access denied > > > Cheers > Graeme * we've "solved" it like this: we're working with a special application that connects to an SQL-Server through ODBX. We had a couple of workstations running fine, which were to replace by faster ones. Now, i've prepared the faster ones with applications, prepared "defaultuser"-Profile and so on. Teking those new clients to the domain lead to the mentioned problem. Setting the systems up new, put them into the domain and doing all ODBC-Stuff then when i got them in the domain worked. Now it seems that our particular application (Papyrus capture, a very special OCR-Application) messed up something still undisclosed when installing it on a local machine and putting it to the domain afterwards. Doing it the other way, first taking it into the domain and installing this application afterwards works fine. The reason is unclear as we've used SQL-authentification (which is not my favour anyway, but this was demanded from this software's produceer) and that should be independent from Domain-credentials. Kind regards Robert -- Deubi ------------------------------------------------------------------------ Posted via http://www.webservertalk.com ------------------------------------------------------------------------ View this thread: http://www.webservertalk.com/message92511.html
Ok well I am still confussed about this. I have 2 PCs that were working fine on the ODBC but now they don't connect. Nothing has changed as far as I know. We are using MS SQL Server 2000 with OnBase scanning software. SQL authentication is being used. Could this be a CAL issue at all?? is it the registry edit problem? (TcpTimedWaitDelay & MaxUserPort) Is there anything I can do that is not too drastic? There are still 5 other clients working fine, set up in the same way, who I don't want to disturb. thanks -- gromits ------------------------------------------------------------------------ Posted via http://www.webservertalk.com ------------------------------------------------------------------------ View this thread: http://www.webservertalk.com/message92511.html
[quoted text, click to view] gromits wrote: > *Ok well I am still confussed about this. I have 2 PCs that were > working fine on the ODBC but now they don't connect. Nothing has > changed as far as I know. > We are using MS SQL Server 2000 with OnBase scanning software. > SQL authentication is being used. Could this be a CAL issue at all?? > is it the registry edit problem? (TcpTimedWaitDelay & MaxUserPort) > Is there anything I can do that is not too drastic? There are still 5 > other clients working fine, set up in the same way, who I don't want > to disturb. > > thanks * You wrote "5 other clients are still working fine", while 2 don't. How many CAL's do you have? -- Deubi ------------------------------------------------------------------------ Posted via http://www.webservertalk.com ------------------------------------------------------------------------ View this thread: http://www.webservertalk.com/message92511.html
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |