EventIDs are not very informative if you don't give us the Source
of the events as well. Now I've done a lot of guessing, so this
might be completely off.
7024 is almost certainly this one:
Event ID: 7204
Source: Service Control Manager
Description: The <service name> service terminated with service-
specific error <error number>.
This event in itself is very general, you have to post the name of
the service and the service-specific error number if you want an
explanation.
I think I can guess 1106 and 1111, which are very common on a TS
and printer related:
Event ID: 1111
Source: TermServDevices
Description: Driver drivername required for printer printertype is
unknown. Contact the administrator to install the driver before you
log in again.
Event ID: 1106
Source: TermServDevices
Description: The printer could not be installed.
29 can be a lot of things as well, ranging from diskkeeper and dmio
(hard disk failure), N100 (network adapter failure), WLBS (cluster
has convergenced), W32Time (time server), etc.
But if we assume that 1111 and 1106 come from the print subsystem,
then 29 might have Source: Print
Event ID: 29
Source: Print
Description: Failed to delete PrintQueue CN=DMR-PS002-DMR-PRCO0012
at <print server>/CN=DMR-
PS002,OU=Computers,OU=DMR,DC=exec,DC=ds,DC=state,DC=ct,DC=us. Error
<error code>.
It almost seems that a connection is made to the TS, printer
redirection fails because the printer is unknown, then a service
crashes (the printer spooler service, presumably) and it crashes
the whole server. Not uncommon if you install 3th party printer
drivers on a TS (have you?).
What does *not* seem to fit into this theory is the fact that this
happens every night, unless you have a scheduled print job at that
time.
I would suggest that you do this:
1) tell us more about the circumstances. Every night, at *exactly
the same time* ??? If so, find out what is happening at that time.
A scheduled backup job? Are you sure that there is not simply a
reboot scheduled at that time? Not unusual on a TS.
2) note the Source of each EventID, as well as the description with
all the details. Post them here, or look them up yourself at
http://www.eventid.net/
3) configure your server to *not* automatically reboot when a fatal
(STOP) error occurs. The next time the server crashes, it will stop
at the Blue Screen of Death. Write down the STOP error code, the
parameters of the STOP error and the driver information (all on the
first four lines of the screen). Post that information here, or
look it up yourself at the MSDN Bug Check Codes page at
http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/ddtools/hh/ddtools/bcintro_f55acfed-3296-4e84-8885-
c3162fd0ddbf.xml.asp
