Terminal Server connectivity problems after reboot

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Hello,

on a english version Windows 2003 Server with MS Exchange 2003,
Domain Controller, we installed a trial version of Dovico time
mangement software. After installation the system suddenly
rebootet.

After this reboot no data (Exchnage, ADS, Profiles) was lost,
but many problems occour in the running system:

- No login to the terminal server is possible anymore. After waiting
the client reports "Remote Desktop Disconnected" even if the service runs.

- Network connection lost at "My network places". Even if the system
is working, the LAN symbol at the network places is missing

- At some of the running services (e.g. Terminal Services) it
is no more possibility to stop, start or restart them.

- At clicking on the dependencies of all services, the error message
"Win32: Not enough storage is available to complete this operation"
comes up.

- Eventlog shows several repeating erros all the time
e.g.
(Application)
Source: MSExchangeSA, Event ID: 9097
The MAD Monitoring thread was unable to connect to WMI, error '0x8007000e'.

- NTBackup failes as scheduled job. Eventlog claims bad Volume Shadow
Copy in Directory Service events:
Source: NTDS Backup, Event ID: 1912
"Attempts to backup or restore Active Directory using the shadow copy
service will not succeed until this is corrected.
Additional Data
Error value:
Not enough storage is available to complete this operation. 8007000e"

- DNS erros in Event log
Source: DNS, Event ID: 140
"The DNS server could not initialize the remote procedure call (RPC)
service. If it is not running, start the RPC service or reboot the
computer. The event data is the error code."

What could happened to the system? Is there any procedure to solve all
these things? Can so many problems occour if the system suddenly
reboots in running state?

I would be very grateful if you could send me your statements on.
Thanks in advance,

Michael