Windows / Exchange Hangs on Shutdown

  • Thread starter Thread starter Joseph Geretz
  • Start date Start date
J

Joseph Geretz

Currently, I'm running Exchange 2003 under Windows Server 2003. However, the
problem originally occurred when I upgraded to Exchange 2003 under Windows
Server 2000. (This was during the course of upgrading my server. I've since
completed the upgrade for both Exchange and Windows.)

Basically, Windows hangs on shutdown. Here are the final entries from the
eventlog. The first entry is a successful shutdown of SQL Server. As you can
see, shutdown was initiated at 8:16. Over the next 10 seconds or so, a whole
bunch of Exchange related failures are logged. Shutdown then simply hangs
and I need to perform a machine reset in order to re-boot. After restarting
I can see where the system hung because there's a large gap in eventlog
entries.

I've presented the shutdown eventlog entries below. If you can help me with
this, I'll be most grateful.

Thanks!

- Joe Geretz -

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/19/2003
Time: 8:16:01 PM
User: N/A
Computer: DIMENSION2
Description:
17147 : SQL Server terminating because of system shutdown.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 8/19/2003
Time: 8:16:03 PM
User: N/A
Computer: DIMENSION2
Description:
Process INETINFO.EXE (PID=1356). All the DS Servers in domain are not
responding.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:04 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 8/19/2003
Time: 8:16:05 PM
User: N/A
Computer: DIMENSION2
Description:
Process MAD.EXE (PID=2116). All Domain Controller Servers in use are not
responding:
dimension2.internal.fpsnow.com

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:06 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
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.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:08 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
lsass (460) The database engine stopped.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
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.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:10 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
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.
 
Digging a bit deeper...

I stopped ALL services manually (except for the handful which cannot be
stopped). Shutdown succeeds. OK, it seems that one of my services is hanging
on shutdown. But which one? I don't relish the prospect of using the trial
and error approach to shut down services one by one, rebooting each time. Is
there any way to generate a verbose log of shutdown activity so that I can
see what's going on during shutdown?

Thanks for your help!

- Joe Geretz -

Joseph Geretz said:
I don't think any of those events have anything to do with the hang. I
stopped all Exchange services manually via the Services console app, but the
system still hung on shutdown. How can I debug this?

Thanks,

- Joe Geretz -

Joseph Geretz said:
Currently, I'm running Exchange 2003 under Windows Server 2003. However, the
problem originally occurred when I upgraded to Exchange 2003 under Windows
Server 2000. (This was during the course of upgrading my server. I've since
completed the upgrade for both Exchange and Windows.)

Basically, Windows hangs on shutdown. Here are the final entries from the
eventlog. The first entry is a successful shutdown of SQL Server. As you can
see, shutdown was initiated at 8:16. Over the next 10 seconds or so, a whole
bunch of Exchange related failures are logged. Shutdown then simply hangs
and I need to perform a machine reset in order to re-boot. After restarting
I can see where the system hung because there's a large gap in eventlog
entries.

I've presented the shutdown eventlog entries below. If you can help me with
this, I'll be most grateful.

Thanks!

- Joe Geretz -

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/19/2003
Time: 8:16:01 PM
User: N/A
Computer: DIMENSION2
Description:
17147 : SQL Server terminating because of system shutdown.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 8/19/2003
Time: 8:16:03 PM
User: N/A
Computer: DIMENSION2
Description:
Process INETINFO.EXE (PID=1356). All the DS Servers in domain are not
responding.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:04 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 8/19/2003
Time: 8:16:05 PM
User: N/A
Computer: DIMENSION2
Description:
Process MAD.EXE (PID=2116). All Domain Controller Servers in use are not
responding:
dimension2.internal.fpsnow.com

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:06 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:08 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
lsass (460) The database engine stopped.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:10 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...
Click to expand...
 
Joseph Geretz wrote in
Digging a bit deeper...

I stopped ALL services manually (except for the handful which
cannot be stopped). Shutdown succeeds. OK, it seems that one of my
services is hanging on shutdown. But which one? I don't relish the
prospect of using the trial and error approach to shut down
services one by one, rebooting each time. Is there any way to
generate a verbose log of shutdown activity so that I can see
what's going on during shutdown?

