shutdown because of EULA violation

My server (2003 SBS) is shutting down and I'm getting this message in my
event logs:

Source: SBCore
Category: None
Event ID: 1001
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.

If I follow the path, I get a 'no information is available' message.


Here's what precipitated this; I installed 2003SBS from my MCSA pack when it
was released. Later we upgraded the server motherboard and reinstalled on a
larger drive. No problems activating either time. Last week that
motherboard died, and I reinstalled the original motherboard and it's drive.
Now I get the shutdowns. I can't find anything about this situation
anywhere; I'm thinking the hardware profile doesn't match the recorded
profile, and I need to re-activate my current configuration. Is this
correct? I actually tried by changing the OOBETimer registry entry in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents
ala XP, but that has no effect.

What do I do to avoid another complete install ???

Ric,

BAsed upon what you describe, the short summary would be that you have had a
disaster recovery and changed hardware, and now are experiencing forced
shutdowns.

When you have a proper licensing condition, your only option is to contact
MS support. You should be able to get this resolved as non-fee call, though
they likely would require you to provide a credit card to get into the queue
then reverse the charge.

- Jeff Middleton SBS-MVP
YCST@SBSmigration.com


"Ric Stone" <spam@msn.com> wrote in message
news:krfCf.2960$Vr.2021@tornado.texas.rr.com...
> My server (2003 SBS) is shutting down and I'm getting this message in my
> event logs:
>
> Source: SBCore
> Category: None
> Event ID: 1001
> 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.
>
> If I follow the path, I get a 'no information is available' message.
>
>
> Here's what precipitated this; I installed 2003SBS from my MCSA pack when
it
> was released. Later we upgraded the server motherboard and reinstalled on
a
> larger drive. No problems activating either time. Last week that
> motherboard died, and I reinstalled the original motherboard and it's
drive.
> Now I get the shutdowns. I can't find anything about this situation
> anywhere; I'm thinking the hardware profile doesn't match the recorded
> profile, and I need to re-activate my current configuration. Is this
> correct? I actually tried by changing the OOBETimer registry entry in
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WPAEvents
> ala XP, but that has no effect.
>
> What do I do to avoid another complete install ???
>
>