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

Symptoms
A NullReferenceException error may occur in the Microsoft .NET Framework version 1.1 when one of the following conditions is true: You use reflection to obtain a default value of a parameter out of a method that uses a default null value for a parameter.You use reflection to invoke a method that uses a default null value for a parameter.
Resolution
To resolve this problem, obtain the latest service pack for the Microsoft .NET Framework 1.1. For more information, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?FamilyId=A8F5654F-088E-40B2-BBDB-A83353618B38(http://www.microsoft.com/downloads/details.aspx?FamilyId=A8F5654F-088E-40B2-BBDB-A83353618B38)

Symptoms
Consider the following scenario:In the Microsoft .NET Framework 2.0, a class is derived from the ServicedComponent class.This class implements a method that is inherited from a custom interface. This method is used to throw a custom exception type that is derived from the ApplicationException exception type.This method does not use non-primitive type parameters. In this scenario, if a managed client application calls this method by using a reference to the custom interface, this method does not throw a custom exception type that is derived from the ApplicationException exception type. Instead, this method incorrectly throws the ApplicationException exception type.
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 Microsoft .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)NoteIn 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.PrerequisitesYou must have the Microsoft .NET Framework 2.0 installed to apply this hotfix.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 informationThe 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.The .NET Framework 2.0, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMscordacwks.dll2.0.50727.821802,30419-Mar-200719:31×86Mscorjit.dll2.0.50727.821326,65619-Mar-200719:31×86Mscorlib.dll2.0.50727.8214,308,99219-Mar-200719:31×86Mscorpe.dll2.0.50727.821102,91219-Mar-200719:31×86Mscorwks.dll2.0.50727.8215,633,02419-Mar-200719:31×86Normalization.dll2.0.50727.82115,36019-Mar-200719:31×86Normidna.nlpNot Applicable59,34219-Mar-200719:31Not ApplicableNormnfc.nlpNot Applicable45,79419-Mar-200719:31Not ApplicableNormnfd.nlpNot Applicable39,28419-Mar-200719:31Not ApplicableNormnfkc.nlpNot Applicable66,38419-Mar-200719:31Not ApplicableNormnfkd.nlpNot Applicable60,29419-Mar-200719:31Not ApplicablePeverify.dll2.0.50727.821136,19219-Mar-200719:31×86Sos.dll2.0.50727.821382,46419-Mar-200719:31×86Vsavb7rt.dll8.0.50727.8211,330,68819-Mar-200719:31×86The .NET Framework 2.0, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMscordacwks.dll2.0.50727.8211,597,44019-Mar-200711:20×64Mscorjit.dll2.0.50727.8211,587,71219-Mar-200711:18×64Mscorlib.dll2.0.50727.8213,960,83219-Mar-200714:36×64Mscorpe.dll2.0.50727.821157,18419-Mar-200711:12×64Mscorpjt.dll2.0.50727.8212,004,99219-Mar-200711:18×64Mscorwks.dll2.0.50727.82110,334,20819-Mar-200711:16×64Normalization.dll2.0.50727.82118,43219-Mar-200711:17×64Normidna.nlpNot Applicable59,34219-Mar-200711:19Not ApplicableNormnfc.nlpNot Applicable45,79419-Mar-200711:19Not ApplicableNormnfd.nlpNot Applicable39,28419-Mar-200711:19Not ApplicableNormnfkc.nlpNot Applicable66,38419-Mar-200711:19Not ApplicableNormnfkd.nlpNot Applicable60,29419-Mar-200711:19Not ApplicablePeverify.dll2.0.50727.821205,82419-Mar-200711:18×64Sos.dll2.0.50727.821480,76819-Mar-200711:27×64The .NET Framework 2.0, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMscordacwks.dll2.0.50727.8212,719,23219-Mar-200711:21IA-64Mscorjit.dll2.0.50727.8212,705,92019-Mar-200711:19IA-64Mscorlib.dll2.0.50727.8213,960,83219-Mar-200715:27IA-64Mscorpe.dll2.0.50727.821313,85619-Mar-200711:12IA-64Mscorpjt.dll2.0.50727.8213,501,05619-Mar-200711:19IA-64Mscorwks.dll2.0.50727.82121,317,63219-Mar-200711:17IA-64Normalization.dll2.0.50727.82144,03219-Mar-200711:18IA-64Normidna.nlpNot Applicable59,34219-Mar-200711:20Not ApplicableNormnfc.nlpNot Applicable45,79419-Mar-200711:20Not ApplicableNormnfd.nlpNot Applicable39,28419-Mar-200711:20Not ApplicableNormnfkc.nlpNot Applicable66,38419-Mar-200711:20Not ApplicableNormnfkd.nlpNot Applicable60,29419-Mar-200711:20Not ApplicablePeverify.dll2.0.50727.821383,48819-Mar-200711:19IA-64Sos.dll2.0.50727.821862,72019-Mar-200711:29IA-64

Symptoms
When you try to add the System Monitor Control (Sysmon.ocx) to a Windows Form, you receive the following error message:

Object Reference Error
Resolution
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft .NET Framework service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product 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)NoteIn 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. The English version of this fix has the file attributes (or later) 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 tool in Control Panel.

DateTimeVersionSizeFile name————————————————————————-17-Aug-200206:401.0.3705.3081,175,552System.data.dll17-Aug-200206:381.0.3705.3081,986,560System.windows.forms.dll

Symptoms
When you use a Collaboration Data Objects (CDO) 1.21-based application to call the Respond method on the parent of a recurring meeting request, the application will throw the following CDO exception:

[MAPI_E_NOT_FOUND (8004010F)]
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.Prerequisites Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 2.
For more information about the latest service packs for Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
836993?(http://support.microsoft.com/kb/836993/) How to obtain the latest service packs for Exchange Server 2003Restart requirementYou do not have to restart thecomputer after you apply this hotfix. Hotfix replacement informationThis hotfixdoes not replace any other software updates.File informationThe 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 sizeDateTimePlatformCdo.dll6.5.7651.38717,82426-Jul-200616:29×86