.NET Questions and Solutions

Symptoms
Consider the following scenario. An orchestration is published as a Web service. The Web service redirects the SOAP request to an external Web service. The external Web service returns a SOAP exception. In this scenario, the negative acknowledgement (NACK) message in Microsoft BizTalk Server 2006 does not contain the details of the original exception. If the hotfix in Microsoft Knowledge Base article 927492 has been installed, the NACK message may be correct. However, the message format may be incorrect. This may cause a NullReferenceException error message.
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.PrerequisitesYou must have BizTalk Server 2006 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 a previously released hotfix.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 sizeDateTimePlatformMicrosoft.biztalk.webservices.serverproxy.dll3.5.1714.054,34428-Sep-200717:42×86Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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
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
An INSERT, UPDATE, or DELETE query that operates on a table that is referenced by an indexed view may encounter a floating point exception during optimization. The batch and transaction is aborted, and you receive the following error message:

Server: Msg 3628, Level 16, State 1, Line 1
A floating point exception occurred in the user process. Current transaction is canceled.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
Hotfix 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.

DateTimeVersionSizeFile name——————————————————————-31-May-200317:452000.80.818.078,400Console.exe25-Jun-200300:012000.80.818.033,340Dbmslpcn.dll25-Apr-200301:12786,432Distmdl.ldf25-Apr-200301:122,359,296Distmdl.mdf30-Jan-200300:55180Drop_repl_hotfix.sql12-Sep-200302:262000.80.859.01,905,216Dtspkg.dll26-Aug-200319:162000.80.854.0528,960Dtspump.dll23-Jun-200321:402000.80.837.01,557,052Dtsui.dll23-Jun-200321:402000.80.837.0639,552Dtswiz.dll24-Apr-200301:51747,927Instdist.sql03-May-200300:561,581Inst_repl_hotfix.sql08-Feb-200305:402000.80.765.090,692Msgprox.dll01-Apr-200301:071,873Odsole.sql05-Apr-200300:462000.80.800.062,024Odsole70.dll07-May-200319:412000.80.819.025,144Opends60.dll02-Apr-200320:482000.80.796.057,904Osql.exe02-Apr-200322:152000.80.797.0279,104Pfutil80.dll04-Aug-200317:17550,780Procsyst.sql11-Sep-200323:3712,305Qfe469315.sql22-May-200321:5719,195Qfe469571.sql06-Sep-200300:361,090,932Replmerg.sql06-Sep-200306:182000.80.858.0221,768Replprov.dll06-Sep-200306:182000.80.858.0307,784Replrec.dll05-Sep-200323:001,087,150Replsys.sql13-Aug-200315:28986,603Repltran.sql29-Jul-200319:132000.80.819.0492,096Semobj.dll31-May-200317:272000.80.818.0172,032Semobj.rll05-Aug-200320:06127,884Sp3_serv_uni.sql01-Jun-200300:012000.80.818.04,215,360Sqldmo.dll07-Apr-200316:4425,172Sqldumper.exe19-Mar-200317:202000.80.789.028,672Sqlevn70.rll01-Jul-200323:182000.80.834.0180,736Sqlmap70.dll03-Sep-200301:562000.80.857.0188,992Sqlmmc.dll02-Sep-200322:032000.80.857.0479,232Sqlmmc.rll08-Feb-200305:402000.80.765.057,920Sqlrepss.dll23-Sep-200300:032000.80.863.07,614,545Sqlservr.exe25-Jul-200320:442000.80.845.0590,396Sqlsort.dll08-Feb-200305:402000.80.765.045,644Sqlvdi.dll25-Jun-200300:012000.80.818.033,340Ssmslpcn.dll01-Jun-200300:012000.80.818.082,492Ssnetlib.dll01-Jun-200300:012000.80.818.025,148Ssnmpn70.dll01-Jun-200300:012000.80.818.0158,240Svrnetcn.dll31-May-200317:592000.80.818.076,416Svrnetcn.exe30-Apr-200322:522000.80.816.045,132Ums.dll01-Jul-200323:192000.80.834.098,816Xpweb70.dll Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Symptoms
Consider the following scenario. In Microsoft SQL Server 2008 Reporting Services, you create a report. The report contains a Tablix data region item, a Subreport item, or a Chart item. The item has the NoRowsMessage property set, and there are no rows in the data region. Or, the report contains a Subreport item that displays error messages. The text box that is generated to display the error messages is split across a report page. You try to render the report. In this scenario, a dump file may be generated in the Reporting Services Logfiles folder. Additionally, you may receive an error message that resembles the following:

Assert in function = Microsoft.ReportingServices.Rendering.HPBProcessing.Paragraph.get_SpaceBefore file =line = 0 expression = Unhandled managed exception: Type = System.NullReferenceException, Message = Object reference not set to an instance of an object.
Resolution
The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
956717?(http://support.microsoft.com/kb/956717/) Cumulative update package 1 for SQL Server 2008Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909?(http://support.microsoft.com/kb/956909/)The SQL Server 2008 builds that were released after SQL Server 2008 was released

Symptoms
When you run a Microsoft .NET Framework 2.0-based application, the application may experience an ArgumentNullException exception and may exit unexpectedly (crash).
Resolution
This problem occurs because the FileSystemWatcher class throws an unhandled ArgumentNullException exception. This exception is generated because a race condition occurs between events that raise loops and the StopRaisingEvents method.