Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
billey100
Starting Member
12 Posts |
 Posted - 2007-05-09 : 09:28:44
|
| This may be a long post so bare with me. I posted a few weeks ago with a SQL issue involving Backup Exec. Long story short I wiped out all SQL on my server and reinstalled Backup exec. It was running fine for about a week and this morning I came in and I can't start the console becasue the services are stopped. I can't start any of them and it is giving me the same errors as before I reloaded. It is a fresh copy of Backup Exec 11d which loads a SQL Express it says. I wiped everything out before the install becasue this is the only thing using sql, after I loaded BE back on I now have in my add/remove programs Micosoft SQL Server 2005, Microsoft SQL Server Native Client, Microsoft SQL Server Setup Support Files, Microsoft SQL Server VSS Writer and also I have MSXML 4.0 SP2 and MSXML 4.0 SP2 Parser/SDK and MSXML 6.0. I had a one time shot with symantec and thats when we reloaded BE and he told me that BE has something to do with MSXML. So this morning I had this in my event viewer Event ID 1000 Faulting application sqlservr.exe, version 2005.90.2047.0, faulting module kernel32.dll, version 5.2.3790.2756, fault address 0x00015e02.I can't start SQL Server (BKUPEXEC) or SQL Server Browser in my services as they give me the error 1053 The service did not respond to the start or control request in a timely fashion.What am I doing wrong why did the service just quit in the middle of the night for no reason after working great for a week or so? Is this more of a symantec issue? Thanks for all the help. |
|
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2007-05-09 : 09:48:52
|
| Do a search on the computer for a file called ERRORLOG. It should show a last modified date of when you last restarted (or attempted to restart) SQL Server. This file should have some clues in it (like a real error message). |
 |
|
|
billey100
Starting Member
12 Posts |
Posted - 2007-05-09 : 10:04:35
|
| Here is what I found and it corresponds to the times in my event viewer, looks like at somepoint that server lost power according to this log but I am not a SQL guy what does the rest of this message mean? SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.2007-05-09 03:24:08.33 spid11s Service Broker manager has shut down.2007-05-09 03:24:08.38 spid11s Error: 17054, Severity: 16, State: 1.2007-05-09 03:24:08.38 spid11s The current event was not reported to the Windows Events log. Operating system error = 1717(The interface is unknown.). You may need to clear the Windows Events log if it is full.2007-05-09 03:24:09.99 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.2007-05-09 03:24:10.69 Server The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x45b. Administrator should deregister this SPN manually to avoid client authentication errors. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-05-09 : 13:12:16
|
| "SQL Server is terminating because of a system shutdown"This is a NORMAL shutdown, not an abnormal one. Once the shutdown of SQL Server is initiated anything that tries to talk to it will be told to "buzz off", so the errors after that point are probably not relevant - although I'm not sure about the very last one.So something shutdown your server - Windows Update set to "automatic reboot" maybe? - the Windows Event log may have a clue as to what "authorised" the restartKristen |
|
|
|
billey100
Starting Member
12 Posts |
Posted - 2007-05-09 : 14:10:34
|
| Why would they not start back up when I reboot then? Is there anything I can do to get the services to start again short of reloading BE? |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-05-09 : 15:01:46
|
I thought that when I was writing my earlier reply, but I don't know the answer.I presume the Backup Exec services are set to auto-start?Maybe they auto-start but SQL Server takes sufficiently long to start that it isn't ready and they abort?If so maybe a BATCH file that starts them - i.e. that you schedule to launch at startup (perhaps with an initial SLEEP delay to give the SQL Service time to get fully upright)?All sounds a bit string-and-chewing-gum to me ... given that Backup Exec has been around for a while.Either way, I hate those sort of processes; they often seem to cause more problems than the weight that they punch at  Kristen |
|
|
|
billey100
Starting Member
12 Posts |
Posted - 2007-05-09 : 17:21:29
|
| Yeah its a very basic server running one software program and this BE is brand new and not backing up a ton. It's not like I am running a ton of stuff on here and something else is conflicting. |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-05-10 : 04:23:07
|
| Hmmm ... stick BE on another machine, and have it "pull" what it wants to backup from this server (and any others you want covered too)?We run BE here to backup our server, but I don't think we are running a service, we just launch the EXE in a batch file that runs on a scheduled ... but its years since we set it up, so I may have misremembered that!Kristen |
|
|
|
|
|
|
|
|
Reoccuring problem