Thanks!
You'll find that all versions of Exchange (ok, not sure about v4) had
this effect on their host Windows. Where is does take a while to go
down you'll find that it comes back up in no time flat. Swings and
roundabouts.
Mark Arnold MCSA MCSE MVP, ma...@mvps.org
FAQ: http://www.swinc.com/resource/exchange.htm &
http:http://www.swinc.com/resource/e2kfaq.htm
I have same problem (looks like). My installation is on Compaq Proliant ML350 G3 server. Everything as you described. I tried to install W2K/E2K instead of W2003/E2003 and it works fine. But the error messages are the same as for E2003 MSExchangeDS MSExchangeAL (6 of them). I don't think it causing the problem. Currently i am trying W2K/E2003 combination. If i will succeed will email to you. But looks like it's not MSExchangeDS problem. Can be some services/agent run by hardware manufacturer.
Regards,
Alex
Check below response from Microsoft (it is normal). As i
email to you before i have same problem tried different
configuration (spend more than a week) W2000/E2000 works
fine W2003/E2003 shutdowns in 12 minutes.
Regards,
Alex
Subject: Re: Shutdown takes up to 12 minutes afetr
installation of E2003
From: "Melissa Travers [MSFT]"
<mtra...@online.microsoft.com> Sent: 10/21/2003 8:54:41
AM
Hi Alex,
If Exchange 2003 is installed on a DC, it may take a long
time for the
server to shutdown. This is because the AD service
(LSASS.EXE) shuts down
before the Exchange services, and DSAccess will go
through several timeouts
before shutting down. The workaround for this issue is to
manually stop the
Exchange services (specifically the Store) before
initiating a system
shutdown or restart. We are in the process of publishing
a KB article that
addresses this design change.
Hope this helps
--
Melissa Travers, MCSE
Microsoft Exchange Support
Please do not send email directly to this alias. This
alias is for newsgroup
purposes only.
This posting is provided "AS IS" with no warranties, and
confers no rights.
"Alex" <anon...@discussions.microsoft.com> wrote in
message
news:05e501c39769$200e3c70$a301...@phx.gbl...
> Hi everyone,
>
> Have the problem. Installed W2003 Standard on the new
> Compaq Proliant M350 G3 server. Installed DDNS. Promoted
> to be DC for the new domain. Run DCDIAG, NLTEST for
> testing DC in the new domain. Everything looks fine.
> Installed E2003 Standard using deployment guide (step by
> step forestprep, domainprep, setup). Now it takes up to
> 12 minutes to shutdown this server. In the log file
error
> messages "Can't locate DC or all are busy". Looks like
> have the problem with AD and Exchange. Any ideas what
can
> be wrong. Don't tell me it's normal 12 minutes to
> shutdown server. Microsfot recommends to have at least 2
> DC with for domain (i need only one). I used W2K/E2K
> without any problems in different sites before.
>
> Regards,
> Alex
.
>.
>
Thanks again for the information!
>..
>
>
>>-----Original Message-----
>>After installing Exchange 2003 Server on my Windows 2003
>>Server, shutdown of the PC now takes at least 10
>minutes.
>>Server shutdown was quick before install of Exchange
>2003
>>Server. If I shutdown the Exchange services before
>>shutdown. The shutdown process takes place as normal
>>(quick). It appears the slow shutdown may be related
>the
>>information store service. Anyone have any ideas or see
>>this in Exchange 2003 Server? What can fix this?
>>
>>Thanks!
>>
>>
>>.
>>
>.
>
net stop "Microsoft Exchange MTA Stacks"
net stop "Microsoft Exchange Information Store"
net stop "Microsoft Exchange System Attendant"
this causes this script to run automatically first at
shutdown, then the other services stop. The computer then
reboots normally.
>..
>
>
>>-----Original Message-----
>>After installing Exchange 2003 Server on my Windows 2003
>>Server, shutdown of the PC now takes at least 10
>minutes.
>>Server shutdown was quick before install of Exchange
>2003
>>Server. If I shutdown the Exchange services before
>>shutdown. The shutdown process takes place as normal
>>(quick). It appears the slow shutdown may be related
>the
>>information store service. Anyone have any ideas or see
>>this in Exchange 2003 Server? What can fix this?
>>
>>Thanks!
>>
>>
>>.
>>
>.
>