From: "Geo." 

It's possible but that one looks more like a local machine error to me but
since it has to do with login information it is possible an unreachable PDC
could cause it.

Geo.

"Ellen K"  wrote in message
news:809906.fda913{at}harborwebs.com...
> Thanks.   :)
>
> Yes, the same network connectivity problems I previously posted about.
>
> Would an "unreachable domain controller" also cause the
problem that happened
> last night (the first one listed in the post)?
>
> Does the fact that we are on NDS (not AD) make any difference?
>
> > From: "Geo." 
> > "Ellen K."  wrote in message
> > news:fn8ig0l7vlpdluhhka2378fbq7q1nm1ug8{at}4ax.com...
> >> "C:\WINNT\system32\w3ctrs.dll" for the 
"W3SVC" service does not match
> >> the trusted performance library information  stored in the
registry. The
> >> functions in this library will not be treated  as trusted.
> > That's an IIS error of some sort.
> >> The job failed.  Unable to determine if the owner
(CORRECT_DOMAIN\ellen)
> >> of job RecordingsNightlyMaintenance has server access
(reason: Could not
> >> obtain information about Windows NT group/user 'CORRECT_DOMAIN\ellen'.
> >> [SQLSTATE 42000] (Error 8198)).
> > This looks like it might be a domain controller unreachable error. Are you
> > having any network connectivity problems, are backups running that might be
> > making it impossible to talk to the domain controllers?
> > Geo.

--- BBBS/NT v4.01 Flag-5