Thanks for your help!
Click to expand...

Try TIP
2983 - How do I enable Windows 2000 verbose boot, shutdown, logon,
and logoff status messages?
at www.jsiinc.com
- Joe Geretz -

Joseph Geretz said:
I don't think any of those events have anything to do with the
hang. I stopped all Exchange services manually via the Services
console app, but the
system still hung on shutdown. How can I debug this?

Thanks,

- Joe Geretz -

Joseph Geretz said:
Currently, I'm running Exchange 2003 under Windows Server 2003.
However, the
problem originally occurred when I upgraded to Exchange 2003
under Windows
Server 2000. (This was during the course of upgrading my
server. I've since
completed the upgrade for both Exchange and Windows.)

Basically, Windows hangs on shutdown. Here are the final
entries from the
eventlog. The first entry is a successful shutdown of SQL
Server. As you can
see, shutdown was initiated at 8:16. Over the next 10 seconds
or so, a whole
bunch of Exchange related failures are logged. Shutdown then
simply hangs
and I need to perform a machine reset in order to re-boot.
After restarting
I can see where the system hung because there's a large gap in
eventlog entries.

I've presented the shutdown eventlog entries below. If you can
help me with
this, I'll be most grateful.

Thanks!

- Joe Geretz -

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/19/2003
Time: 8:16:01 PM
User: N/A
Computer: DIMENSION2
Description:
17147 : SQL Server terminating because of system shutdown.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 8/19/2003
Time: 8:16:03 PM
User: N/A
Computer: DIMENSION2
Description:
Process INETINFO.EXE (PID=1356). All the DS Servers in domain
are not responding.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:04 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 8/19/2003
Time: 8:16:05 PM
User: N/A
Computer: DIMENSION2
Description:
Process MAD.EXE (PID=2116). All Domain Controller Servers in
use are not responding:
dimension2.internal.fpsnow.com
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:06 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:08 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.
Click to expand...

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

Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
lsass (460) The database engine stopped.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:10 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...
Click to expand...
Click to expand...
 
One thing I forgot to add, is the machine in question is dual boot with
Windows XP Professional which unlike W2K3 does not have any shutdown issues.

Paul


Paul B T Hodges said:
I've also got a shutdown problem on one of my pcs with win2k3. I tried
enabling verbose messaging in group policy as this tip describes but
unfortunately I don't see that it gains you very much, apart from a few
extra messages flashing past in the bottom line of the starting up and
shutting down window.

At the point when my system hangs on shutdown, the box has diappeared and
all that is left is a frozen mouse pointer on a blank grey screen.

If I power down the system manually it comes back fine. Funnily enough, if I
do a restart instead of shutdown that works every time.

I suppose this could point to some problem with windows telling the bios to
power off the system. What would be great, is if, like some other Operating
Systems that I've worked on, it was possible to generate a shutdown logfile
with timestamped entries showing each process shutting step by step. If the
last line was something like "Sending call to bios to power down" this would
confirm it.

Perhaps I'm missing something and there is a way to achieve this.

If not, is there an article somewhere which explains the internals of
shutdown functionality step by step. Is there a registry entry or script
which could be modified to achieve this. If not publicly documented, surely
MS must have some way of achieving this for their own internal testing
purposes.

Best Regards

Paul





Mark V said:
Joseph Geretz wrote in
Digging a bit deeper...

I stopped ALL services manually (except for the handful which
cannot be stopped). Shutdown succeeds. OK, it seems that one of my
services is hanging on shutdown. But which one? I don't relish the
prospect of using the trial and error approach to shut down
services one by one, rebooting each time. Is there any way to
generate a verbose log of shutdown activity so that I can see
what's going on during shutdown?

Thanks for your help!
Click to expand...

Try TIP
2983 - How do I enable Windows 2000 verbose boot, shutdown, logon,
and logoff status messages?
at www.jsiinc.com
- Joe Geretz -

I don't think any of those events have anything to do with the
hang. I stopped all Exchange services manually via the Services
console app, but
the
system still hung on shutdown. How can I debug this?

Thanks,

- Joe Geretz -

