.NET Questions and Solutions

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
Consider the following scenario:In Microsoft Visual Studio 2005, you create a C++ application.You do not specify the /fp:except option. Therefore, floating-point exceptions are not enabled in the C++ application.You do not specify the /fp:strict option. Therefore, the strict floating-point model is not enabled in the C++ application.An inline function in the C++ application returns an uninitialized floating-point variable.You compile the C++ application.In this scenario, a floating-point exception may occur when you run the C++ application. Additionally, you may receive the following error message:

0xC0000090: Floating-point invalid operation.Note This problem may occur in debug builds and in release builds.
Resolution
This problem occurs when the uninitialized floating-point variable loads a memory location that contains a signaling not-a-number (NaN) value.

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 Microsoft Clip Gallery 5.0, you may notice that some clip art is missing that had been available in the past.
Resolution
This problem can occur when you install Microsoft Publisher 2000 and one or more of the following Microsoft programs:PhotoDraw 2000Home Publishing 2000Greetings 2000All of these other programs install some of the same collections as does Publisher 2000, but the programs are installed into different folder locations. These collections are called catalogs. The problem occurs when the path to one or more of the collections becomes invalid.
A path to the Clip Gallery catalog can become invalid if one or more of these programs are removed without using the correct uninstall process.

Symptoms
In a Microsoft .NET Framework 2.0-based application, you use a recursively defined constraint ofa generic type. When you do this, a BadImageFormatException exception may occur at run time. This problem occurs only in certain scenarios.
Resolution
This problem occurs because of an issue in the Microsoft Visual Studio 2005 common language runtime (CLR 2.0) components.

Symptoms
This article describes a hotfix rollup package that is available for the Microsoft Systems Management Server (SMS) 2003 Service Pack 3 (SP3) client. This update is in the form of an MSP package and can only be used to update existing SMS 2003 SP3 clients. The same update is also available as a Client.msi package inhotfix 941214. This hotfix provides an updated Client.msi for Systems Management Server 2003.
This hotfix rollup packages resolves the following problems.
Problem 1The Wmiprvse.exe process on client computers in the organization may generate high CPU usage while SMS 2003 SP3 Asset Advisor is performing hardware-inventory operations. Sometimes, the CPU usage may reach 100 percent. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937882?(http://support.microsoft.com/kb/937882/) After you install SMS 2003 Service Pack 3, the Wmiprvse.exe process may generate high CPU usage on client computers during hardware-inventory operations
Problem 2When you schedule advertisements in Microsoft Systems Management Server 2003, you experience the following symptoms:Advertisements that have a recurring daily schedule that you create in British Summer Time (BST) run one hour too early after the time changes to Coordinated Universal Time (UTC).Advertisements that have a recurring daily schedule that you create in Coordinated Universal Time run one hour too late after the time changes to BST.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
933870?(http://support.microsoft.com/kb/933870/) Advertisements that have a recurring schedule are off by one hour in SMS 2003 when the time changes between British Summer Time (BST) and Coordinated Universal Time
Problem 3The hardware inventory process may fail for SMS clients that are running on Windows Vista-based computers. Additionally, Task Manager may display that a Wmiprvse.exe process has more than 500 megabytes (MB) of private working set. This behavior usually occurs on a computer that has more than 100,000 events in the Security log.
The symptoms of hardware failure may vary. Typically, no inventory data is sent to the management point when this problem occurs. Additionally, one of the following messages is logged in the InventoryAgent.log file.
Log message 1
Inventory: Starting reporting task.
Reporting: (80041013) Reading of reports failed
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of CLIMSG_HINV_ERROR_REPORTFAILURE
…
CReportTask::CreateReportHeader: GetSingleWMIObject() – Failed to read the client version & type.
CReportTask::CreateReport: CreateReportHeaderFile()failed.
CReportTask::CreateReport() failed.
Reporting: Cycle failed: 80041013
Inventory: Reporting Task completed in 0.062 seconds
Inventory: Reporting task failed to completed successfully. No report will be sent.Log message 2
Unknown error encountered processing an instance of class CCM_System: 80041013
Collection: Failed to process mandatory data item for class: CCM_System. Cycle abandoned !!
Failed to process instances of CCM_System: 80004005
Collection: Cycle failed: 80004005Log message 3
Unknown error encountered processing an instance of class SMS_MIFGroup: 80041013Note This information is logged when some noncritical classes are not listed in the inventory data. The class that is listed in the log information may vary between clients or between instances of hardware inventory that are executed. The 80041013 error code represents a WMI Provider Load Failure (WBEM_E_PROVIDER_LOAD_FAILURE) error.
Resolution
Problem 4 Some processes have an access violation problem because the AssetAdvisor.dll module allocates insufficient memory. For example, the Wmiprvse.exe process may have this access violation problem.
Problem 5 After you upgrade to Microsoft SMS 2003 Service Pack 3, you run a report that is based on the v_Add_Remove_Programs view. However, the report stops responding, and the process uses 100 percent of the CPU resources. For example, reports such as the “Computers with specific software registered in Add Remove Programs” report stop responding, and the process uses 100 percent of the CPU resources.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
939872?(http://support.microsoft.com/kb/939872/) Reports that use the v_Add_Remove_Programs view stop responding and cause high CPU use in SMS 2003 Service Pack 3
Problem 6 SMS 2003 should use data that is combined with the ProductID registry entry and the DigitalProductID registry entry to determine sale channel code. Earlier products do not support the DigitalProductID registry entry.
Problem 7Inventory counts are inaccurate in the License 1A report and in the License 1B report. Multiple components that have the same Microsoft product code (MPC) appear as a single product instead of as individual products.
Problem 8When Microsoft SQL Enterprise Manager and Books online are installed on the computer, they are incorrectly reported as SQL Server installations in the License Ledger report.
Problem 9The SMS_InstalledSoftware class incorrectly generates a software code for Windows operating systems by inserting some extra characters.