April 29, 2012 at 11:41 pm
Hi every one
Please i need your help i have win server 2008 64- bit and install the SQl server 2008 but when i want to add the ODBC the message appeare :
Sql state :"01000"
Sql server error:"11001"
[Microsoft] [ODBC Sql server driver] TCP/IP [sockets]
connection open (connect())
connection failed
sql state :"08001"
sql server error:"6
[Microsoft] [ODBC Sql server driver] TCP/IP [sockets]
sql server not found
this mean what error on the TCP /IP or Error on the SQL
and this is the one time that i work in win server 2008 and SQL 2008
so please hlep me
Regards to every one
Amanee
April 30, 2012 at 12:13 am
The following link might help you:
SQL Server May Not Listen on TCP/IP Sockets When TCP/IP is the Only Protocol
April 30, 2012 at 12:36 am
Dear Vinu,
First I want to thank you becouse you help me, but i still need help you
when i run the step
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ [Instance Name]\MSSQLServer\SuperSocketNetLib\Tcp\REG_SZ TcpPort=
I foun the Directoty:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ [Instance Name]\Sql\MSSQLSERVER\MSSQL10.MSSQLSERVER
only this what mean there is error in the setup of the Sql server 2008 or what ?
please If you know tell me.
with my best regards,
amanee
April 30, 2012 at 2:35 am
Can you pls provide the exact steps you followed to create the ODBC?
Online Trainer For SQL DBA and Developer @RedBushTechnologies with 18 yrs exp.
April 30, 2012 at 2:43 am
al_yamama_1980 (4/30/2012)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\ [Instance Name]\MSSQLServer\SuperSocketNetLib\Tcp\REG_SZ TcpPort=
This means that there is no registry entry for the default port that SQL Server is listening to. You can edit it as mentioned in the link I gave you.
Did you try editing it??...Did it work??....This doesn't mean that there is error in the setup of the Sql server 2008.
It just means that the default TCP/IP port was not mentioned. Editing the port in the Registry should solve your problem.
April 30, 2012 at 2:52 am
Yes i do the step and add the directory but the seem problem ?
April 30, 2012 at 2:56 am
April 30, 2012 at 3:02 am
Of curse i will tall you all the step
control panel\odbc\sysytem dsn\add\Sql serverame=Local Server , srver :Local\ with sql usre name = admin pwd= ??\ and when i chose next
the error appers.
this is what i do my friend.
regrds
amanee
April 30, 2012 at 3:06 am
yes I tay to do all step that you told me the seem error and i coonect the odbc like this:
control panel\odbc\sysytem dsn\add\Sql serverame=Local Server , srver :Local\ with sql usre name = admin pwd= ??\ and when i chose next
the error still
regrds ,
amanee
April 30, 2012 at 3:43 am
Are you connecting to Sql Server through an application??....
Try this:
1. Open SQL Server Configuration Manager.
2. In the left side select "Protocols For MSSQLServer" which is under "SQLServer Network Configuration". Check if TCP/IP is enabled. If not enable it.
3. In the left side select "Client Protocols" which is under "SQLNative Client 10.0 Configuration". Check if TCP/IP is enabled. If not enable it.
Does this help?
April 30, 2012 at 3:46 am
al_yamama_1980 (4/30/2012)
Of curse i will tall you all the stepcontrol panel\odbc\sysytem dsn\add\Sql serverame=Local Server , srver :Local\ with sql usre name = admin pwd= ??\ and when i chose next
the error appers.
this is what i do my friend.
regrds
amanee
For Local Server, I suggest Shared Memory protocol instead of TCP/IP.
April 30, 2012 at 3:59 am
Dear vinu512,
I do that but the seem problem i don't know what is the problem?!!!
regards,
April 30, 2012 at 4:11 am
Dear Sir Suresh B.,
Please can you tall me what you mean in shera memory?
in details
thanks
April 30, 2012 at 4:27 am
al_yamama_1980 (4/30/2012)
Dear Sir Suresh B.,Please can you tall me what you mean in shera memory?
in details
thanks
Quoted from BOL
Shared memory is the simplest protocol to use and has no configurable settings. Because clients using the shared memory protocol can only connect to a SQL Server instance running on the same computer, ...
Please see the attached screen shot.
April 30, 2012 at 4:28 am
I definitely feel that it is a case of SQL Server not listening to the connections from the TCP/IP port. I could be wrong.
Last I faced this issue....I followed the steps that were mentioned in the first link I gave you and that had solved my problem.
What is the name of the driver that you select when you create the DSN??
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply