T
Tarkan Shahho
Hi All,
This is a repost of a previous issue as I don't want to confuse the matter
with some of my previous findings as I may have had compounded issues and
most of them have been solved.
Terminal Server 2003 with Exchange Server 2000 Sp3 running Office 2000.
Server has had all Critical and non Critical updates applied (with the
exception of DirectX)
Office 2000 has had all Office updates installed.
after the server has been running for say 10 hours of good use, a user will
attempt to launch outlook and nothing happens. Once this occurs no-one else
can launch outlook afterwards. Those who are already in are fine and can
continue to operate their machines. If the "problem" sessions attempt to
launch outlook again, they still don't get a response. If you observe the
task manager, you will see multiple instances of Outlook and I cannot end
those processes.
The users that have been operating successfully have not experienced any
problems at all, except that speed of their respective sessions begins to
fail.
There is an error in the Application Event Log at roughly the same time
referring to a HANG. Shortly afterwards there are two Exchange Errors - The
log entries are listed below.
===================================================================
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 23/10/2003
Time: 08:46
User: N/A
Computer: XYZSERVER
Description:
Hanging application OUTLOOK.EXE, version 9.0.0.6604, hang module hungapp,
version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 4f 55 54 4c 4f 4f OUTLOO
0018: 4b 2e 45 58 45 20 39 2e K.EXE 9.
0020: 30 2e 30 2e 36 36 30 34 0.0.6604
0028: 20 69 6e 20 68 75 6e 67 in hung
0030: 61 70 70 20 30 2e 30 2e app 0.0.
0038: 30 2e 30 20 61 74 20 6f 0.0 at o
0040: 66 66 73 65 74 20 30 30 ffset 00
0048: 30 30 30 30 30 30 000000
==================================================================
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 23/10/2003
Time: 09:03
User: N/A
Computer: SERVER
Description:
Process MAD.EXE (PID=2752). All Domain Controller Servers in use are not
responding:
bourkeserver.bahs.com.au
For more information, click http://www.microsoft.com/contentredirect.asp.
===================================================================
Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 23/10/2003
Time: 09:03
User: N/A
Computer: SERVER
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.
For more information, click http://www.microsoft.com/contentredirect.asp.
This is a repost of a previous issue as I don't want to confuse the matter
with some of my previous findings as I may have had compounded issues and
most of them have been solved.
Terminal Server 2003 with Exchange Server 2000 Sp3 running Office 2000.
Server has had all Critical and non Critical updates applied (with the
exception of DirectX)
Office 2000 has had all Office updates installed.
after the server has been running for say 10 hours of good use, a user will
attempt to launch outlook and nothing happens. Once this occurs no-one else
can launch outlook afterwards. Those who are already in are fine and can
continue to operate their machines. If the "problem" sessions attempt to
launch outlook again, they still don't get a response. If you observe the
task manager, you will see multiple instances of Outlook and I cannot end
those processes.
The users that have been operating successfully have not experienced any
problems at all, except that speed of their respective sessions begins to
fail.
There is an error in the Application Event Log at roughly the same time
referring to a HANG. Shortly afterwards there are two Exchange Errors - The
log entries are listed below.
===================================================================
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 23/10/2003
Time: 08:46
User: N/A
Computer: XYZSERVER
Description:
Hanging application OUTLOOK.EXE, version 9.0.0.6604, hang module hungapp,
version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 48 61 6e 67 ion Hang
0010: 20 20 4f 55 54 4c 4f 4f OUTLOO
0018: 4b 2e 45 58 45 20 39 2e K.EXE 9.
0020: 30 2e 30 2e 36 36 30 34 0.0.6604
0028: 20 69 6e 20 68 75 6e 67 in hung
0030: 61 70 70 20 30 2e 30 2e app 0.0.
0038: 30 2e 30 20 61 74 20 6f 0.0 at o
0040: 66 66 73 65 74 20 30 30 ffset 00
0048: 30 30 30 30 30 30 000000
==================================================================
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 23/10/2003
Time: 09:03
User: N/A
Computer: SERVER
Description:
Process MAD.EXE (PID=2752). All Domain Controller Servers in use are not
responding:
bourkeserver.bahs.com.au
For more information, click http://www.microsoft.com/contentredirect.asp.
===================================================================
Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8250
Date: 23/10/2003
Time: 09:03
User: N/A
Computer: SERVER
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.
For more information, click http://www.microsoft.com/contentredirect.asp.