 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Clustering / July 2008Event ID 17055 (18052 Error:826)
Lost power on the active node of my SQL Server. It failed over to Node 2 without problem, but when I brought it back to Node 1 (the server that lost power) I get Event ID 17055 Error Description 18052 Error 826 Severity 22 The MSSQLServer service trys to start and then stops. I can't find anything on this specific error. Thanks, Paul Sounds like the MSSQL service is set to start up automatically. A clustered SQL service should be set to Manual start. The Cluster service handles starting and stopping the actual SQL services. SQL likely failed because its disk resources were not online on Node 1.  SignatureGeoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP > Lost power on the active node of my SQL Server. It failed over to Node 2 > without problem, but when I brought it back to Node 1 (the server that [quoted text clipped - 10 lines] > Thanks, > Paul Services are set correctly. Disk resources are on the node and accessable. The service starts and then immediately stops when attempting to start from Services. > Sounds like the MSSQL service is set to start up automatically. A clustered > SQL service should be set to Manual start. The Cluster service handles [quoted text clipped - 15 lines] > > Thanks, > > Paul Anything in the SQL Server errorlog - beyond what you have posted? SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau Services are set correctly. Disk resources are on the node and accessable. The service starts and then immediately stops when attempting to start from Services. "Geoff N. Hiten" wrote: > Sounds like the MSSQL service is set to start up automatically. A > clustered [quoted text clipped - 16 lines] > > Thanks, > > Paul Nope, that's pretty much everything. Paul > Anything in the SQL Server errorlog - beyond what you have posted? > [quoted text clipped - 24 lines] > > > Thanks, > > > Paul Anything in the system application log? Is this the exact same not physically repaired or is it a replacement node with a new OS? SignatureGeoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP > Nope, that's pretty much everything. > [quoted text clipped - 33 lines] >> > > Thanks, >> > > Paul Nothing different on the system, simply lost power due to a faulty UPS. Brought the system back up when the power came back on. Nothing in the system log. Paul > Anything in the system application log? > [quoted text clipped - 38 lines] > >> > > Thanks, > >> > > Paul Sorry if I was not specific enough. Look in the Application Log to see if there are any extended error messages related to startup failures for SQL. SQL logs errors in its own error log once it is running, but it logs in the Application log when it fails to start. SignatureGeoff N. Hiten Principal SQL Infrastructure Consultant Microsoft SQL Server MVP > Nothing different on the system, simply lost power due to a faulty UPS. > Brought the system back up when the power came back on. [quoted text clipped - 47 lines] >> >> > > Thanks, >> >> > > Paul Geoff, The reason I am posting is because there is no additional information in any of the logs. I have reviewed Application, System, and Security logs. I have reviewed the SQL Logs. The only thing they say is: Event ID 17055, in the description it states 18052 Error:826 Severity:24(mis-stated in initial post) and State:6. Nothing else in any of the logs. I cannot post the logs since the servers are in a Government facility. Thanks, Paul > Sorry if I was not specific enough. Look in the Application Log to see if > there are any extended error messages related to startup failures for SQL. [quoted text clipped - 52 lines] > >> >> > > Thanks, > >> >> > > Paul Sorry to say this, but you may be looking at opening a ticket with Microsoft. SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau Geoff, The reason I am posting is because there is no additional information in any of the logs. I have reviewed Application, System, and Security logs. I have reviewed the SQL Logs. The only thing they say is: Event ID 17055, in the description it states 18052 Error:826 Severity:24(mis-stated in initial post) and State:6. Nothing else in any of the logs. I cannot post the logs since the servers are in a Government facility. Thanks, Paul "Geoff N. Hiten" wrote: > Sorry if I was not specific enough. Look in the Application Log to see if > there are any extended error messages related to startup failures for SQL. [quoted text clipped - 52 lines] > >> >> > > Thanks, > >> >> > > Paul > The service starts and then immediately stops when attempting to start from > Services. Did you try to start it from Cluster Administrator by bringing the SQL Server resource online? Linchi > Services are set correctly. Disk resources are on the node and accessable. > The service starts and then immediately stops when attempting to start from [quoted text clipped - 19 lines] > > > Thanks, > > > Paul I first attempted to start it from Cluster Administrator, then when the resource failed I tried to start it from Services. Paul > > The service starts and then immediately stops when attempting to start from > > Services. [quoted text clipped - 27 lines] > > > > Thanks, > > > > Paul > Lost power on the active node of my SQL Server. It failed over to Node 2 > without problem, but when I brought it back to Node 1 (the server that lost [quoted text clipped - 8 lines] > Thanks, > Paul Review the document at http://www.eventid.net/display.asp?eventid=17055&eventno=251&source=MSSQLServer& phase=1 Towards the middle of the page, I found this: Error: 18052 - Startup of MSSQLServer fails with this listed in Event Viewer and no real additional information. I found that a second startup parameter for the master_log_path was added pointing to an invalid file, conflicting with the default (mastlog.ldf). The only resolution was via Regedit -> HKLM\Software\Microsoft\MSSQLServer\Parameters\SQLArg#. Look for a duplicate -l pointing to anything but the mastlog.ldf and remove it. This may cause some errors on the master_file_path and error_log_path; situation that I have not tested. Don't know if this applies, but worth a shot. Jeff |
Reply to this Message |
 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
|
©2008 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.