Hi,
I am facing a strange behavior during loging in to SQL server mangement studio.
Whenever I install SQL server express, various protocols like Named Pipe and TCP/IP and SQL browser are disabled by default. But still I am able to log in to SQL Server throguh Management studio.
But when I try to log in to SQL server throguh one of my applications, it allows me to log in to it only for one time. From next time onwards, I am not able to log in to SQL server neither through my application nor through Management studio.
I connect to SQL server using "machine name"\"Instance name". Machine name is the name of machine on my office LAN.
PS: Once this problem occurs, I can log in to SQL server if I use "localhost" instead of "machine name".
Any suggestions would be tremendously helpful.
Regards
-Orion
SQL Express supports connecting through Shared Memory, which is a local connectivity protocol that is used by the SQL Native Client. This is how you're connecting with Management Studio. I can't tell you what the problem is with your application as you have not provided an error message or error log.
Mike
|||Hi Mike,
Thanks for the reply.
>>
I can't tell you what the problem is with your application as you have not provided an error message or error log
>>
Following are the details of the exception thrown by SQL server.
{"State:08001,Native:6,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] State:01000,Native:11004,Origin:[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]"}
The problem is when it allows my application to connect to SQL Server only once. After this, I need to enable TCP/IP protocol for any subsequent connection through my application or SQL Server management studio.
Regards,
Orion
Hi Orion,
Could you define what you mean by "subsequent connections through my application"? Are you talking about a single application creating multiple threads connecting to SQL Server? Are these different copies of the same application being run by other users on other computers? What is the connection string you're using from your application?
I don't recognize that error, is there any more descirptive text?
Mike
No comments:
Post a Comment