.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
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
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
In Microsoft BizTalk Server 2004, you may receive the following error message when you try to compile a large map:

Exception Caught: Object reference not set to an instance of an object.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751?(http://support.microsoft.com/kb/888751/) How to obtain the latest BizTalk Server 2004 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 tool in Control Panel.

DateTimeVersionSizeFile name——————————————————————————————01-Apr-200402:313.0.5267.0676,864Btsxmltools.dll01-Apr-200402:573.0.5267.0274,432Microsoft.biztalk.basefunctoids.dll01-Apr-200402:573.0.5267.045,056Microsoft.biztalk.crossreferencing.dll01-Apr-200402:573.0.5267.040,960Microsoft.biztalk.crossreferencingfunctoids.dll01-Apr-200402:573.0.5267.0249,856Microsoft.biztalk.mapper.dll01-Apr-200402:573.0.5267.01,114,112Microsoft.biztalk.tom.dll
NoteBecause of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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

Symptoms
When you use the IMSAdminBase::CopyKey method as part of the IIS 6.0 Compatibility components that are included with IIS 7.0, the ApplicationHost.config file becomes corrupted. Additionally, you receive the following error message when you run a Microsoft .NET Framework application that tries to read the configuration file:

Unhandled Exception: System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0×80070003)The following error message is logged in the ABO Mapper log file:

Failed to generate custom nodes.error = 800700b7
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.PrerequisitesTo apply this hotfix, you must have IIS 7.0 and the IIS 6.0 Compatibility componentsinstalled.Restart requirementYou mustrestart the computer after you apply this hotfix.Hotfix replacement information This hotfix does not replace any other previously released hotfixes. Registry information To use this hotfix, you do not have to make any changes to the registry. 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.x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformAbocomp.dll7.0.6001.22154209,40810-Apr-200804:57×86Coadmin.dll7.0.6001.2215475,77610-Apr-200804:57×86Iisadmin.dll7.0.6001.2215420,48010-Apr-200804:59×86Iiscfg.dll7.0.6001.22154991,74410-Apr-200804:59×86Inetinfo.exe7.0.6001.2215413,82410-Apr-200803:15×86Infoadmn.dll7.0.6001.2215416,38410-Apr-200804:59×86Infocomm.dll7.0.6001.22154227,32810-Apr-200804:59×86Infoctrs.dll7.0.6001.221549,72810-Apr-200804:59×86Infoctrs.hNot Applicable3,27618-Dec-200721:05Not ApplicableInfoctrs.iniNot Applicable22,87218-Dec-200721:05Not ApplicableIsatq.dll7.0.6001.2215455,29610-Apr-200804:59×86Iscomlog.dll7.0.6001.2215419,96810-Apr-200804:59×86Metadata.dll7.0.6001.22154268,28810-Apr-200805:00×86Rpcref.dll7.0.6001.221547,68010-Apr-200805:02×86Wamreg.dll7.0.6001.2215432,25610-Apr-200805:02×86x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformAbocomp.dll7.0.6001.22154229,88810-Apr-200805:22×64Coadmin.dll7.0.6001.2215482,94410-Apr-200805:23×64Iisadmin.dll7.0.6001.2215424,06410-Apr-200805:25×64Iiscfg.dll7.0.6001.221541,058,30410-Apr-200805:25×64Inetinfo.exe7.0.6001.2215415,87210-Apr-200803:51×64Infoadmn.dll7.0.6001.2215422,52810-Apr-200805:25×64Infocomm.dll7.0.6001.22154270,33610-Apr-200805:25×64Infoctrs.dll7.0.6001.2215412,28810-Apr-200805:25×64Infoctrs.hNot Applicable3,27618-Dec-200721:06Not ApplicableInfoctrs.iniNot Applicable22,87218-Dec-200721:06Not ApplicableIsatq.dll7.0.6001.2215464,51210-Apr-200805:26×64Iscomlog.dll7.0.6001.2215423,04010-Apr-200805:26×64Metadata.dll7.0.6001.22154284,67210-Apr-200805:26×64Rpcref.dll7.0.6001.221549,21610-Apr-200805:28×64Wamreg.dll7.0.6001.2215437,88810-Apr-200805:29×64Abocomp.dll7.0.6001.22154209,40810-Apr-200804:57×86Coadmin.dll7.0.6001.2215475,77610-Apr-200804:57×86Iisadmin.dll7.0.6001.2215420,48010-Apr-200804:59×86Iiscfg.dll7.0.6001.22154991,74410-Apr-200804:59×86Infoadmn.dll7.0.6001.2215416,38410-Apr-200804:59×86Infocomm.dll7.0.6001.22154227,32810-Apr-200804:59×86Infoctrs.dll7.0.6001.221549,72810-Apr-200804:59×86Isatq.dll7.0.6001.2215455,29610-Apr-200804:59×86Iscomlog.dll7.0.6001.2215419,96810-Apr-200804:59×86Metadata.dll7.0.6001.22154268,28810-Apr-200805:00×86Rpcref.dll7.0.6001.221547,68010-Apr-200805:02×86Wamreg.dll7.0.6001.2215432,25610-Apr-200805:02×86IA-64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformAbocomp.dll7.0.6001.22154521,72810-Apr-200805:10IA-64Coadmin.dll7.0.6001.22154193,02410-Apr-200805:12IA-64Iisadmin.dll7.0.6001.2215454,78410-Apr-200805:15IA-64Iiscfg.dll7.0.6001.221541,382,40010-Apr-200805:15IA-64Inetinfo.exe7.0.6001.2215428,16010-Apr-200803:43IA-64Infoadmn.dll7.0.6001.2215440,44810-Apr-200805:15IA-64Infocomm.dll7.0.6001.22154555,00810-Apr-200805:15IA-64Infoctrs.dll7.0.6001.2215424,06410-Apr-200805:15IA-64Infoctrs.hNot Applicable3,27618-Dec-200721:06Not ApplicableInfoctrs.iniNot Applicable22,87218-Dec-200721:06Not ApplicableIsatq.dll7.0.6001.22154139,26410-Apr-200805:15IA-64Iscomlog.dll7.0.6001.2215451,20010-Apr-200805:15IA-64Metadata.dll7.0.6001.22154569,34410-Apr-200805:15IA-64Rpcref.dll7.0.6001.2215414,33610-Apr-200805:18IA-64Wamreg.dll7.0.6001.2215477,31210-Apr-200805:19IA-64Abocomp.dll7.0.6001.22154209,40810-Apr-200804:57×86Coadmin.dll7.0.6001.2215475,77610-Apr-200804:57×86Iisadmin.dll7.0.6001.2215420,48010-Apr-200804:59×86Iiscfg.dll7.0.6001.22154991,74410-Apr-200804:59×86Infoadmn.dll7.0.6001.2215416,38410-Apr-200804:59×86Infocomm.dll7.0.6001.22154227,32810-Apr-200804:59×86Infoctrs.dll7.0.6001.221549,72810-Apr-200804:59×86Isatq.dll7.0.6001.2215455,29610-Apr-200804:59×86Iscomlog.dll7.0.6001.2215419,96810-Apr-200804:59×86Metadata.dll7.0.6001.22154268,28810-Apr-200805:00×86Rpcref.dll7.0.6001.221547,68010-Apr-200805:02×86Wamreg.dll7.0.6001.2215432,25610-Apr-200805:02×86