December 21, 2005 at 11:21 pm
THIS IS DRIVING ME NUTS!!
I currently can't connect to my database in SQL Server 2005 (enterprise) but 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:
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
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.
For more information, see Help and
December 23, 2005 at 2:19 am
I wonder if the problem is revealed by the first and last of these error messages .
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>]
...
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
SQL Server is reporting that it has reached the maximum number of user connections, and that it cannot connect to the report server database.
I suggest you check the number of concurrent connections. In SQL Server 2000 you would right click the server in Enterprise Manager, select properties and pick the connections tab from the dialog, looking for the setting for the maximum concurrent user connections (0 is unlimited). This value may be set in a different place in SQL Server 2005.
David
If it ain't broke, don't fix it...
December 27, 2005 at 11:15 am
Take a look at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=178160&SiteID=1 - there's information in there about using DAC to connect to the database. Ultimately though the user uninstalled and resinstalled SQL Server.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply