Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / March 2008

Tip: Looking for answers? Try searching our database.

Cannot login SQL Server with 'sa'

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
kai - 23 Dec 2005 21:08 GMT
Hi,
After I setup 'sa' password in SQL Server 2005,  I get out SQL Server and
re-login using SQL Authentication mode with 'sa' and pasword, I get error:

"A connection was successfully established with the server, but then the
error occured during the login process. (Provider: Shared memeoryprovider,
error 0 - No process is on the other end of the pipe.) (Microsoft SQL Server
: error 233)"

Please help

Thanks

kai
Andrew J. Kelly - 23 Dec 2005 21:19 GMT
Do you have Shared Memory connections enabled?  Run the SQL Server
Configuration Manager and look at the protocols and shared Memory to see if
it is enabled or not.

Signature

Andrew J. Kelly  SQL MVP

> Hi,
> After I setup 'sa' password in SQL Server 2005,  I get out SQL Server and
[quoted text clipped - 10 lines]
>
> kai
kai - 23 Dec 2005 22:10 GMT
Andrew,
 Thanks for your help. I checked it, it is enabled. I found additional
error when I login second time:

"Login failed for user 'sa'.The user is associated with a trusted SQL Server
connection. (Microsoft SQL Server, error: 18452)

Kai
> Do you have Shared Memory connections enabled?  Run the SQL Server
> Configuration Manager and look at the protocols and shared Memory to see
[quoted text clipped - 15 lines]
>>
>> kai
Andrew J. Kelly - 24 Dec 2005 00:06 GMT
See if this may help:
http://support.microsoft.com/?id=328306

Signature

Andrew J. Kelly  SQL MVP

> Andrew,
>  Thanks for your help. I checked it, it is enabled. I found additional
[quoted text clipped - 23 lines]
>>>
>>> kai
Kalen Delaney - 24 Dec 2005 02:20 GMT

Is it possible you're trying to connect multiple times over the dedicated
Admin connection?

Signature

HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com

> Andrew,
>  Thanks for your help. I checked it, it is enabled. I found additional
[quoted text clipped - 23 lines]
>>>
>>> kai
Michael Cheng [MSFT] - 24 Dec 2005 06:14 GMT
Hi Kai,

Generally speaking, error code 18452 suggests SQL Authentication is not
enabled. Would you please check to see whether it was enabled?

- Right Click the instance name in the Object Explorer, select Properties
- Select Security page and make sure SQL Server and Windows Authentication
mode is selected.

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

kai - 24 Dec 2005 21:49 GMT
Michael ,

 Thank you for your help.
 It is enabled. I check my other two SQL Servers, they all have the same
problems.
Kai

> Hi Kai,
>
[quoted text clipped - 15 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Michael Cheng [MSFT] - 26 Dec 2005 08:43 GMT
Hi Kai,

This issue occurs because SQL Server Management Studio cannot correctly
report the error when the maximum number of concurrent connections has been
reached.

To work around this issue, you can use the sp_configure Transact-SQL
procedure to increase the maximum number of concurrent connections. You can
also manage the instance of SQL Server 2005 in other ways. For example, you
can use the sqlcmd utility.

To use sp_configure to increase the maximum number of concurrent
connections, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.  
2. At the command prompt, type the following command, and then press ENTER.
sqlcmd.exe -E -S servername  
3. When you successfully connect to the instance of SQL Server 2005,
execute the following Transact-SQL statements at the SQL Server prompt.
sp_configure 'user connections', <NewNumber>
Go
Reconfigure
Go

4. Restart the SQL Server service for the change to take effect.  

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

kai - 29 Dec 2005 20:04 GMT
Michael,
Thank you very much for your help.
When I installed SQL Server 2005 initially, I use Wondows Authentication
mode. After the installation, I changed to Mixed mode. Then I setup the new
password for 'sa' and other SQL Server logins, I cannot login with any SQL
logins.

I just found out the Login properties (status) for those SQL logins ware
setup to "Disable" by default, after I change them to "Enaled", I can login
with SQL logins.

Thank you so much !!!

Kai

> Hi Kai,
>
[quoted text clipped - 39 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Michael Cheng [MSFT] - 30 Dec 2005 05:51 GMT
Hi Kai,

Happy New Year! You are welcome!

If you have any questions or concerns next time, don't hesitate to let me
know. We are always here to be of assistance!

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

muzammil - 20 Mar 2008 07:05 GMT
Kai,

Can you please guide me where exactly u changed it to Enabled?

url:http://www.ureader.com/msg/1158785.aspx
Erland Sommarskog - 20 Mar 2008 11:38 GMT
> Kai,
>
> Can you please guide me where exactly u changed it to Enabled?
>
> url:http://www.ureader.com/msg/1158785.aspx

You are replying to a message from 2005, and the thread is full of various
tips.

If none of those tips help you, I suggest that you state your problem more
clearly, since it may be different from in the old thread. Also specify
which verion of SQL Server you are using.

Signature

Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Sanjay Turkhade - 07 Aug 2007 10:49 GMT
By default max no. of connections is set to 10.
To increase the maximum no. of connections

1. In Object Explorer, right-click a server and click Properties.
2. Click the Connections node.
3. Under Connections, in the Max number of concurrent connections box, type
or select a value from 0 through 32767 to set the maximum number of users
that are allowed to connect simultaneously to the instance of SQL Server.

set it to 0 (it means unlimited connections)
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.