![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
You said you tried using sp_configure but I'll ask you to go to EM and connect to your instance and then go to SQL Server Properties dialog box and select Connections tab and check the "Maximum concurrent user connections" option for this situation. If it's set to 15 or something, please change it to "0" which means unlimited connections are going to be accepted by SQL Server. Please let me know about the result of this course. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:EEB5A7C4-2ECA-47EC-BF23-DC2EB21989B6 (AT) microsoft (DOT) com... Problem description ============== - I have 4 clients and 1 server (SQL server) - 3 clients are Monitoring console 1 client is operation console - Monitoring console collects some data from the control unit and store them into the Sql server - The operation console then retrieve this data from the sql for reporting and statistics purposes - I am using ODBC connection - The problem is that the operation console is not able to connect to Sql server - I receive Error message: “A connection could not be established to fileserver-(SQL server). Unable to connect. The max number of 15 configured user connections are already connected. System administrator can configure to a higher value with SP_Configure” - I receive the same error message in many conditions while I am using the EM (Enterprise Manager) GUI Environment ======== Windows NT 4.0 SQL 6.5 Troubleshooting (we have done & Analysis) ===== - Seems that sql server has reached the max allowable number of connections - It might be some opened connection those never being closed by some application. - This problem also appears when 7.5 installed while 6.5 is also installed, however I don’t have 7.5 installed - We tried to perform: Exec sp_configure ‘user connections’, 25 Go RECONFIGURE Go And then try to restart the sql server - I was unable to execute the above steps as I was receiving time out - Unable to stop/restart Sql server, I had to reboot to start sql server (I was being interrupted with the error message again) - Check sql configuration parameters from EM, I checked: 1. “conn time out” : reasonable values for Min, Max and running 2. “worker threads”: reasonable values for Min, Max and running 3. “user connections”: reasonable values for Min, Max and running - Seems no problem with configuration parameters (the major ones related to the symptoms we have at least) - Also we performed restar for sql server service through the rebooting with no impact on the problem - We tried to truncate the log file of the database as I suspected it causes a problem, we performed the following procedure: Backup LOG <your database name> with truncate_only - Try to restart your sql server, no avail - We checked scheduled tasks, as you mentioned that this problem started to appear three weeks ago and I noted that when I restart the sql server or stop the clients the problem disappears but reoccurs each Sunday, we found one scheduled task which configured to run in the exact same time (on Sunday) however you added that restarting your server is no more effective to temporary solve the problem as before (and this is obvious through our trials above to restart the server) - We tried to remove that schedule task and then restart as it might be the cause of the problem - I was unable to remove the scheduled task, and I received another error message related to Sql server!! - While we were performing the above steps, I have been interrupted with the same error message while I am using the query analyzer - The server looks to be in very unstable state, so I need some recommendations to fix the problem as mentioned bove. Waiting for any feedback recommended to fix the server problem. |
#3
| |||
| |||
|
|
Something pulls you back from changing it but I can't figure out what it is from this message unfortunately ![]() You can clear the Application Log from Event Viewer. Go to Event Viewer and right click on it and clear it. If you need to keep that log, then save it before clearing. I could suggest you to connect to your SQL Server in a Single-User mode and then try that change in that mode. You can do that going to SQL Server Configuration Manager and go to properties of SQL Server service. Go to Advanced tab and add "-m;" parameter to the Startup Parameters. Restart your SQL Server service and then try changing Maximum concurrent connections value. After performing this, do not forget to going back to SQL Server service properties and erasing that "-m" parameter and restarting your SQL Server service. Otherwise, nobody except for you could loging to SQL Server. Also, stop SQL Server agent before trying to login to SQL Server when it's in Single User mode, because it may try to use that Single-User right and then you may end up failing to login to SQL Server because of SQL Server Agent service. Please let me know about the result of this process if you proceed. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:485D24AF-35CA-4577-8A42-7B2E3403E6B7 (AT) microsoft (DOT) com... Thank you for your tips. I've tried to change the user connections to 0, I found the error message was no more active for a long period before it reactivated again at the end but with connections user 25! Through that time I've received the following message "A connection could not be established to fileserver - (DB-Library) SQL server connection Timed out". "SQL server connection time out. Do you wish to retry? "ERROR 10024 (DB Library) SQL server connection time out" Msg No 10007 Severity 5 State 0. General SQL server error. Here some more problem clarification that it could help fixing the problem - The working data base is marked inaccessible and cannot be edited - The following message appears when restart the server and before login "The application log file is full" If you have any further useful tips, please do not hesitate to send it to me. Thank you and best regards. KHATER "Ekrem Önsoy" wrote: You said you tried using sp_configure but I'll ask you to go to EM and connect to your instance and then go to SQL Server Properties dialog box and select Connections tab and check the "Maximum concurrent user connections" option for this situation. If it's set to 15 or something, please change it to "0" which means unlimited connections are going to be accepted by SQL Server. Please let me know about the result of this course. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:EEB5A7C4-2ECA-47EC-BF23-DC2EB21989B6 (AT) microsoft (DOT) com... Problem description ============== - I have 4 clients and 1 server (SQL server) - 3 clients are Monitoring console 1 client is operation console - Monitoring console collects some data from the control unit and store them into the Sql server - The operation console then retrieve this data from the sql for reporting and statistics purposes - I am using ODBC connection - The problem is that the operation console is not able to connect to Sql server - I receive Error message: “A connection could not be established to fileserver-(SQL server). Unable to connect. The max number of 15 configured user connections are already connected. System administrator can configure to a higher value with SP_Configure” - I receive the same error message in many conditions while I am using the EM (Enterprise Manager) GUI Environment ======== Windows NT 4.0 SQL 6.5 Troubleshooting (we have done & Analysis) ===== - Seems that sql server has reached the max allowable number of connections - It might be some opened connection those never being closed by some application. - This problem also appears when 7.5 installed while 6.5 is also installed, however I don’t have 7.5 installed - We tried to perform: Exec sp_configure ‘user connections’, 25 Go RECONFIGURE Go And then try to restart the sql server - I was unable to execute the above steps as I was receiving time out - Unable to stop/restart Sql server, I had to reboot to start sql server (I was being interrupted with the error message again) - Check sql configuration parameters from EM, I checked: 1. “conn time out” : reasonable values for Min, Max and running 2. “worker threads”: reasonable values for Min, Max and running 3. “user connections”: reasonable values for Min, Max and running - Seems no problem with configuration parameters (the major ones related to the symptoms we have at least) - Also we performed restar for sql server service through the rebooting with no impact on the problem - We tried to truncate the log file of the database as I suspected it causes a problem, we performed the following procedure: Backup LOG <your database name> with truncate_only - Try to restart your sql server, no avail - We checked scheduled tasks, as you mentioned that this problem started to appear three weeks ago and I noted that when I restart the sql server or stop the clients the problem disappears but reoccurs each Sunday, we found one scheduled task which configured to run in the exact same time (on Sunday) however you added that restarting your server is no more effective to temporary solve the problem as before (and this is obvious through our trials above to restart the server) - We tried to remove that schedule task and then restart as it might be the cause of the problem - I was unable to remove the scheduled task, and I received another error message related to Sql server!! - While we were performing the above steps, I have been interrupted with the same error message while I am using the query analyzer - The server looks to be in very unstable state, so I need some recommendations to fix the problem as mentioned bove. Waiting for any feedback recommended to fix the server problem. |
#4
| |||
| |||
|
|
Please can you tell me what is the difference between the application log and the transaction log? if both of them are identical, can I use the commnd "DUMP trnsaction log"?. Is it necessary to dump database after processing DUMP transaction log?. Please can you tell me the difference between DUMP and DROP database? Thank you "Ekrem nsoy" wrote: Something pulls you back from changing it but I can't figure out what it is from this message unfortunately ![]() You can clear the Application Log from Event Viewer. Go to Event Viewer and right click on it and clear it. If you need to keep that log, then save it before clearing. I could suggest you to connect to your SQL Server in a Single-User mode and then try that change in that mode. You can do that going to SQL Server Configuration Manager and go to properties of SQL Server service. Go to Advanced tab and add "-m;" parameter to the Startup Parameters. Restart your SQL Server service and then try changing Maximum concurrent connections value. After performing this, do not forget to going back to SQL Server service properties and erasing that "-m" parameter and restarting your SQL Server service. Otherwise, nobody except for you could loging to SQL Server. Also, stop SQL Server agent before trying to login to SQL Server when it's in Single User mode, because it may try to use that Single-User right and then you may end up failing to login to SQL Server because of SQL Server Agent service. Please let me know about the result of this process if you proceed. -- Ekrem nsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:485D24AF-35CA-4577-8A42-7B2E3403E6B7 (AT) microsoft (DOT) com... Thank you for your tips. I've tried to change the user connections to 0, I found the error message was no more active for a long period before it reactivated again at the end but with connections user 25! Through that time I've received the following message "A connection could not be established to fileserver - (DB-Library) SQL server connection Timed out". "SQL server connection time out. Do you wish to retry? "ERROR 10024 (DB Library) SQL server connection time out" Msg No 10007 Severity 5 State 0. General SQL server error. Here some more problem clarification that it could help fixing the problem - The working data base is marked inaccessible and cannot be edited - The following message appears when restart the server and before login "The application log file is full" If you have any further useful tips, please do not hesitate to send it to me. Thank you and best regards. KHATER "Ekrem nsoy" wrote: You said you tried using sp_configure but I'll ask you to go to EM and connect to your instance and then go to SQL Server Properties dialog box and select Connections tab and check the "Maximum concurrent user connections" option for this situation. If it's set to 15 or something, please change it to "0" which means unlimited connections are going to be accepted by SQL Server. Please let me know about the result of this course. -- Ekrem nsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:EEB5A7C4-2ECA-47EC-BF23-DC2EB21989B6 (AT) microsoft (DOT) com... Problem description ============== - I have 4 clients and 1 server (SQL server) - 3 clients are Monitoring console 1 client is operation console - Monitoring console collects some data from the control unit and store them into the Sql server - The operation console then retrieve this data from the sql for reporting and statistics purposes - I am using ODBC connection - The problem is that the operation console is not able to connect to Sql server - I receive Error message: "A connection could not be established to fileserver-(SQL server). Unable to connect. The max number of 15 configured user connections are already connected. System administrator can configure to a higher value with SP_Configure" - I receive the same error message in many conditions while I am using the EM (Enterprise Manager) GUI Environment ======== Windows NT 4.0 SQL 6.5 Troubleshooting (we have done & Analysis) ===== - Seems that sql server has reached the max allowable number of connections - It might be some opened connection those never being closed by some application. - This problem also appears when 7.5 installed while 6.5 is also installed, however I don't have 7.5 installed - We tried to perform: Exec sp_configure 'user connections', 25 Go RECONFIGURE Go And then try to restart the sql server - I was unable to execute the above steps as I was receiving time out - Unable to stop/restart Sql server, I had to reboot to start sql server (I was being interrupted with the error message again) - Check sql configuration parameters from EM, I checked: 1. "conn time out" : reasonable values for Min, Max and running 2. "worker threads": reasonable values for Min, Max and running 3. "user connections": reasonable values for Min, Max and running - Seems no problem with configuration parameters (the major ones related to the symptoms we have at least) - Also we performed restar for sql server service through the rebooting with no impact on the problem - We tried to truncate the log file of the database as I suspected it causes a problem, we performed the following procedure: Backup LOG <your database name> with truncate_only - Try to restart your sql server, no avail - We checked scheduled tasks, as you mentioned that this problem started to appear three weeks ago and I noted that when I restart the sql server or stop the clients the problem disappears but reoccurs each Sunday, we found one scheduled task which configured to run in the exact same time (on Sunday) however you added that restarting your server is no more effective to temporary solve the problem as before (and this is obvious through our trials above to restart the server) - We tried to remove that schedule task and then restart as it might be the cause of the problem - I was unable to remove the scheduled task, and I received another error message related to Sql server!! - While we were performing the above steps, I have been interrupted with the same error message while I am using the query analyzer - The server looks to be in very unstable state, so I need some recommendations to fix the problem as mentioned bove. Waiting for any feedback recommended to fix the server problem. |
#5
| |||
| |||
|
|
Application Log is nothing to do with Transaction Log. They are totally different things. Don't confuse yourself with that. Application Log is about Windows and it keeps logs of Application Events. Transaction Log containt all your activities about the database that it belongs to. Please read the following articles from BOL: DUMP Makes a backup copy of a database (DUMP DATABASE) or makes a copy of the transaction log (DUMP TRANSACTION) in a form that can be read into Microsoft® SQL Server™ using the BACKUP or LOAD statements. Important The DUMP statement is included in SQL Server version 2000 for backward compatibility. It is recommended that the BACKUP statement be used instead of the DUMP statement. In a future version of SQL Server, DUMP will not be supported. DROP DATABASE Removes one or more databases from Microsoft® SQL Server™. Removing a database deletes the database and the disk files used by the database. You may find more information about Transact-SQL commands and much more from Books Online: http://msdn2.microsoft.com/en-us/library/bb545450.aspx -- Ekrem Önsoy "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:393777BD-CE08-4C42-9466-788421073E98 (AT) microsoft (DOT) com... Please can you tell me what is the difference between the application log and the transaction log? if both of them are identical, can I use the commnd "DUMP trnsaction log"?. Is it necessary to dump database after processing DUMP transaction log?. Please can you tell me the difference between DUMP and DROP database? Thank you "Ekrem Önsoy" wrote: Something pulls you back from changing it but I can't figure out what it is from this message unfortunately ![]() You can clear the Application Log from Event Viewer. Go to Event Viewer and right click on it and clear it. If you need to keep that log, then save it before clearing. I could suggest you to connect to your SQL Server in a Single-User mode and then try that change in that mode. You can do that going to SQL Server Configuration Manager and go to properties of SQL Server service. Go to Advanced tab and add "-m;" parameter to the Startup Parameters. Restart your SQL Server service and then try changing Maximum concurrent connections value. After performing this, do not forget to going back to SQL Server service properties and erasing that "-m" parameter and restarting your SQL Server service. Otherwise, nobody except for you could loging to SQL Server. Also, stop SQL Server agent before trying to login to SQL Server when it's in Single User mode, because it may try to use that Single-User right and then you may end up failing to login to SQL Server because of SQL Server Agent service. Please let me know about the result of this process if you proceed. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:485D24AF-35CA-4577-8A42-7B2E3403E6B7 (AT) microsoft (DOT) com... Thank you for your tips. I've tried to change the user connections to 0, I found the error message was no more active for a long period before it reactivated again at the end but with connections user 25! Through that time I've received the following message "A connection could not be established to fileserver - (DB-Library) SQL server connection Timed out". "SQL server connection time out. Do you wish to retry? "ERROR 10024 (DB Library) SQL server connection time out" Msg No 10007 Severity 5 State 0. General SQL server error. Here some more problem clarification that it could help fixing the problem - The working data base is marked inaccessible and cannot be edited - The following message appears when restart the server and before login "The application log file is full" If you have any further useful tips, please do not hesitate to send it to me. Thank you and best regards. KHATER "Ekrem Önsoy" wrote: You said you tried using sp_configure but I'll ask you to go to EM and connect to your instance and then go to SQL Server Properties dialog box and select Connections tab and check the "Maximum concurrent user connections" option for this situation. If it's set to 15 or something, please change it to "0" which means unlimited connections are going to be accepted by SQL Server. Please let me know about the result of this course. -- Ekrem Önsoy MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT "KHATER" <KHATER (AT) discussions (DOT) microsoft.com> wrote in message news:EEB5A7C4-2ECA-47EC-BF23-DC2EB21989B6 (AT) microsoft (DOT) com... Problem description ============== - I have 4 clients and 1 server (SQL server) - 3 clients are Monitoring console 1 client is operation console - Monitoring console collects some data from the control unit and store them into the Sql server - The operation console then retrieve this data from the sql for reporting and statistics purposes - I am using ODBC connection - The problem is that the operation console is not able to connect to Sql server - I receive Error message: “A connection could not be established to fileserver-(SQL server). Unable to connect. The max number of 15 configured user connections are already connected. System administrator can configure to a higher value with SP_Configure” - I receive the same error message in many conditions while I am using the EM (Enterprise Manager) GUI Environment ======== Windows NT 4.0 SQL 6.5 Troubleshooting (we have done & Analysis) ===== - Seems that sql server has reached the max allowable number of connections - It might be some opened connection those never being closed by some application. - This problem also appears when 7.5 installed while 6.5 is also installed, however I don’t have 7.5 installed - We tried to perform: Exec sp_configure ‘user connections’, 25 Go RECONFIGURE Go And then try to restart the sql server - I was unable to execute the above steps as I was receiving time out - Unable to stop/restart Sql server, I had to reboot to start sql server (I was being interrupted with the error message again) - Check sql configuration parameters from EM, I checked: 1. “conn time out” : reasonable values for Min, Max and running 2. “worker threads”: reasonable values for Min, Max and running 3. “user connections”: reasonable values for Min, Max and running - Seems no problem with configuration parameters (the major ones related to the symptoms we have at least) - Also we performed restar for sql server service through the rebooting with no impact on the problem - We tried to truncate the log file of the database as I suspected it causes a problem, we performed the following procedure: Backup LOG <your database name> with truncate_only - Try to restart your sql server, no avail - We checked scheduled tasks, as you mentioned that this problem started to appear three weeks ago and I noted that when I restart the sql server or stop the clients the problem disappears but reoccurs each Sunday, we found one scheduled task which configured to run in the exact same time (on Sunday) however you added that restarting your server is no more effective to temporary solve the problem as before (and this is obvious through our trials above to restart the server) - We tried to remove that schedule task and then restart as it might be the cause of the problem - I was unable to remove the scheduled task, and I received another error message related to Sql server!! - While we were performing the above steps, I have been interrupted with the same error message while I am using the query analyzer - The server looks to be in very unstable state, so I need some recommendations to fix the problem as mentioned bove. Waiting for any feedback recommended to fix the server problem. |
![]() |
| Thread Tools | |
| Display Modes | |
| |