Outlook 2000 appears to be causing TRMSVR2003 to fail

[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.

 

[msnews]

It's happened again, please help

Another Symptom is that the Server appears to be under so much load that the
task manager will not launch when I right click and select via the taskbar.
The Terminal Services Manager just has a yellow question mark on the Server
branch and a message on the right hand side that says something about it
"still gathering information about the server"

If I leave it for about 2 hours (with all sessions closed) the server sort
of comes back. The task manager (that I attempted to launch 2 hours earlier)
is displayed and the Terminal Services manager is also displayed correctly.

The weird thing is that there are no users displayed in the Users tab of the
Task manager, however, the processes tab tells a different story. There are
many services displayed for users that "used to be logged on". The common
process to all of them is OUTLOOK.EXE. Some of the sessions have multiple
instances of OUTLOOK.EXE (because they attempted to launch it to make it
run). Other sessions have WINWORD.EXE, EXCEL.EXE and DWWIN.EXE still
running.

I don't think I am overloading the server, there are only 10 users at any
one time and it's a twin P4 with 2GB of RAM.

This is driving me nuts, I am so tempted to rebuild this server (for the 4th
time) but this time with Windows 2000 as opposed to 2003. I have several
clients on Windows 2000 Terminal Services and they are all pretty much
stable. I have 3 TS 2003 clients and they are all experiencing problems of
some sort (this one is a desperate one), what am I doing wrong?

This client is a 6 hour drive away, can I hire the services of a Microsoft
Expert to help me with this, it's obviously over my head.

Please Help!
distraught

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.

 

[msnews]

Some more info.

More info

In the EVENT VIEWER some errors and warnings
==============================================================
Event Type: Error
Event Source: Application Hang
Event Category: (101)
Event ID: 1002
Date: 23/10/2003
Time: 04:14
User: N/A
Computer: BOURKESERVER
Description:
Hanging application tsadmin.exe, version 5.2.3790.0, 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 74 73 61 64 6d 69 tsadmi
0018: 6e 2e 65 78 65 20 35 2e n.exe 5.
0020: 32 2e 33 37 39 30 2e 30 2.3790.0
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: Application Hang
Event Category: (101)
Event ID: 1002
Date: 23/10/2003
Time: 04:46
User: N/A
Computer: SERVER
Description:
Hanging application EXCEL.EXE, version 9.0.0.6627, 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 45 58 43 45 4c 2e EXCEL.
0018: 45 58 45 20 39 2e 30 2e EXE 9.0.
0020: 30 2e 36 36 32 37 20 69 0.6627 i
0028: 6e 20 68 75 6e 67 61 70 n hungap
0030: 70 20 30 2e 30 2e 30 2e p 0.0.0.
0038: 30 20 61 74 20 6f 66 66 0 at off
0040: 73 65 74 20 30 30 30 30 set 0000
0048: 30 30 30 30 0000
==================================================================
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 23/10/2003
Time: 04:47
User: NT AUTHORITY\SYSTEM
Computer: SERVER
Description:
Windows saved user XXXX\eyehealth registry while an application or service
was still using the registry during log off. The memory used by the user's
registry has not been freed. The registry will be unloaded when it is no
longer in use.

This is often caused by services running as a user account, try configuring
the services to run in either the LocalService or NetworkService account.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

===============================================================
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1524
Date: 23/10/2003
Time: 05:38
User: XXXX\ellen
Computer: SERVER
Description:
Windows cannot unload your classes registry file - it is still in use by
other applications or services. The file will be unloaded when it is no
longer in use.



For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
=================================================================
Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 23/10/2003
Time: 05:38
User: NT AUTHORITY\SYSTEM
Computer: SERVER
Description:
Windows saved user XXXX\ellen registry while an application or service was
still using the registry during log off. The memory used by the user's
registry has not been freed. The registry will be unloaded when it is no
longer in use.

This is often caused by services running as a user account, try configuring
the services to run in either the LocalService or NetworkService account.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

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.

 

[Tarkan Shahho]

PLEASE HELP..

PLEASE PLEASE PLEASE

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.

 

[Matthew Harris [MVP]]

Have you seen these articles:

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

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


I'd have to assume that Outlook is causing the system to
become unstable, and as people get frustrated with the
syetm's unresponsiveness, they logout. However, since
Outlook is currently working, it probably has some locked
registry entires, which then cause the user's profiles to
unload (hence the eventlog entries about profiles not
unloading properly). When the user's eventually finish
logging out, the Outlook processes aren't being killed
off, and they then become orphaned processes not belonging
to anyone (hence the multiple Outlook.exe processes you
see belonging to various people who aren't logged in
anymore).

-M

-----Original Message-----
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.


.

 

[Tarkan Shahho]

Thanks Matthew,

I have contacted MS and they are sending me the Hotfix, "fingers crossed"

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.