2003 Server won't shut down or restart 1

[Adams999]

When I try to restart the server it hangs on "Server is shutting down" screen. I eventually push the restart button (the longest I've waited is 30 minutes). After startup, the app log shows the following errors:

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 11/19/2003
Time: 12:54:37 PM
User: N/A
Computer: SOLUTIONS
Description:
LDAP Bind was unsuccessful on directory SOLUTIONS.tsgroup.solutionsbiz.com for distinguished name ''. Directory returned error:[0x34] Unavailable.

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 11/19/2003
Time: 12:54:38 PM
User: N/A
Computer: SOLUTIONS
Description:
Process MAD.EXE (PID=3152). All Domain Controller Servers in use are not responding:
SOLUTIONS.tsgroup.solutionsbiz.com

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 11/19/2003
Time: 12:54:43 PM
User: N/A
Computer: SOLUTIONS
Description:
LDAP Bind was unsuccessful on directory SOLUTIONS.tsgroup.solutionsbiz.com for distinguished name ''. Directory returned error:[0x51] Server Down.

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 11/19/2003
Time: 12:54:44 PM
User: N/A
Computer: SOLUTIONS
Description:
The Win32 API call 'DsGetDCNameW' returned error code [0x862] The specified component could not be found in the configuration information. The service could not be initialized. Make sure that the operating system was installed properly.

 

[ctsolutionsbiz]

I wish I had a solution, instead of just the same problem. But maybe sharing information can help us eliminate factors that our configurations don't have in common...Is yours acting as both DC and Exchange server? Is it the only server in your forest? Are you using Exchange 2003? Is your server a Dell and if so, did you use the Dell Openmanage installation routine? Is your functional level set so as to allow pre-windows-2000 systems access? I would have to say yes to all. Anything I can rule out?

 

[jepoybato]

With the same idea as ctsolutionsbiz, I do not have a solution but am seeing the same issue that I am currently still troubleshooting.

Mine is Win2K3, with Exchange 2K3 and is both a DC and Exchange Server, along with being the only server in the forest (for now). Mine is not a Dell, it is a Compaq DL380 with a RAID Array (Raid 1).

From MS's site, they recommend the following for general Win2K3 issues shutting down that I am still working through:

http://support.microsoft.com/default.aspx?scid=kb;en-us;324268&Product=winsvr2003

I am also enabling Verbose Startup and Shutdown in the hopes of finding the solution:

http://support.microsoft.com/default.aspx?scid=kb;en-us;325376&Product=winsvr2003

So far, these are the suspect drivers that I am going through:
Microsoft (R) Windows (R) Version 5.2 (Build 3790)
1 2 2004 14:43:04.375
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\i2omgmt.SYS
Did not load driver \SystemRoot\system32\DRIVERS\imapi.sys
Did not load driver \SystemRoot\system32\DRIVERS\mrxsmb.sys
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\system32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver ACPI Multiprocessor PC
Did not load driver ATI Technologies Inc. 3D RAGE IIC PCI
Did not load driver Audio Codecs
Did not load driver Communications Port
Did not load driver Fips.SYS
Did not load driver Intel PentiumIII Processor
Did not load driver Legacy Audio Drivers
Did not load driver Legacy Video Capture Devices
Did not load driver Media Control Devices
Did not load driver mnmdd.SYS
Did not load driver Printer Port
Did not load driver Serial.SYS
Did not load driver Video Codecs
Did not load driver Wanarp.SYS

Sorry for not having a solution but hopefully the more info, the more clear a possible solution can be...

- Jepoy

=======================================
Know Thyself...
=======================================

 

[csutton]

Anyone have any updates for fixes for this? Our server is home built, but very quick processor, etc. We were able to shutdown fine until we installed Exchange Server 2003. Since then, it has been taking forever to shutdown, and we generally hit the power button to restart.

Thanks

 

[Adams999]

My configurstion is identical to what ctsolutionsbiz describes. I appreciate hearing from all of you. It sounds like this problem is fairly widespread.

 

[karmic]

Is this a small business server? or a member server running exchange?

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[Adams999]

Windows Server 2003 Standard running Exhchange 2003, not Small Business Server.

 

[Steve Bowman]

This has always been an issue with rebooting Shutdown/Restart on server as PDC with/Exchange Installed and on some Standalone with/Exchange Installed.

This is not just a 2003 issue I have seen it on NT4

As an experement use Control->Admin->Services to first stop all exchange services then shutdown/restart the server. In most cases the shutdown will work.

I do not like my solution but what I do is write a "reboot.cmd" file and use NET STOP bla bla and stop all exchange services then as last line shutdown /l /y /c /r /t:2 and I use the cmd file to reboot the server instead of the Start->Shutdown.

Additionaly you can add the cmd to scheduler and automate regular shutdowns

Steve Bowman
steve.bowman@ultraex.com

 

[PHPHT]

I used the batch file with the shutdown command. Worked like a charm! It's 2004... Shouldnt there be a patch for this by now?

 

[smurfsrus]

I have the same problem although the average shutdown time is about 15 minutes for me. I found the microsoft article q322837 about having these problems after you install SP2 or 3 for exchange 2000. They say that it is safe to ignore so I am wondering whether this is an issue that they have ignored going to Exchange 2003. More than likely that is the case and hopefully a patch or new SP will solve the issue someday.

 

[jferrante]

I have the same problem using Small Business Server 2003. I've tried stopping just about every service I could think of, and still does not shut down.

Server hardware is an Intel 875 server board with SATA hard drives.

So it doesn't seem like an isolated problem or specific to 2000, 2003 or Exchange 2000/2003.

 

[Adams999]

Stopping the Exchange services produced a clean shutdown. Thanks!

 

[smurfsrus]

Found a Microsoft article that explains what is going on. Check out 555025. The solution is what SteveB7 suggested. Notice the disclaimer for this solution though. Gotta love Microsoft.

 

[mansnes]

The errors 2104, 2102, and 8250 upon startup are all caused because Exchange Management Svc hasn't been fully brought up when other components start calling funcitons it provides. These messages can be ignored. See MSKB 322837.

But the stalled shutdown is a problem with Exchange on a Domain Controller. During the shutdown process, the directory services used by Exchange are stopped before the Exchange services that try to access them. It's all a timing issue.

To prevent the stall, as stated above, you need to shut down the Exchange services before shutting down the system. To make it easier, you can use the below script to initiate the shutdown or restart (copy and paste to a batch file). It will terminate the Exchange services (and some additional services in the background) before shutting down the system. Note that if you abort it after it has run, you'll have to manually restart the stopped services.

-----------------------
@ECHO OFF
ECHO 0. CANCEL
ECHO 1. SHUTDOWN
ECHO 2. REBOOT
ECHO.
CHOICE /C 012

IF ERRORLEVEL 2 GOTO REBOOT
IF ERRORLEVEL 1 GOTO SHUTDOWN
IF ERRORLEVEL 0 GOTO END
GOTO END

:REBOOT
SET PARAM=/r
GOTO STOPSERVICES

:SHUTDOWN
SET PARAM=/s
GOTO STOPSERVICES

:STOPSERVICES
ECHO ON
REM .....CLOSING IIS AND DEPENDENT SERVICES IN BACKGROUND.
START /MIN NET STOP IISADMIN /YES
REM .....STOPPING EXCHANGE PRIMARY SERVICES
NET STOP MSEXCHANGEES /YES
NET STOP MSEXCHANGEIS /YES
NET STOP MSEXCHANGEMTA /YES
NET STOP MSEXCHANGESA /YES
shutdown %PARAM% /t 30

REM SERVER GOING DOWN IN 30 SECONDS,
REM TO ABORT, USE:
REM
REM SHUTDOWN /A

:END

-------------------------------





-Michael Ansnes, MCSA, MCSE,
Systems Architect,
Network Synergy Solutions.