• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 971
  • Last Modified:

Server 2003 restarting on it's own

we are using server 2003...........
we have not installed any ew software for months.... but now realize that it is constantly restarting...we get a system failure - stop error... and there are codes for it..  0x0000008e ( 0xc 0000005, 0x8081bbd5 , 0xf2bcec 98, 0x00000000 )... this usually leads me to a MS error messge thelling me that i have a device prolem... but not which one...
how do you begin to break this down and out?
looking for an interesting discusion....
0
intelogent
Asked:
intelogent
  • 3
  • 3
  • 2
  • +2
3 Solutions
 
Malli BoppeCommented:
did you try last known good configuration.
0
 
bluetabCommented:
do you have automatic updates set to install on their own or did you install any device driver updates recently?  Is there any hardware plugged directly into the server (ie; printer, tape drive, USB drive)?  Unplug these and see if the problem continues.  
0
 
ajbrittonCommented:
Is there a file C:\DEBUGLOG.TXT. If so, please post the contents.

Check the event logs, specifically System and Application logs. Look for the red errors or yellow warnings that occur just prior to the reboots.

Is the server a terminal server? If so, maybe a user has tried to install something.

Have you added any printer drivers? These can sometimes cause problems.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
intelogentAuthor Commented:
Interesting thoughts....and i am not the Tech...which is usually found here... but i do like to learn..

it is a terminal server.. However, i do not think TS Users can install programs .. can they.. would it not have to be in " install mode "
"Check the event logs, specifically System and Application logs"    where are these logs visible...   I would like to check them.
we have installed new disk back up unit....         i guess if the above does not work i could disable the device....and pull the ribon cable
the server has restarted late a night when no one is printing... would that rule out a " printer driver"

Last night, my Tech updATED EVERY DRIVER  in the system.....
we will wait a deay or two to see it's effect...
0
 
jsonnenvzlaCommented:
search for ms debugging tool, then find in c:\ a folder called minidumps, which are small dumps after each irrgular reboot. Analyse this minidumps, and youll get clues of what's going wrong. I had a network card driver error which was corrected once the new driver was installed. If the server is still in the warranty period, you could call their 800- and send them the minidump. They'll analise it for you.
0
 
Malli BoppeCommented:
To go log CLICK start  CLICK RUn and type eventvwr and click okay. That should show the event viewer which would have application and system log.
0
 
intelogentAuthor Commented:
thanks mboppe,

I now found the event viewer... and the logs... They do show red and yellow..
I see the certain things... like printer driver errors.. but they do not make sense....

for instance....

Event Type:      Error
Event Source:      TermServDevices
Event Category:      None
Event ID:      1111
Date:            8/13/2007
Time:            7:15:32 AM
User:            N/A
Computer:      HICKSVILLE
Description:
Driver HP Deskjet 6800 Series required for printer HP Deskjet 6800 Series is unknown. Contact the administrator to install the driver before you log in again.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 12 0d 00 00   ........

what does this tell you..surely, i use the printer all day long.

any help appreciated
0
 
ajbrittonCommented:
That looks like a user connecting from a workstation that has a local HP Deskjet 6800. The MSTSC client attempts to connect the terminal server session to the local printer at the workstation, but cannot find a printer driver for it. I would not expect this to cause server reboots. Do those entries coincide with reboots?

Did you look for the C:\DEBUGLOG.TXT file?
0
 
intelogentAuthor Commented:
I have alerted every on  the server... terminal and local users to e mail every time there is a restart...so that should help us pinpoint......
i can not find that file.....
also, jsonnenvzla:   suggest i view the minidump... but that too.. i cannot find.
i did a search on "my computer"
should i not be able to find both...?
0
 
ajbrittonCommented:
Do not trust the Explorer search function. You may also need to tweak the Explorer settings so that you are able to see hidden and system files...

1 - From any Explorer window (eg My Computer), open the Tools menu and select Folder Options
2 - Select the View tab and then make sure the following options are selected;
  - Select: Show hidden files & folders
  - Untick: Hide extensions for known filetypes
  - Untick: Hide protected operating system files

You should now be able to locate the C:\DEBUGLOG.TXT file (if it exists) or the minidumps.

It is quite easy to find out when a server has been restarted. Look in the System log for entries from the 'eventlog' source with event number 6009. This event is always logged at server boot up.

You can 'filter' the event log so that only particular events are displayed if you like...

1 - In the Event Viewer, right click on the System entry in the left hand pane and click on Properties
2 - Select the Filter tab
3 - Open the Event Source drop down list and select the event you are interested in (eg 'eventlog')
4 - In the Event ID box, type an event ID number (eg 6009)
5 - Click OK. All the events which match the filter will be displayed

To clear the filter, either go back to the Filter tab, click Restore Defaults then OK, or, close and re-open the event viewer.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now