SERVER KEEPS SHUTTING DOWN (SBCORE)

PROBLEM: In the Small Business server one problem can give you hard time which is shutdown automatically. There may be many reasons for that but two error that I found in the event log, they are as follows-

ERROR TYPE # 1

• Event Type: Error
• Event Source: SBCore
• Event Category: None
• Event ID: 1001
• Date: 3/1/2007
• Time: 02:49:31
• User: N/A
• Computer: SERVER
• Description: The server was shut down because it did not comply with the EULA. For more information, contact Microsoft. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

ERROR TYPE # 2

• Event Type: Error
• Event Source: SBCore
• Event Category: None
• Event ID: 1014
• Date: 3/1/2007
• Time: 02:19:31
• User: N/A
• Computer: SERVER
• Description: This computer must be configured as a domain controller. It will be shut down in 30 minutes. To prevent this computer from shutting down, run Setup on the disk that you used to install the operating system to configure the computer as a domain controller. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

CAUSE (which I found in micosoft web site): This issue can occur if the Windows 2003 Small Business Server integrated setup was not completed. Windows 2003 Small Business Server must be a domain controller and hold all FSMO roles for the domain. In order to facilitate migration from an existing domain, the Small Business Server can function for 7 days after installing without being promoted to a domain controller. After that time, the Small Business Server must be promoted to a domain controller using the integrated setup. If the integrated setup is not completed, the SBCore service will initiate a shut down of the server.

SOLUTION # 1

To resolve this issue, complete the Windows 2003 Small Business Server integrated setup. To access integrated setup, select "Windows Small Business Server 2003" in the Add/Remove Programs applet in the Control Panel.

SOLUTION # 2

• Download tools from http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx
• Run regedit and expand the nodes until you reach the following hive / key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SBCore
• Right click this, hit permissions and give the "Administrators" group on the local machine full access ( don't forget to replace permissions on child nodes ). F5 in regedit and you'll see all of the values and data under this key.
• Select the "Start" DWORD and change it from 2 to 4 – this basically sets the service to the "Disabled" state as far as the MMC services snap-in (and windows for that matter) is concerned.
• Next, adjust the permissions on the file C:\WINDOWS\system32\sbscrexe.exe so that EVERYONE account is denied any sort of access to this file.
• Then open process explorer, and kill the sbscrexe.exe process, if it doesn't restart – congratulations!
• Load up the services MMC snap-in and you should find that "SBS Core Services" is stopped and marked as Disabled.