Currently, I'm running Exchange 2003 under Windows Server 2003.
However,
the
problem originally occurred when I upgraded to Exchange 2003
under
Windows
Server 2000. (This was during the course of upgrading my
server. I've
since
completed the upgrade for both Exchange and Windows.)

Basically, Windows hangs on shutdown. Here are the final
entries from
the
eventlog. The first entry is a successful shutdown of SQL
Server. As you
can
see, shutdown was initiated at 8:16. Over the next 10 seconds
or so, a
whole
bunch of Exchange related failures are logged. Shutdown then
simply
hangs
and I need to perform a machine reset in order to re-boot.
After
restarting
I can see where the system hung because there's a large gap in
eventlog entries.

I've presented the shutdown eventlog entries below. If you can
help me
with
this, I'll be most grateful.

Thanks!

- Joe Geretz -

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/19/2003
Time: 8:16:01 PM
User: N/A
Computer: DIMENSION2
Description:
17147 : SQL Server terminating because of system shutdown.


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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 8/19/2003
Time: 8:16:03 PM
User: N/A
Computer: DIMENSION2
Description:
Process INETINFO.EXE (PID=1356). All the DS Servers in domain
are not responding.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:04 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.


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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 8/19/2003
Time: 8:16:05 PM
User: N/A
Computer: DIMENSION2
Description:
Process MAD.EXE (PID=2116). All Domain Controller Servers in
use are not responding:
dimension2.internal.fpsnow.com


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:06 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
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.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:08 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.


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

Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
lsass (460) The database engine stopped.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
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.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:10 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory
dimension2.internal.fpsnow.com for distinguished name ''.
Directory returned error:[0x51] Server Down.


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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...
Click to expand...
Click to expand...
 
If Exchange 2003 is installed on a DC/GC, it may take approximately 10
minutes 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.

Hope this helps.

-------------------------
Michael Palermiti
Enterprise Messaging Support

This posting is provided "AS IS" with no warranties, and confers no rights.
© 2003 Microsoft Corporation. All rights reserved.


Joseph Geretz said:
Currently, I'm running Exchange 2003 under Windows Server 2003. However, the
problem originally occurred when I upgraded to Exchange 2003 under Windows
Server 2000. (This was during the course of upgrading my server. I've since
completed the upgrade for both Exchange and Windows.)

Basically, Windows hangs on shutdown. Here are the final entries from the
eventlog. The first entry is a successful shutdown of SQL Server. As you can
see, shutdown was initiated at 8:16. Over the next 10 seconds or so, a whole
bunch of Exchange related failures are logged. Shutdown then simply hangs
and I need to perform a machine reset in order to re-boot. After restarting
I can see where the system hung because there's a large gap in eventlog
entries.

I've presented the shutdown eventlog entries below. If you can help me with
this, I'll be most grateful.

Thanks!

- Joe Geretz -

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/19/2003
Time: 8:16:01 PM
User: N/A
Computer: DIMENSION2
Description:
17147 : SQL Server terminating because of system shutdown.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 8/19/2003
Time: 8:16:03 PM
User: N/A
Computer: DIMENSION2
Description:
Process INETINFO.EXE (PID=1356). All the DS Servers in domain are not
responding.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:04 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 8/19/2003
Time: 8:16:05 PM
User: N/A
Computer: DIMENSION2
Description:
Process MAD.EXE (PID=2116). All Domain Controller Servers in use are not
responding:
dimension2.internal.fpsnow.com

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:06 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
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.

--------------------------------------------------------------------------
Click to expand...
--
-----

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:08 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
lsass (460) The database engine stopped.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
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.

--------------------------------------------------------------------------
Click to expand...
--
-----

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:10 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...
 
Hi Michael,

I think that your diagnosis is correct. First of all, I want to retract my
original assertion. The system does not hang (although 10 minutes seems like
a lifetime when you are trying to restart ;-) Your estimate of 10 minutes is
right on the money; this is how long it takes to shut down. I will look into
ways of shutting down Exchange first and then shutting down the OS.

Just a suggestion for MS, if I may. Services start in a defined sequence
when the OS boots up. Shouldn't the reverse sequence be used to stop
services when the OS is powering down?

