Re: SBCore shutdown event 1012

Marina,

The DNS callouts are not listed as failures. What drew my attention to them
is the statement " this usually means there is more that one domain
controller" which is what is causing the SBCore event 1012 and shutdowns.
Looking back in my event log, I've been getting the event 1011 SBcore
"multiple SBS2003 domain controller" callouts since the 13th, which would
seem to explain the system shutdown on the 27th as the end of a two week
grace period. The problem is there were no configuration changes around the
13th that would have caused the problem to pop up.

More information on the DNS callouts in Netdiag. The DNS server is listing
two IP addresses for the server, which is accurate because it is a
multi-homed machine, one is connected to internet 10.XXX.XXX.XXX, and the
other for the local subnet 192.XXX.XXX.XXX. Would SBCore interpet the two IP
addresses for the DC as being two separate Domain Controllers?

I spent most of this evening restoring the server from backup to reset the
system to prior to the 27th, after that I found the SBcore callouts back to
the 13th, so I'm not sure the restore process fixed the problem. I am
considering restoring the system back to my oldest backup, the 11th of August.

The SBCore Event 1011 "multiple SBS 2003 domain controllers" callout did
only occur 4 times between the 13 and the 27th with no obvious pattern.

Would it helped if I emailed the netdiag.txt and dcdiag.txt files?

Thank you so much for your help,

Jonathan

.

Loading