Hello,
I have a SECC 4.02.06 that reboots every two weeks on Sunday night at 10:12pm. Sometimes the system will come back up by itself and have a elan connection to the switch the next time I'll have to reboot it again to get a connection.I read thread 959-1003108 about having reports scheduled with invalid destinations. So,I tried rebooting it myself the Friday before to see if it would still reboot by itself again Sunday night and it still did. I did notice that before daylight savings time changed, it was doing this at 9:12pm then went to 10:1pm after that.
Does anyone having any suggestions?
Below is from the event browser.
Sunday, July 13, 2008 11:08:28 PM 41550 Alarm Set Critical System Manager Service 0 The SM could not start service SDMCA_Service.
Sunday, July 13, 2008 10:54:40 PM 41550 Alarm Set Critical System Manager Service 0 The SM could not start service RDC_Service.
Sunday, July 13, 2008 10:40:52 PM 41550 Alarm Set Critical System Manager Service 0 The SM could not start service OAM_Service.
Sunday, July 13, 2008 10:12:30 PM 40592 Alarm Set Critical Fault: NT Log Monitor 0 Event from NT System Log(EventLog), Event: ID=6008, Description: The previous system shutdown at 10:06:23 PM on 7/13/2008 was unexpected. .
Saturday, July 12, 2008 4:55:36 AM 40592 Alarm Set Critical Fault: NT Log Monitor 0 Event from NT System Log(Service Control Manager), Event: ID=7031, Description: The Sybase BCKServer _ VHAAMAMUL7_BS service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action. .
Friday, July 11, 2008 4:52:09 PM 40592 Alarm Set Critical Fault: NT Log Monitor 0 Event from NT System Log(Service Control Manager), Event: ID=7024, Description: The MAS Time Service service terminated with service-specific error 41507. .
I have a SECC 4.02.06 that reboots every two weeks on Sunday night at 10:12pm. Sometimes the system will come back up by itself and have a elan connection to the switch the next time I'll have to reboot it again to get a connection.I read thread 959-1003108 about having reports scheduled with invalid destinations. So,I tried rebooting it myself the Friday before to see if it would still reboot by itself again Sunday night and it still did. I did notice that before daylight savings time changed, it was doing this at 9:12pm then went to 10:1pm after that.
Does anyone having any suggestions?
Below is from the event browser.
Sunday, July 13, 2008 11:08:28 PM 41550 Alarm Set Critical System Manager Service 0 The SM could not start service SDMCA_Service.
Sunday, July 13, 2008 10:54:40 PM 41550 Alarm Set Critical System Manager Service 0 The SM could not start service RDC_Service.
Sunday, July 13, 2008 10:40:52 PM 41550 Alarm Set Critical System Manager Service 0 The SM could not start service OAM_Service.
Sunday, July 13, 2008 10:12:30 PM 40592 Alarm Set Critical Fault: NT Log Monitor 0 Event from NT System Log(EventLog), Event: ID=6008, Description: The previous system shutdown at 10:06:23 PM on 7/13/2008 was unexpected. .
Saturday, July 12, 2008 4:55:36 AM 40592 Alarm Set Critical Fault: NT Log Monitor 0 Event from NT System Log(Service Control Manager), Event: ID=7031, Description: The Sybase BCKServer _ VHAAMAMUL7_BS service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: No action. .
Friday, July 11, 2008 4:52:09 PM 40592 Alarm Set Critical Fault: NT Log Monitor 0 Event from NT System Log(Service Control Manager), Event: ID=7024, Description: The MAS Time Service service terminated with service-specific error 41507. .