.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘hotfix’

After you run the Sysprep.exe tool in Windows Vista or in Windows Server 2008, the ACLs for a folder in C:\users\public\documents\data are out of order

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

A 0xC0AA0007 error is returned when an application uses IMAPI v2 to burn some data to a recordable disc on a computer that is running Windows Vista or Windows Server 2008

Symptoms
Assume that an application uses Image Mastering API version 2.0 (IMAPI v2) to burn some data onto a recordable DVD or CD on a computer that is running Windows Vista or Windows Server 2008. However, a 0xC0AA0007 error is returned.
This problem typically occurs with backup applications that use IMAPI v2. For example, this problem occurs when you try to create a system repair disc by using the Backup and Restore tool in the operating system. The job fails and you receive the following error message:

Fail to create system repair disc. (0xC0AA0007)
Resolution
In certain scenarios, the time that a device takes to close a session on a disc exceeds the time-out value in IMAPI. This behavior causes the image verification to fail. This hotfix increases the time-out value.

FIX: An EXCEPTION_STACK_OVERFLOW exception may occur when you try to run a Transact-SQL query in SQL Server 2005

Symptoms
This article describes the following about this hotfix release: The issues that are fixed by this hotfix packageThe prerequisites for applying the hotfix packageWhether you must restart the computer after you apply the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changes after you apply the hotfix packageThe files that are contained in the hotfix package
Resolution
When you try to run a Transact-SQL query in Microsoft SQL Server 2005, an EXCEPTION_STACK_OVERFLOW exception may occur. When this problem occurs, the SQL Server service may stop unexpectedly.
Note This problem may only occur in SQL Server 2005 x64 editions.

FIX: Exception Access Violation Encountered During Query Normalization

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.

FIX: A Windows Forms application that uses ActiveX controls may crash, and a null reference exception occurs after you install the .NET Framework 2.0 Service Pack 1

Symptoms
After you install the Microsoft .NET Framework 2.0 Service Pack 1, a Windows Forms application that uses Microsoft ActiveX controls may crash. When this problem occurs, a null reference exception occurs. Additionally, the following call stack is generated in the Windows Forms application:

System.NullReferenceException: Object reference not set to an instance of an object.at System.Windows.Forms.AxHost.OleInterfaces.AttemptStopEvents(Object trash)at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
Resolution
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 2.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Prerequisites To apply this hotfix, you must have the .NET Framework 2.0 Service Pack 1 installed. Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis 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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSystem.windows.forms.dll2.0.50727.18195,173,24814-3-200803:40×86

FIX: A new user profile may not be created and you may receive an exception when you try to create a new user profile in Commerce Server 2007

Symptoms
When you try to create a new user profile in Microsoft Commerce Server 2007, a new user profile may not be created.Additionally, you may receive the following exceptions in the Application event log.
Exception 1

An exception occurred in the ‘ProfilesWebService’ Web service.Exception details follow: System.Runtime.InteropServices.COMException (0×8007202F): A constraint violation occurred. (Exception from HRESULT: 0×8007202F)
at Microsoft.CommerceServer.Interop.Profiles.IProfileObject2.Update()
at Microsoft.CommerceServer.Internal.Profiles.ProfileStorage.UpdateOnProfilePIA(IProfileObject2 piaProfileObject, ProfileErrorContext ctxt)
at Microsoft.CommerceServer.Internal.Profiles.ProfileStorage.UpdateProfile(XmlElement profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.UpdateProfile(XmlElement& profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Exception 2

Microsoft.CommerceServer.ServerFaultException: A constraint violation occurred. (Exception from HRESULT: 0×8007202F) —>
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: A constraint violation occurred.
(Exception from HRESULT: 0×8007202F) —>
Microsoft.CommerceServer.ServerFaultException: A constraint violation occurred.
(Exception from HRESULT: 0×8007202F)
— End of inner exception stack trace —
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.PropagateOrLogExceptionInternal(Exception ex)
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.PropagateOrLogException(Exception ex)
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.UpdateProfile(XmlElement& profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)at Microsoft.CommerceServer.Internal.Profiles.ProfilesServiceProxy.AuthorizedInvoke(String methodName, Object[] parameters)— End of inner exception stack trace —
at Microsoft.CommerceServer.ServiceAgent.TryHandleWebMethodException(Exception ex, SoapHttpClientProtocol serviceProxy)at Microsoft.CommerceServer.Internal.Profiles.ProfilesServiceProxy.AuthorizedInvoke(String methodName, Object[] parameters)
at Microsoft.CommerceServer.Internal.Profiles.ProfilesServiceProxy.UpdateProfile(XmlElement& profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at Microsoft.CommerceServer.Profiles.ProfileManagementContext.UpdateProfile(XmlElement profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at Microsoft.CommerceServer.Profiles.ProfileManagementContext.UpdateProfile(XmlElement profileXml, Boolean forceOverwrite)
at Microsoft.CommerceServer.UI.CustomerAndOrdersManager.ProfilesManagementProxy.TryUpdateProfile(XmlElement profileXml, Boolean forceOverwrite)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. This problem occurs if the following conditions are true:You use a centralized profile store to maintain credentials in Active Directory Application Mode (ADAM).You try to set a password for the unicodePwd attribute.Note This problem may not occur if the unicodepwd attribute is blank.
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 this specific problem. 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 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.PrerequisitesNo prerequisites are required.Restart requirementYou must restart Microsoft Internet Information Services (IIS) after you apply this hotfix. To restart IIS, run the following command at a command prompt.

IISRESET/RESTART Note This option stops and then restarts all IIS services.Hotfix replacement information This hotfix does not replace any other software updates.
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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMscsdp.dll6.0.4010.066,56023-Feb-200722:55×86