Link to home
Start Free TrialLog in
Avatar of JohnnyHeavens
JohnnyHeavens

asked on

System Event Log Error ID 1011 Source SBCORE

Event Log gives this:
Product: Windows Operating System
ID: 1011
Source: SBCore
Version: 5.2
Symbolic Name: EVENTLIC_MULTIPLE_SBS_DCS_WARNING
Message: Multiple domain controllers running Windows Server 2003 for Small Business Server have been detected in your domain. To prevent this computer from shutting down in the future, you must remove all but one of these from the domain.
detail to message
***end**
-There is NOT another SBS server
-Server shuts down about every one and a half hours and an hour after the above event is logged.

Any ideas?
Avatar of Lofty Worm
Lofty Worm
Flag of United States of America image

I ran into this before, but when I did, it was after adding the SBS to a real domain.  In SBS, it can be the only domain controller, so what other servers do you have in your domain?  I suspect that because it is SBS, that you have lots of restrictions on what can be in the domain.
Avatar of JohnnyHeavens
JohnnyHeavens

ASKER

Fair question but the one other "server" but it only serving file shares and this issue was happening before the other server was introduced.
The lay out includes 5 total machines. One SBS server, Three XP machines, and one other server here just so files are available during reboots as this is a Tax shop and as you all know...it's tax time.

Any other ideas? DNS seems to be configured correctly now. (I fixed that) Everything resolves OK.
ASKER CERTIFIED SOLUTION
Avatar of Lofty Worm
Lofty Worm
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
There is a grace period of 7 days when connecting sbs to another domain for migrations. this can be extended to 21 days with update 943494.

You would not have any problems with multiple domain controllers during this period.

Are you sure you dont have 2 domain controllers.
frederikgovaert-A fair question and yes. I'm positive there are not more then one DC. I even started dcpromo on the file server I mention above just to make sure. I scanned the whole subnet-besides, there are only 6 cables going into the switch and all are accounted for. I understand the disbelief tho. :) Even google only finds two results for the error "EVENTLIC_MULTIPLE_SBS_DCS_WARNING" and one is here on EE but totally un-helpful.

Alright, here is an update after poking around some more. The sbs server seems to be a bit jacked up to say the least. None of the snap-ins AD management work. It seems they can't connect to the domain. or even to localhost. loftyworm, you maybe on to something. I talked more to the client and it seems that they use some tax software that was giving them some trouble. TaxWise I believe it was. Part of what the taxwise guys had them do to troubleshoot an update is remove the software and then re-install. It was after this that the server started having trouble. No idea what it could have been or if it is simply a coincidence. Any more thoughts?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
And can you check if all the five FSMO roles are assigned to the SBS server ?

I suspect that the tax software guys did not finish the SBS installation completely.


How to view and transfer FSMO roles in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324801
Hello experts,

I'm experiencing the exact same issue on a Windows 2003 SBS. It is the only server in a small network of aprox. 15 machines. All the rest of the machines are either Windows VIsta or XP. The customer contacted us to fix a problem on the server (some memory error). After determining that the Windows copy was corrupted, we decided to run repair. That didn't solve the problem, so we proceeded to install a fresh copy on Windows 2003 SBS in the machine (leaving also the old corrupted copy in the hard drive). Both copies co-existed ok for about a week. Then the client called us back reporting that the server was rebooting every couple of hours. After checking the Event Log, we saw error 1011 showing up "Multile domain controllers and the whole yada yada", so we thought, it's probably detecting the old copy of Windows in the Hard drive. Maybe there was something left in the Registry. So, after surfing a little bit on the web without finding an easy solution, we decided to format the Hard drive and reinstalling Windows from scratch, that way we would make sure it was the only copy of Windows 2003 in the machine and the network. After reinstalling, everything was working great. Not a week has passed since then, but today I was checking the Event log and saw error 1011 poping up again! The server is not rebooting frequently yet, but it will start doing it on April 6th, when the 7 days grace period expires. I've exhausted everything I know. I really need expert help on this one!! I'm willing to coolaborate by any "virtual" means in order to nail this sucker!
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial