SBS sends me a weekly list of errors which it has picked out from the various Event Logs.
It's pretty obvious what I need to do about this one, isn't it!
Microsoft-Windows-Diagnosis-DPS 170 11/12/2010 13:34:07 3
Event Details:
Diagnostic module {C0F51D84-11B9-4E74-B083-99F11BA2DB0A} (%windir%\system32\radardt.dll) encountered an error while handling scenario {739FF6CF-5033-428C-9E2F-582096482DD5}, instance {3D3D36F9-600D-4A27-8234-2ED0BD33341B}, original activity ID {00000000-0000-0000-0000-000000000000}. The error code was -2147023888.
The straightforwardness of error messages
-
John Gray
- PlatinumLounger
- Posts: 5408
- Joined: 24 Jan 2010, 08:33
- Location: A cathedral city in England
The straightforwardness of error messages
John Gray
"(or one of the team)" - how your appointment letter indicates you won't be seeing the Consultant...
"(or one of the team)" - how your appointment letter indicates you won't be seeing the Consultant...
-
Claude
- cheese lizard
- Posts: 6241
- Joined: 16 Jan 2010, 00:14
- Location: Sydney Australia
Re: The straightforwardness of error messages
That's an easy one! There was no activity on your network so it shut itself downJohn Gray wrote: original activity ID {00000000-0000-0000-0000-000000000000}
Cheers, Claude.