.NET Questions and Solutions

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
Source: Microsoft Support
Resolution
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION.THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptoms
Source: Microsoft Support
Resolution
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION.THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptoms
Source: Microsoft Support
Resolution
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION.THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptoms
This article describes how to enable SQL Server connectivity on Windows XP Service Pack 2.
By default, Windows Firewall is enabled on computers that are running Microsoft Windows XP Service Pack 2. Windows Firewall closes ports such as 445 that are used for file and printer sharing to prevent Internet computers from connecting to file and print shares on your computer or to other resources. When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP ports and these ports must be open. SQL Server clients that are trying to connect to SQL Server will be not be able to connect until SQL Server is set as an exception in Windows Firewall. To set SQL Server as an exception in Windows Firewall, use the steps that are listed in the “More Information” section.
Resolution
Create an exception for each instance of SQL Server The following method will open User Datagram Protocol (UDP) port 1434 in addition to the Transmission Control Protocol (TCP) port. If you want to open these ports manually, see the following article in the Microsoft Knowledge Base:
841252?(http://support.microsoft.com/kb/841252/) How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server 2000
Note If you are running multiple instances of SQL Server, you will have to create an exception for each instance. Click Start, and then click Run. In the Run dialog box, type Firewall.cpl, and then click OK.In the Windows Firewall dialog box, click Add a Program on the Exceptions tab.In the Add Program dialog box, you can select an instance of SQL Server or you can click the Browse button to locate the instance of SQL Server that you want to add to the exception list. The default installation locations for SQL Server are listed in the following table.

Collapse this tableExpand this table
VersionFile pathSQL Server 7.0 Mssql\Binn\Sqlservr.exeSQL Server 2000 Default InstanceProgram Files\Microsoft SQL Server\Mssql\Binn\Sqlservr.exeSQL Server 2000 Named InstanceProgram Files\Microsoft SQL Server\Mssql$instancename\Binn\Sqlservr.exeSQL Server 2005 Default InstanceProgram Files\Microsoft SQL Server\MSSQL.x\MSSQL\Binn\sqlservr.exeSQL Server 2005 Named InstanceProgram Files\Microsoft SQL Server\MSSQL.x\MSSQL\Binn\sqlservr.exe
Note Each SQL Server 2005 instance is made up of a distinct set of services with specific settings for collations and other options. The directory structure, registry structure, and service names all reflect the specific instance ID of the SQL Server instance that is created during SQL Server 2005 Setup. x is the instance ID of the SQL Server instance that is created during SQL Server 2005 Setup.Select the name of the instance, and then click OK.Under Programs and Services, select the check box that is next to the name you selected in step 6, and then click OK. How to use Multiprotocol Remote Procedure Call (RPC)If you are using Multiprotocol, you must perform the steps in the “Create an exception for each instance of SQL Server” section as well as open the correct TCP ports on Windows Firewall.How to run RPC over TCPWarning 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.
To run RPC over TCP, follow these steps:Enable port 135 on Windows Firewall. To do this, follow these steps: Click Start, and then click Run.In the Run dialog box, type Firewall.cpl, and then click OK.On the Exceptions tab, click Add Port. In the Port number box, type 135, and then click the TCP button.In the Name box, type a name for the port such as MULTI, and then click OK.On the Exceptions tab, you will see the new service. To enable the port, click to select the check box next to your new service, and then click OK.Modify the \\HKLM\SOFTWARE\Policies\Microsoft\Windows NT\RPC registry key.
Note If you have just installed SQL Server, this registry key does not exist. You will have to create the key and set the value. To do this, follow these steps: Click Start, and then click Run.In the Run dialog box, type Regedit, and then click OK. This will start Registry Editor.Locate the \\HKLM\SOFTWARE\Policies\Microsoft\Windows NT\RPC Registry key.Set the RestrictRemoteClients key to 0. Quit Registry EditorRestart the computer that is running SQL Server.How to use RPC over Named PipesIf you are running RPC over Named Pipes, you must open port 445 on Windows Firewall. To do this, follow these steps: Click Start, and then click Run.In the Run dialog box, type Firewall.cpl, and then click OK.On the Exceptions tab, click Add Port. In the Port number box, type 445, and then click the TCP button.In the Name box, type a name for the port such as MULTI, and then click OK.On the Exceptions tab, you will see the new service. To enable the port, click to select the check box next to your new service, and then click OK.

Symptoms
The SQL Server may encounter an access violation exception during normalization. The following or similar stack track is generated in the SQL Server error log indicating you have encountered the failure condition:

CGroupProperties::FTableGroup() line 52 + 18 bytesCOpArg::DeriveNormalizedGroupProperties(CTreeHandle * 0×26d1ac28) line 1250 + 8 bytesCOptExpr::DeriveGroupProperties(unsigned long 0) line 2714 + 25 bytesCImpRuleBaseJoinToIdxLookup::BuildSubstitutes(COptExpr * 0×1c933b2c, CRuleContext * 0×26d1b590, CRuleReturn * 0×26d1b5fc) line 1428CTask_ApplyRule::Perform(int 5799) line 1692 + 46 bytesCMemo::ExecuteTasks(COptTask * 0×1c90b3ac, int 0, int 0) line 3453 + 20 bytesCMemo::OptimizeQuery(CQuery * 0×1c6da8bc, COptExpr * 0×1c8ca63c, double * 0×1c6d430c, int 0, int 0, s_OptimPlans * 0×26d1baf4) line 3779COptContext::PexprSearchPlan(COptExpr * 0×1c8ca63c) line 1809 + 227 bytesCOptContext::PcxteOptimizeQuery(COptExpr * 0×1c8ca63c, DRgCId * 0×26d1df24) line 1337 + 15 bytesCQuery::Optimize() line 576 + 16 bytesCQuery::Optimize(unsigned long 1) line 1101CCvtTree::PqryFromTree(TREE * 0×1c740c9c, IMemObj * 0×1c6da030, CRangeCollection * 0×1c6da85c, unsigned long 0, CCompPlan * 0×1c6da2bc {CCompPlan}) line 1056 + 25 bytesBuildQueryFromTree(TREE * 0×1c740c9c, IMemObj * 0×1c6da030, IMemObj * 0×1c6e0020, IQueryObj * * 0×1c6da800, CRangeCollection * 0×1c6da85c, unsigned long 0, CCompPlan * 0×1c6da2bc {CCompPlan}) line 521 + 31 bytes
Resolution
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 this specific problem.
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, submit a request to 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 tocreate 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. The English version of this fix should have the following file attributes or later:

File namePlatform———————-s80222i.exeIntel NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.