[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 341
  • Last Modified:

SBS 2000 Server shuts down intermittently - not a hardware issue

I have a client with a Dell PowerEdge 2500SC Windows 2000 Small Business Server that for the past couple weeks has been shutting itself down for no apparent reason.  The logs show only two things before shutting down:

Information type log entry - event ID 26 - Application popup: java.exe - DLL Initialization Failed : The application failed to initialize because the window station is shutting down.  (this repeats 6 times)

then 20-30 seconds later it shows the typical:

Information type log entry - event ID 6006 - The Event log service was stopped.

When you boot it back up all the log entries are normal and nothing mentions an unexpected shutdown.

Here are some steps I have taken:

- I ran a full virus scan (Symantec AV Corp. 10.0) which came up with only a rather benign trojan which after it was removed made no diffence in it shutting down.  
- It being a Dell, it has a diagnostics utility partition you can boot into and after running the full hardware tests it came back with no errors or warnings.  

A server rebuild does not sound appealling to me or my client so I'm throwing this out there to see if anyone has any thoughts or suggestions.  Thanks.
0
jtgerdes
Asked:
jtgerdes
  • 5
  • 4
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
What are the errors immediately PRECEDING the event 26 errors?  These are already recognizing that windows is shutting down... you need to find out what's happening prior to that.

Jeff
TechSoEasy
0
 
jtgerdesAuthor Commented:
Well that's the thing, it's nothing out of the ordinary, and nothing consistent that is right before it.  In fact there's no errors at all - just information events.  It might be a print job sent 10 minutes earlier or some other normal everyday event that may have been 1 minute or 30 minutes prior to the event 26 errors.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Are you looking in both the application AND system event logs?

Jeff
TechSoEasy
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
jtgerdesAuthor Commented:
yes - I was looking in all the logs for some kind of clues.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Why do you think that this is not a hardware issue?

Jeff
TechSoEasy
0
 
jtgerdesAuthor Commented:
Two reasons:

A. It passed all hardware diagnostic tests with no problems.
B. As I mentioned earlier, it is aware of itself shutting down according to the logs, and upon reboot gives no "unexpected shut down" type error log.

In fact, I rebooted it on purpose to compare the log entries from an unwanted shut down with the log entries of a purposeful reboot and they are identical.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Do you have any Event 5000's in your logs?

What service pack do you have applied?

Jeff
TechSoEasy
0
 
jtgerdesAuthor Commented:
Without looking at it again to double check, I'm fairly certain that there are no event 5000's.

However, interestingly enough, I uninstalled Exchange from it several days ago and it has not shut down since.  It had not been used for a number of months and was not going to be used again.  The services had all been disabled, but I thought I'd give it a shot anyway.  So far so good.  I'll update this if in a week or so if it doesn't shut down again, but so far this is the longest we've gone in a few weeks without it spontaneously shutting down.

Thanks for the suggestions so far though.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
ok, good luck!
0
 
CetusMODCommented:
PAQed with points refunded (500)

CetusMOD
Community Support Moderator
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now