I currently can't connecto to my database in SQL Server 2005 (enterprise) from the SQL Server Management Studio itself! as soon as I try to use any functions, I get cryptic errors found below. I am about to pull my hair out. Everything was working fine for around 4 days and now everything just blows up. I've tried using both sql authentification and also windows:< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Errors I'm getting (print screens):
http:
SQL logs:
http:
Event log errors are:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17809
Date: 12/21/2005
Time: 11:18:34 PM
User: N/A
Computer: BG-SQL2005
Description:
Could not connect because the maximum number of '4' user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed. [CLIENT: <local machine>]
For more information, see Help and < xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" />
Data:
0000: 91 45 00 00 14 00 00 00 E......
0008: 0b 00 00 00 42 00 47 00 ....B.G.
0010: 2d 00 53 00 51 00 4c 00 -.S.Q.L.
0018: 32 00 30 00 30 00 35 00 2.0.0.5.
0020: 00 00 00 00 00 00 ......
Event Type: Failure Audit
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 18456
Date: 12/21/2005
Time: 10:34:03 PM
User: N/A
Computer: BG-SQL2005
Description:
Login failed for user 'sa'. [CLIENT: <local machine>]
For more information, see Help and
Data:
0000: 18 48 00 00 0e 00 00 00 .H......
0008: 0b 00 00 00 42 00 47 00 ....B.G.
0010: 2d 00 53 00 51 00 4c 00 -.S.Q.L.
0018: 32 00 30 00 30 00 35 00 2.0.0.5.
0020: 00 00 07 00 00 00 6d 00 ......m.
0028: 61 00 73 00 74 00 65 00 a.s.t.e.
0030: 72 00 00 00 r...
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 8561
Date: 12/21/2005
Time: 10:19:51 PM
User: N/A
Computer: BG-SQL2005
Description:
Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
For more information, see Help and
Data:
0000: 71 21 00 00 0a 00 00 00 q!......
0008: 0b 00 00 00 42 00 47 00 ....B.G.
0010: 2d 00 53 00 51 00 4c 00 -.S.Q.L.
0018: 32 00 30 00 30 00 35 00 2.0.0.5.
0020: 00 00 07 00 00 00 6d 00 ......m.
0028: 61 00 73 00 74 00 65 00 a.s.t.e.
0030: 72 00 00 00 r...
Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 12/21/2005
Time: 4:46:14 PM
User: N/A
Computer: BG-SQL2005
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
Cannot connect to Database in Server Management Studio
SuperNova298
excittor
Still weird though, but glad you can get back to work :-)
Sandyboy
yes, that's what I have been doing, terminal into it because it's a an MS Virtual Server. Yes, I can ping it and can ODBC to from my Windows XP Machine. I can also ping it from the server itself.
>>>>If so, first check your SQL Server Configuration Manager for any misconfigurations
as far as I can tell it is configured fine and has been all along..unless something has changed but I do not recall changing anything.
Here are screen shots of my Configuration Manager:
Keep in mind this was all working fine before. I did change a few settings in TCP/IP in the configuration manager but then they're all back to normal as far as I can tell...I changed them back.
http://www.photopizzaz.biz/junk/configuration_manager.doc
I have enabled remote connection via TCP/IP in the Remote properties in the SQL Server Service configuration window for both the SQL Server Engine and Also Analysis services...so I don't understand why I get the error saying that remote is not enabled. I stopped and restarted the Engine several times throughout the course of 2 days but no luck, I still get that message also amongst all the others including one talking about named pipes as I have stated in which is also disabled!
uray
If so, first check your SQL Server Configuration Manager for any misconfigurations.
Let us know if this is properly configured.
hth
WesleyB
Visit my SQL Server weblog @ http://dis4ea.blogspot.com
taltaltal28
Check out this post, maybe you can find some interesting tips.
WesleyB
Visit my SQL Server weblog @ http://dis4ea.blogspot.com
William Friant
More info
TITLE: Connect to Server
------------------------------
Cannot connect to BG-SQL2005.
------------------------------
ADDITIONAL INFORMATION:
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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
C. McGrunty