Re: install SBS2003 Trial - Update, reboot = "Expired"

BTW, can someone tell me, DID it present the date to me ?
I only remember the time zone. Although it took all day so I was inserting a CD - returning an hour later - next Cd etc. Maybe I just didn't notice

I started reinstall - it DOES show the date/time zone - apparently I only checked the Time Zone - so it was my stupid mistake.

Bobb


"- Bobb -" <bobb@xxxxxxxxxxxx> wrote in message news:ObsO3HzfGHA.356@xxxxxxxxxxxxxxxxxxxxxxx

"Steven Zhu [MSFT]" <v-stezhu@xxxxxxxxxxxxxxxxxxxx> wrote in message news:Gyr$1BwfGHA.2260@xxxxxxxxxxxxxxxxxxxxxxxx
Hi Bob,

Thanks for posting here.

From your post, my understanding on this issue is: you get the "Your trial
period has expired please purchase a full copy license" error message when
you install Windows SBS 2003, and you get the blue screen after you reboot
the server. If I am off base, please feel free to let me know.

========
Steven,

I think that my problem is a date / "activation period " issue. According to the logfiles, I tarted install on 7/23 and after windowsupdate date was 5/23. My guess is that the program that tracks 14 days for activation got triggered. If there's a way around that so that I CAN activate, I think I'd be golden. But it looks like the mousetrap has already been sprung.
Here's the step-by-step if needed:

I got the error message only after updating ( there were 28 KB's that I installed). Install went fine until Cd #6. I then got an error that it couldn't read/find a file on CD. It asked - skip file? After reseating the CD and still error, I said yes and it looked as if the process finished normally and that there were 2 things that needed doing - setup network and ... something else. I clicked on setup network. did so and then after a reboot I got to a login screen - saw the To do list and I shutdown and rebooted twice - just to see if all was OK with that error message. Looked good so then I started the "To Do " list as part of the install process.

Got to step #2 of the "To Do List" which was" Setup network" . I did so. It then recommended that I update - I did. After the windowsupdate, the install recommended a reboot - I did. It was then that I got the "Your trial period has expired please purchase a full copy license" message. The screen then went black ( that looked 'normal' as if SBS was about to shutdown). THEN I got the blue screen - not a complete register dump - just an error code - then it did restart. That blue screen was only for ~1 second. Then it went away then black again - THEN the reboot. I interpreted the blue screen message as meaning - "your trial has expired". After reboot it looks fine. I login, then I get the 'expired' message - fade to black - blue screen - reboot. So the BSOD is only AFTER it tells me that license has expired. Prior to windowsupdate, it was fine.By booting my XP drive and checking the SBS logs I then saw that the install date was 7/23 for all but the system folders. ( not 5/23 as it should be) So I then figured that what must have happened was:
I plugged in the PC ( an old PC that I haven't plugged in for about a year) and did the install. I don't think that the install ever asked me the date - just the time zone. So I'm guessing that the date in the BIOS was wrong and connecting to windowsupdate corrected it ( this is a total guess - would the site correct the date on the PC ?). So the start of the install was 7/23/2006 and after the updates and a reboot the date was then 5/23/2006 and it triggered something in the activation period program. It now thinks that it's been more than 14 days to register, so the " license activation bit" has been set and it won't let me login.

If I could fix THAT, then the OS is fine ( at least it was prior to windowsupdate).
Next time I'll check the date in BIOS. BTW, can someone tell me, DID it present the date to me ? I only remember the time zone. Although it took all day so I was inserting a CD - returning an hour later - next Cd etc. Maybe I just didn't notice

Bobb

===========

Based on your description, I suggest you reinstall the system and if you
still receives blue screen, please follow the steps below to check whether
this is a BSoD (Blue Screen of Death) issue.

1. Right click My Computer and click Properties.
2. Click Advanced tab and click Settings under "Startup and Recovery".
3. Make sure that the "Write debugging information" has been set as
"Complete memory dump". And the dump file will be saved as
"%SystemRoot%\MEMORY.DMP".

After the problem occurs again, please open C:\Windows folder and check
whether the memory.dmp file exists.

If this is a blue screen issue, it is too complex to troubleshoot it in the
newsgroup. At this point, you have to contact our PSS support for debugging.

A suggestion would be to contact Microsoft Product Support Services via
telephone so that a dedicated Support Professional can assist with your
request. Please be advised that contacting phone support will be a charged
call. To obtain the phone numbers for specific technology request please
take a look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

I'd like to provide you with more info for your reference.

STOP message checklist:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/
ddtools/BCIntro_f55acfed-3296-4e84-8885-c3162fd0ddbf.xml.asp

Although we cannot provide debugging support via newsgroups, if you're
interested in troubleshoot the problem by yourself, you can also refer to
the following info and tools.

Debugging Tools for Windows - Overview
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx

What's New for Debugging Tools for Windows
http://www.microsoft.com/whdc/devtools/debugging/whatsnew.mspx

Install Debugging Tools for Windows 32-bit Version
http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.3.17.0.exe

Download Windows Symbol Packages
http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx
http://msdl.microsoft.com/download/symbols/packages/windowsxp/WindowsXP-KB83
5935-SP2-slp-Symbols.exe

I hope the above information helps.

Have a nice day.

Best Regards,

Steven Zhu
MCSE
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD were
updated on February 14, 2006.? Please complete a re-registration process
by entering the secure code mmpng06 when prompted. Once you have
entered the secure code mmpng06, you will be able to update your profile
and access the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================









.

Relevant Pages

  • RE: Help! Startup automatically reboots halfway through
    ... Insert the Windows XP startup disk into the floppy disk drive, ... If this does not fix your issue I suggest that you do a parallel install ... rename the system folder to something besides windows or winnt. ... Once you are done you can try and reboot ...
    (microsoft.public.win2000.setup_deployment)
  • RE: Help!SOS!Hardest Senario-Cant start up!-computer reboots halfway through setup
    ... Insert the Windows XP startup disk into the floppy disk drive, ... If this does not fix your issue I suggest that you do a parallel install ... rename the system folder to something besides windows or winnt. ... Once you are done you can try and reboot ...
    (microsoft.public.win2000.setup)
  • Re: Since installing AD, server reboots every 2-3 days
    ... Windows Debugging Tools and take a look. ... what is causing the reboot. ... sense that the Repair install would have fixed the problem. ... Blue screens? ...
    (microsoft.public.win2000.active_directory)
  • Re: SP2 what a bunch of @#$!!!
    ... I installed SP 2 but lost network connectivity as a result, ... so i forced a hardware reboot. ... My last resort was a repair re-install of windows SP-1 from the original CD. ... end of the install after it had written a lot of stuff to the disk. ...
    (microsoft.public.vstudio.development)
  • Re: install SBS2003 Trial - Update, reboot = "Expired"
    ... I tarted install on 7/23 and after windowsupdate date was 5/23. ... I got the error message only after updating. ... did so and then after a reboot I got to a login screen - saw the To do list and I shutdown and rebooted twice - just to see if all was OK with that error message. ... Debugging Tools for Windows - Overview ...
    (microsoft.public.windows.server.sbs)