Nothing occurs when you click Explore on the desktop in ActiveSync 4.0 or in ActiveSync 4.1 on a computer that is running Windows Server 2003 x64 Edition (907885)

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

When you click Explore on the desktop in Microsoft ActiveSync 4.0 and in Microsoft ActiveSync 4.1, nothing occurs. You experience this issue when the following conditions are true:

You install ActiveSync 4.0 or ActiveSync 4.1 on a computer that is running Microsoft Windows Server 2003 x64 Edition.
You install Terminal Server on the computer.
You run Terminal Server in Execute Mode.

CAUSE

This problem occurs because Windows Server 2003 substitutes the path of the Windows installation folder with a path of a user-specific Windows folder. The user-specific Windows folder is the %HOMEDRIVE%\%HOMEPATH%\WINDOWS folder. When ActiveSync starts the Mobile Device shell extension, ActiveSync determines whether ActiveSync is running on a 64-bit Windows edition. Then, ActiveSync starts the 32-bit Explorer.exe application to host the 32-bit shell extension. Because Terminal Server path substitution occurs, ActiveSync tries to start the Explore.exe application from the %HOMEDRIVE%\%HOMEPATH%\WINDOWS\SysWOW64 folder. However, the Explore.exe application may not run because the SysWOW64 folder does not exist in the user-specific Windows folder.

RESOLUTION

To resolve this problem, you must set the application compatibility flag for the 32-bit ActiveSync Application (WCESMgr.exe) and for the 32-bit ActiveSync Connection Manager (Wcescomm.exe). When you do this, Terminal Server does not substitute the Windows folder path with the user-specific Windows folder path.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. Follow these steps, and then quit Registry Editor:

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\WCESMgr
On the Edit menu, click Modify.
Type 00000408, and then press ENTER.

Note You must follow similar steps for the ActiveSync connection manager HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\Applications\wcescomm registry subkey.

MORE INFORMATION

Steps to reproduce the behavior

Install Terminal Server and ActiveSync 4.0 or ActiveSync 4.1 on a computer that is running Windows Server 2003 x64 Edition.
On the computer, connect a Windows Mobile device, and establish a partnership.

You notice the behavior that is mentioned in the "Symptoms" section when you use one of the following methods to click Explore:
- On the ActiveSync Tools menu, click Explore Device.
- In ActiveSync, click the Explore toolbar.
- In the notification area, right-click ActiveSync, and then click Explore.

REFERENCES

For more information about Terminal Server application compatibility flags, click the following article number to view the article in the Microsoft Knowledge Base:

186499 Terminal Server registry settings for applications

Note The registry path that is used for WOW64 application compatibility flags differs from the path that is discussed in Microsoft Knowledge Base article 186499.