Re: Shutdown hangs...

Nathan, thanks for the reply. As for my reboot time, it is still taking
approx. 10 minutes from the time I click restart until the server will
actually reboot. Basically I click shutdown or restart, it'll start the
shutdown script I wrote based on advice from Merv, then it says Windows is
shutting down and then it sits a grey screen for about 7-8 minutes and then
performs the reboot. Prior to my updating the antivirus software I never had
the issue. A reboot would take a total of 7-8 minutes, shutting, restarting
and being able to log in. Now it takes approx. 15 minutes until I am able to
get to the login screen after I send the reboot command.
Additionally, the server is still dropping the CAL's and its on the reboot,
not on a virus scan. So as of right now I have no idea what my server is
doing on a reboot command or why it is taking so long to perform it or why it
is dropping the CAL's after a reboot. My thoughts are still gearing towards
a swing so I know for sure that I'll a clean install, but I'd like to try and
figure out why its acting the way it is too.
FYI - here's the script I wrote that runs on a shutdown command:
REM script to stop MSExchangeSA on reboot
net stop msexchangesa /y /y
net stop "Microsoft Exchange Routing Engine"

Any other ideas at all? Thanks again.

"Nathan Liu [MSFT]" wrote:

> Hello Ken,
>
> Thank you for your update.
>
> Also, many thanks for Dave and Merv's great input.
>
> According to your description, I understand that the SBS 2003 Server
> shutdown speed is quick a bit after you installed the UPHclenaup software,
> but you have a another issue with SBS 2003 Licenses. If I have
> misunderstood your concern, please don't hesitate to let me know.
>
> To troubleshoot this issue, please help me perform the following steps:
>
> 1. As Merv mentioned, please try to configure your AV software exclude the
> license folder from scan. Since you have do this at yesterday, please try
> again. Please test if the issue be re-produced.
>
> 2. If the issue persists, please try the solution in the KB article 888818.
>
> 888818 The number of client access licenses may be reset to five in Windows
>
> http://support.microsoft.com/?id=888818
>
> 3. This issue will also occur if:
>
> - The license store is reset, and the license codes cannot be located, or
> if the license codes cannot be restored immediately.
> - An antivirus program deletes or quarantines the license store file. The
> license store file is located in the %systemdrive%\Windows\System32 folder.
> - Low memory or free disk space.
> - A Dll file is unregistered by accident.
>
> The license store file is backed up when product activation is completed,
> and the Restore License Wizard points to this file. If the Windows Small
> Business Server license service cannot locate the license store file, a new
> license store file is created. By default, this new license store file
> contains five CALs that are included with Windows Small Business Server
> 2003. See the antivirus program documentation, and make sure that .cpa,
> .cpl and .lls files have not been scanned, moved or deleted.
>
> 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 Small Business Server license
> service behaves as if it has been modified and resets the license store to
> the default of five CALs.
>
> 4. This issue may also occur if the Licdll.dll or Regwizc.dll files are not
> registered. We have determined that some antiSpy program will un-register
> these windows file and cause the issue. You can re-register the files as I
> suggested in the first response. I would like to include the steps as
> following:
>
> a. Click "Start", click "Run".
> b. Type "regsvr32 c:\windows\system32\licdll.dll" (without the
> quotation marks), and then click "OK".
>
> Note: You must close and reopen the Server Management console after you run
> this command.
>
> Please do perform the steps above and then check if the issue is resolved.
>
> I'm looking forward to your update. If you have any questions or concerns,
> please do not hesitate to let me know. I am always happy to be of further
> assistance.
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.

.

Relevant Pages

  • Re: Shutdown hangs...
    ... Server shutdown operation is very slow and the SBS 2003 CAL Licenses ... >> license folder from scan. ... >> - An antivirus program deletes or quarantines the license store file. ...
    (microsoft.public.windows.server.sbs)
  • Re: ASP Error HTTP-500 "The Requested Resource is in Use" SBS2003
    ... I understand that the SBS 2003 Server ... license folder from scan. ... - An antivirus program deletes or quarantines the license store file. ...
    (microsoft.public.windows.server.sbs)
  • Re: Shutdown hangs...
    ... I understand that the SBS 2003 Server ... license folder from scan. ... - An antivirus program deletes or quarantines the license store file. ... >Subject: Re: Shutdown hangs... ...
    (microsoft.public.windows.server.sbs)
  • Re: Error Code 8: 0x8007000e Windows Product Activation
    ... Error occurred while wizard was checking the current windows product ... This server has been going strong for 4 years, ... because it can't check the product license. ... one way or the other whether I should just reboot? ...
    (microsoft.public.windows.server.general)
  • Re: User cannot connect to Win2003 TS - Temporary License Expired
    ... I run my TS license server 24/7 with device licenses and never have a problem. ... You shouldn't have to reboot to make it work. ... I noticed this morning that the restart's had not been happening for a week or so and it was due to an expired service account password. ...
    (microsoft.public.windows.terminal_services)