.NET Questions and Solutions

Symptoms
On a Microsoft Windows XP-, Microsoft Windows Server 2003-, Microsoft Windows Vista- and Microsoft Windows Server 2008-based computer, if you attempt to shutdown the computer when you are running an application that uses the Remote Access Connection Manager, or the Telephony service, the Remote Access Connection Manager or the Telephony service may not be stopped properly and an unexpected error may occur.
In addition, even if you try to stop the Remote Access Connection Manager service or the Telephony service, the following error massage is displayed and the service cannot be stopped.

When running the Remote Access Connection Manager service Windows XP and Windows Server 2003

Cannot stop the Remote Access Connection Manager service on a local computer.
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem persists, contact your system administrator. On Windows Vista and Windows Server 2008, you cannot click the Stop button once the service is in use and an error message will not be displayed.
When running the Telephony service Windows XP and Windows Server 2003

Cannot stop the Telephony service on a local computer.
Error 1053:The service did not respond to the start or control request in a timely fashion. Windows Vista and Windows Server 2008

Cannot stop the Telephony service on a local computer.
Error 1052:The requested control is not valid for this service.
Resolution
Because the Remote Access Connection Manager or the Telephony service cannot be stopped properly, an application that uses these services may return an unexpected error.

Symptoms
When you run the System Preparation tool (Sysprep.exe) on a computer that is running Windows Vista or Windows Server 2008,a folder is created in or copied to the following location:
C:\users\public\documents\dataHowever, the access control lists (ACLs) forthis folder are out of order.
For example, assume that you create a folder under C:\users\public\documents\data. Then, you right-click the folder, you click Properties, and then you click the Security tab. In this scenario, the Security dialog box does not appear. Instead, youreceive the following error message:

The permissions on %foldername% are incorrectly ordered, which may cause some entries to be ineffective.
Resolution
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites To apply this hotfix on a computer that is running Windows Vista, you must have Windows Vista Service Pack 1 (SP1) orWindows Vista SP2 installed.
To apply this hotfix on a computer that is running Windows Server 2008, you must have Windows Server 2008 SP1 orWindows Server 2008 SP2 installed. Restart requirement You do not have to restart the computer after you apply this hotfix. Hotfix replacement information This hotfix does not replace any other hotfixes. File information The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Vista and Windows Server 2008 file information notesThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment arelisted separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature. For all supported x86-based versions of Windows Server 2008 andof Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSetupcl.exe6.0.6001.2243441,98415-May-200910:37×86Setupcl.exe6.0.6002.2213741,98415-May-200910:25×86For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSetupcl.exe6.0.6001.2243448,64015-May-200910:56×64Setupcl.exe6.0.6002.2213748,64015-May-200910:33×64For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSetupcl.exe6.0.6001.2243495,23215-May-200910:34IA-64Setupcl.exe6.0.6002.2213795,23215-May-200910:26IA-64

Symptoms
When you try to activate Windows Vista or Windows Server 2008 over the Internet, the activation may be unsuccessful. Additionally, you may experience one or more of the following symptoms: Activation fails with error code 0×8004FE33. The following Error events may be recorded in the Application log:

Log Name: Application
Source: Software Licensing Service
Event ID: 8198
Level: Error Description: License Activation (SLUI.exe) failed with the following error code: 0×80004005

Log Name: Application
Source: Software Licensing Service
Event ID: 1008
Level: Error Description: Acquisition of Secure Processor Certificate failed. Status Code=hr=0×8004FE33Activation is not successful, and you are not prompted for credentials.
Resolution
This issue may occur when you connect to the Internet through a proxy server where Basic authentication is enabled.
When the proxy server is configured for Basic authentication, the server requires that you type a username and a password. However, the activation user interface does not let you enter these credentials. Therefore, the Basic authentication fails, and activation is not successful.

Symptoms
Consider the following scenario:You install the Terminal Services role on a computer that is running Windows Server 2008.You start a Terminal Services session with the terminal server from a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1). You try to shadow another Terminal Services session in the Terminal Services session.Your shadow request is accepted by the user account in the Terminal Services session that you want to shadow.In this scenario, the remote control operation fails. Additionally, the shadowed Terminal Services session is disconnected, and the user account in the shadowed Terminal Services session receives one of the following error messages:
Error message 1

Your Remote Desktop session has ended. Your network administrator might have ended the connection. Try connecting again, or contact technical support for assistanceError message 2

The remote session to the remote computer was ended by means of an administration tool. Your administrator might have ended your connectionAdditionally, an event that resembles the following is added to the System log on the terminal server:
Log Name:System
Source:TermDD
Date:<date>
Event ID:50
Task Category: None
Level:Error
Keywords:Classic
User:N/A
Computer:computername.domain.com
Description:
The RDP protocol component “DATA ENCRYPTION” detected an error in the protocol stream and has disconnected the client.

Resolution
The issue occurs because one input buffer size is insufficient.
The RemoteFX feature is introduced in Service Pack 1 for Windows Server 2008 R2 and for Windows 7. This feature causes one input buffer that is used by Windows Server 2008 Terminal Server to be insufficient.

Symptoms
When you use Microsoft System Center Operations Manager 2007 to monitor system performance on Windows Server 2008-based computers, a memory leak occurs. Specifically, this memory leak occurs in the performance counters that are used by System Center Operations Manager 2007.
Note Any applications that use performance counters in Windows Server 2008 may also experience this problem.
Resolution
This problem occursbecause of a bug in the way that Windows Server 2008 manages allocated memory.

Symptoms
Consider the following scenario:
You install the Terminal Services role on a computer that is running Windows Server 2008.You connect to this terminal server, and then you perform some window-related operations in a terminal server session.
For example, you open and then close some windows in the terminal server session.In this scenario, the computer may restart unexpectedly. Additionally, you receive a Stop error message that resembles the following:

STOP 0×0000003B (parameter1, parameter2, parameter3, parameter4)
SYSTEM_SERVICE_EXCEPTION
Notes
The parameters in this Stop error message may vary, depending on the configuration of the computer.Not all the “Stop 0×0000003B” Stop errors are caused by this issue.

Resolution
This issue occurs because the Rdpwd.sys driver does not check whether a returned list is NULL or not.
When the returned list is NULL, the Rdpwd.sys driver accesses the wrong memory location. Therefore, an access violation exception occurs.