Over the past two nights the File Server Machine has shut down, in the
machines event log the following Events are listed.
Event ID 1074
The process C:\Windows\system32\silsvc.exe (FILE-SERVER01) has initiated the
power off of computer FILE-SERVER01 on behalf of user NT AUTHORITY\SYSTEM for
the following reason: No title for this reason could be found
Reason Code: 0x2000c
Shutdown Type: power off
Comment: Licensing Compliance Service caused a shutdown. Please look at the
events under Microsoft > Windows > Server Infrastructure Licensing >
Operational for details.
Event ID 38
The Additional Server Count Check detected a condition in your environment
that is out of compliance with the licensing policy. This server will be
automatically shut down if the issue is not corrected in 179 day(s) 11
hour(s) 0 minute(s). Please look for additional events for Additional Server
Count Check to troubleshoot
The Additional Server Count Check in the Licensing component did not pass
because error 0x8007203a occurred in function f4 [KOAU].
The server is not operational.
Event 4
Make sure that your DNS server can be contacted and the following services
are running: Active Directory Domain Services (NTDS), DNS Server (DNS),
Kerberos Key Distribution Center (KDC). This server will be automatically
shut down if the issue is not corrected.
Has anyone had the same issues..?
Regards
It's my understanding that SBS 2008 licensing does not allow SBS to be
installed as just a file server - that you've been running it for any
amount of time is meaningless as MS updates security and licensing
functions frequently.
--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
spam9...@rrohio.com (remove 999 for proper email address)
I had the same problem. But it was with a SBS2003 and a SBS2008 server mix.
This mix is only a temporary setup as we are migrating from the SBS2003 to
the SBS2008.
Long story short is:- to stop the SBS2008 server from shutting itself down
you need to make it so it cant see the other SBS server. To do this you need
to either
1/ Put them on separate networks (or same network with different IP
range/subnet)
2/ Stop and Disable to following 2 services: 'Computer Browser' & 'Remote
procedure call (RPC) locator'. It is possible that only one of the two
services needs to be stopped but you would need to test this.
Hope this helps
DavidR.
Hi Matt,
Thanks for your post and others' input.
Based on the Event ID errors and experience, I would like provide the following suggestions for your refernece, hope it works.
Suggestion 1: Because the server doesn't comply with EULA. Probably, you have more than 1 SBS 2003 in the same network somehow, SBS 2003 is not detected as a DC. If this is
the situation, you may try David's advice.
Suggestion 2: This issue also might occur when the computer is low on memory or low on free disk space, some of the licensing checks that are performed by the Windows Small
Business Server license service will fail because the license check or the Active Directory directory service query to verify the credentials cannot be completed successfully.
In this scenario, the Windows SBS license service behaves as if it has been modified and resets the license store to the default of five CALs. Therefore, please go to Licensing
console to check your CALs and free up some space on the system drive if it's running out of space now.
Moreover, SBS BPA tool is good friend to detect the SBS server for potential problems. The Windows Small Business Server Best Practices Analyzer(BPA) examines a server that
is running Windows Small Business Server (Windows SBS) and presents a list of information and errors that administrators should review.
Please have a try and hope it works.
Sincerely,
Robbin Meng
Microsoft Online Newsgroup Support
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================