Re: Poweredge server powering down by itself using SBS 2003



Thanks so much for all of the assistance. I understand that if I do not set
up the server as a domain controller I will keep having the server power down
every 100 hours. I have asked my local computer installer to come by and
finalize the installation. They preferred that I did not setup the server
with a domain controller, I do not understand why, but, hopefully this will
solve the powering down issue.

Thanks

Manny

"NJS" wrote:

> Sounds like the SBS2003 setup hasn't been finished - there should be an icon
> on the desktop to run the setup, or else use the SBS CD 1.
>
> "Manny Chopra" <Manny Chopra@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:97C71C8A-19A1-4EF4-B968-747D7F478983@xxxxxxxxxxxxxxxx
> > Hi,
> >
> > I am new to the server world of computing, and recently purchased a new
> > Dell
> > server, Poweredge 1800 with Small business server 2003. The computer is
> > supposed to be on at all times, however, when we come into work in the
> > morning, it is usually powered down. After numerous conversations with
> > Dell
> > support, and some diagnostic testing, they concluded that it was a
> > software
> > issue. Here are the error messages - please help, or advise. we are
> > trying
> > to not run the computer as a domain controller.
> >
> > Thanks
> >
> > In reviewing the DSET log, I found the following references for which
> > there
> > are repeats for multiple days. The errors are being reported by the
> > operating
> > system to the event log:
> >
> > 5/9/2005 10:14:01 AM
> > SBCore 1001 DELLSERVER
> > The server was shut down because it did not comply with the EULA. For more
> > information, contact Microsoft.
> >
> > 5/9/2005 10:14:03 AM
> > USER32 1074 NT AUTHORITY\SYSTEM DELLSERVER The process sbscrexe.exe has
> > initiated the shutdown of computer DELLSERVER on behalf of user NT
> > AUTHORITY\SYSTEM for the following
> > reason: No title for this reason could be found Reason Code: 0x0 Shutdown
> > Type: shutdown Comment:
> >
> > 5/10/2005 4:10:43 PM SBCore 1013 N/A DELLSERVER This computer must be
> > configured as a domain controller. To prevent this computer from shutting
> > down in the future, run Setup on the disk that you used to install the
> > operating system to configure the computer as a domain controller.
> >
> >
> > Manny
> >
> >
>
>
>
.



Relevant Pages

  • Re: Client performance problem windows 2003 server...
    ... >Subject: Re: Client performance problem windows 2003 server... ... >Deploying Active Directory for Branch Office Environments ... >results from not having a domain controller in a particular site. ... incorrectly applied site coverage will be bad for clients ...
    (microsoft.public.windows.server.networking)
  • problems with domain controllers
    ... A brief description of my setup is necessary before I ask my question. ... This summer I set up a Terminal Server Farm that covers two buildings, ... far side of the wireless one of boxes is set up as a domain controller, ...
    (microsoft.public.windows.terminal_services)
  • Re: Client performance problem windows 2003 server...
    ... Testing server: Verkstadsgatan\VERKTYG ... Deploying Active Directory for Branch Office Environments ... results from not having a domain controller in a particular site. ... incorrectly applied site coverage will be bad for clients ...
    (microsoft.public.windows.server.networking)
  • RE: NTDS.dit file is currupt
    ... "microsoft" wrote:> We are currently facing a serious problem with one our client server. ... > After rebooting the machine in directory services restore mode, I had> followed the steps below; ntdsutil neither defrag Active Directory Database> nor repair. ... Restart the domain controller. ... Check the integrity of the Active Directory database. ...
    (microsoft.public.win2000.active_directory)
  • Re: Thoroughly confused SBS 2003 Server
    ... fact I first had SBS running on the box that now has the Server Enterprise ... A year ago or moe I put up the second server and made it a domain controller ... The replication generated an error: ...
    (microsoft.public.windows.server.sbs)