Thanks for your help!

- Joe Geretz -

Michael Palermiti said:
If Exchange 2003 is installed on a DC/GC, it may take approximately 10
minutes 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.

Hope this helps.

-------------------------
Michael Palermiti
Enterprise Messaging Support

This posting is provided "AS IS" with no warranties, and confers no rights.
© 2003 Microsoft Corporation. All rights reserved.


Joseph Geretz said:
Currently, I'm running Exchange 2003 under Windows Server 2003. However, the
problem originally occurred when I upgraded to Exchange 2003 under Windows
Server 2000. (This was during the course of upgrading my server. I've since
completed the upgrade for both Exchange and Windows.)

Basically, Windows hangs on shutdown. Here are the final entries from the
eventlog. The first entry is a successful shutdown of SQL Server. As you can
see, shutdown was initiated at 8:16. Over the next 10 seconds or so, a whole
bunch of Exchange related failures are logged. Shutdown then simply hangs
and I need to perform a machine reset in order to re-boot. After restarting
I can see where the system hung because there's a large gap in eventlog
entries.

I've presented the shutdown eventlog entries below. If you can help me with
this, I'll be most grateful.

Thanks!

- Joe Geretz -

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/19/2003
Time: 8:16:01 PM
User: N/A
Computer: DIMENSION2
Description:
17147 : SQL Server terminating because of system shutdown.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 8/19/2003
Time: 8:16:03 PM
User: N/A
Computer: DIMENSION2
Description:
Process INETINFO.EXE (PID=1356). All the DS Servers in domain are not
responding.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:04 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 8/19/2003
Time: 8:16:05 PM
User: N/A
Computer: DIMENSION2
Description:
Process MAD.EXE (PID=2116). All Domain Controller Servers in use are not
responding:
dimension2.internal.fpsnow.com

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:06 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:08 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
lsass (460) The database engine stopped.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:10 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...
Click to expand...
 
I had heard that this will be resolved in the RTM release.

just my 2 cents

Joseph Geretz said:
Currently, I'm running Exchange 2003 under Windows Server 2003. However, the
problem originally occurred when I upgraded to Exchange 2003 under Windows
Server 2000. (This was during the course of upgrading my server. I've since
completed the upgrade for both Exchange and Windows.)

Basically, Windows hangs on shutdown. Here are the final entries from the
eventlog. The first entry is a successful shutdown of SQL Server. As you can
see, shutdown was initiated at 8:16. Over the next 10 seconds or so, a whole
bunch of Exchange related failures are logged. Shutdown then simply hangs
and I need to perform a machine reset in order to re-boot. After restarting
I can see where the system hung because there's a large gap in eventlog
entries.

I've presented the shutdown eventlog entries below. If you can help me with
this, I'll be most grateful.

Thanks!

- Joe Geretz -

Event Type: Information
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 8/19/2003
Time: 8:16:01 PM
User: N/A
Computer: DIMENSION2
Description:
17147 : SQL Server terminating because of system shutdown.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2104
Date: 8/19/2003
Time: 8:16:03 PM
User: N/A
Computer: DIMENSION2
Description:
Process INETINFO.EXE (PID=1356). All the DS Servers in domain are not
responding.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:04 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 8/19/2003
Time: 8:16:05 PM
User: N/A
Computer: DIMENSION2
Description:
Process MAD.EXE (PID=2116). All Domain Controller Servers in use are not
responding:
dimension2.internal.fpsnow.com

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:06 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:07 PM
User: N/A
Computer: DIMENSION2
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.

--------------------------------------------------------------------------
Click to expand...
--
-----

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:08 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Information
Event Source: ESENT
Event Category: General
Event ID: 101
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
lsass (460) The database engine stopped.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:09 PM
User: N/A
Computer: DIMENSION2
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.

--------------------------------------------------------------------------
Click to expand...
--
-----

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:10 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
Description:
LDAP Bind was unsuccessful on directory dimension2.internal.fpsnow.com
for distinguished name ''. Directory returned error:[0x51] Server Down.

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

Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 8/19/2003
Time: 8:16:11 PM
User: N/A
Computer: DIMENSION2
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.
Click to expand...
 
Back
Top