Jack is Here, asp.net findings

Symptoms
Consider the following scenario:You connect a Windows Server 2008-based computer to a storage device that is controlled by Microsoft Multipath I/O (MPIO).You use a third-party device specific module (DSM) for MPIO.You disconnect all data cables and then reconnect them.In this scenario, access to the storage device fails. Therefore, applications that try to access the storage device crash or receive an exception. This problem persists until you restart the Windows Server 2008-based computer.
Resolution
Hotfix informationImportant Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.
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.PrerequisitesNo prerequisites are required.Restart requirementYou must 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.File information notesThe files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
VersionProductMilestoneService branch6.0.6000.16xxxWindows VistaRTMGDR6.0.6000.20xxxWindows VistaRTMLDR6.0.6001.18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR6.0.6001.22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDRService Pack 1 is integrated into Windows Server 2008.The MANIFEST (.manifest) files and MUM (.mum) files that are installed for each environment are listed separately. MUM and MANIFEST files and their associated security catalog (.cat) files are critical to maintaining the state of the updated component. The security catalog files are signed with a Microsoft digital signature. (The attributes of these files are not listed.)All supported x86-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMpio.infNot applicable3,76004-Feb-200900:45Not applicableMpio.sys6.0.6001.22368104,41604-Feb-200906:06x86All supported x64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMpio.infNot applicable3,76804-Feb-200900:44Not applicableMpio.sys6.0.6001.22368128,48004-Feb-200906:30x64All supported Itanium-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMpio.infNot applicable3,76403-Feb-200923:42Not applicableMpio.sys6.0.6001.22368282,60804-Feb-200905:07IA-64

Symptoms
Consider the following scenario:You have an SQL table that contains an identity column.You start an application that uses a Microsoft ActiveX Data Objects (ADO) client-side Recordset object to access the SQL database. This application calls the UpdateBatch method to insertseveral rows into the table.In this scenario, you find a memory leakoccurs.
If you use Performance Monitor (Perfmon.exe) to monitorapplication processes, you notice that the value of the Private Bytes counter continually increases. This is evidence of a memoryleak.
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.PrerequisitesTo apply this hotfix, your computer must be running one of the following operating systems:Windows Server 2003 Service Pack 2 (SP2)Windows Vista Service Pack 1 (SP1)Windows Vista Service Pack 2 (SP2)Windows Server 2008Windows Server 2008 Service Pack 2 (SP2)Windows 7Windows Server 2008 R2For more information about how to obtain a Windows Server 2003 service pack or a Windows XP Professional x64 Edition service pack, click the following article number to view the article in the Microsoft Knowledge Base:
889100?(http://support.microsoft.com/kb/889100/) How to obtain the latest service pack for Windows Server 2003 For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791?(http://support.microsoft.com/kb/935791/) How to obtain the latest Windows Vista service packFor more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849?(http://support.microsoft.com/kb/968849/) How to obtain the latest service pack for Windows Server 2008Registry informationTo use the hotfix in this package, you do not have to make any changes to the registry.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 informationThe English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.Windows Server 2003 file information noteIn addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.For all supported x86-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll2.82.4635.0356,35211-Dec-200916:48For all supported x64-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMsadce.dll2.82.4635.0622,59211-Dec-200914:42x64Wmsadce.dll2.82.4635.0356,35211-Dec-200914:42x86For all supported IA-64-based versions of Windows Server 2003
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMsadce.dll2.82.4635.01,212,41611-Dec-200914:41IA-64Wmsadce.dll2.82.4635.0356,35211-Dec-200914:41x86Windows Vista and Windows Server 2008 file information notesImportant Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only “Windows Vista” is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows Vista” on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to.The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Collapse this tableExpand this table
VersionProductSR_LevelService branch6.0.600 1.22xxxWindows Vistaand Windows Server 2008SP1LDR6.0.600 2.22xxxWindows Vistaand Windows Server 2008SP2LDRService Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.For all supported x86-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.0.6001.22581454,65611-Dec-200914:53Msadce.dll6.0.6002.22286454,65611-Dec-200914:28For all supported x64-based versions of Windows Server 2008 and ofWindows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.0.6001.22581589,82411-Dec-200915:11Msadce.dll6.0.6002.22286589,82411-Dec-200914:28For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.0.6001.225811,175,55211-Dec-200914:54Msadce.dll6.0.6002.222861,175,55211-Dec-200914:28Windows 7 and Windows Server 2008 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under “Windows 7/Windows Server 2008 R2″ on the page. Always refer to the “Applies To” section in articles to determine the actual operating system that each hotfix applies to.For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.1.7600.20595561,15213-Dec-200908:56For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.1.7600.20595749,56813-Dec-200911:12For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeMsadce.dll6.1.7600.205951,335,29613-Dec-200908:25

Symptoms
On a Windows XP-based or Windows Vista-based computer, you run an application that uses Microsoft XML Core Services (MSXML) 6.0. The application contains a hyperlink control that users can use to open a file or an e-mail message. However, in this scenario, the hyperlink control may fail.
This issue occurs if the following conditions are true:The file URL or the e-mail message URL is encoded in the UTF-8 format.The output is in the HTML format. Note This issue does not occur if the URL starts with http://.
Resolution
XSL Transformation (XSLT) does not recognize the UTF-8-encoded URL because there is no “no-uri-escaping” XSLT flag in MSXML 6.0.

Symptoms
A black screen is displayed after you enter your user credentials in the logon dialog box on a computer that is running Windows Vista or Windows Server 2008. When this issue occurs, you can still move the mouse pointer. However, you cannot start applications such as Windows Explorer. After a while, the operating system stops responding.
Resolution
This issue occurs if an event log is corrupted. In this situation, the Event Log service spins in an infinite loop when you log on.

Symptoms
Windows XP Service Pack 2 (SP2) includes Microsoft Windows Firewall, the updated firewall software thatreplaces Internet Connection Firewall (ICF). If Microsoft Windows Firewall is blocking a port that is used by a service or by a program, you can configure the Windows Firewall to create an exception. Windows Firewall may be blocking a program or a service if the following conditions are true:Programs do not respond to a client’s request.Client programs do not receive data from the server.A Windows Firewall Security Alert may notify you that Windows Firewall is blocking a particular program.When this scenario occurs, you may unblock the program by selecting Unblock this program in the Security Alert dialog box.To help determine which programs and ports are being blocked, you can configure Windows Firewall to log dropped packets.With Windows Firewall Netsh Helper, you can configure Windows Firewall and Windows Firewall logging at the command prompt. Program compatibility may not always be the issue.Group Policy settings can also prevent programs from running. Windows XP Service Pack 2 (SP2) includes several utilities that you can use to troubleshoot Windows Firewall issues.
Resolution
The best way to resolve firewall blocking issues is to modify programs to work with stateful filtering firewalls. If you cannot modify a program, you can configure the Windows Firewall to add exceptions for specific ports and programs. This article discusses the failure symptoms that relate to the default configuration of the Windows XP Service Pack 2 firewall, how to configure exceptions for ports and for programs, and how to perform some troubleshoot methods for firewall settings.