Jack is Here, asp.net findings

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

Symptoms
An access violation in Lsasrv.dll may cause a Windows 2000-based server to become unresponsive. When this problem occurs, the server does not accept connections, and the server becomes unstable. The following event is recorded in the event log:

Event Type: Error
Event Source: LsaSrv
Event Category: Devices
Event ID: 5000
Date: date
Time: time
User: N/A
Computer: SERVERNAME
Description:
The security package Negotiate generated an exception. The package is now disabled.
The exception information is the data.
Data:
0000: c0000005 00000000 00000000 77f83941
0010: 00000002 00000001 00000010 0001003f
0020: 00000000 00000000 00000000 00000000
0030: 00000000 00000000 ffff027f ffff0000
0040: ffffffff 00000000 00780000 00000000
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
260910?(http://support.microsoft.com/kb/260910/) How to obtain the latest Windows 2000 service pack
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.
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, submit a request to 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. The English version of this fix has the file attributes(or later) that are listed in the following table. The dates and times forthese files are listed in coordinated universal time (UTC). When you view thefile information, it is converted to local time. To find the difference betweenUTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

DateTimeVersionSizeFile name——————————————————–09-Dec-200222:145.0.2195.6109124,688Adsldp.dll09-Dec-200222:145.0.2195.5781131,344Adsldpc.dll09-Dec-200222:145.0.2195.610962,736Adsmsext.dll09-Dec-200222:145.0.2195.6143358,672Advapi32.dll09-Dec-200222:145.0.2195.609449,936Browser.dll09-Dec-200222:145.0.2195.6143135,952Dnsapi.dll09-Dec-200222:145.0.2195.613496,016Dnsrslvr.dll09-Dec-200222:145.0.2195.612545,328Eventlog.dll09-Dec-200222:145.0.2195.6137147,216Kdcsvc.dll22-Nov-200218:455.0.2195.6137203,536Kerberos.dll21-Aug-200216:275.0.2195.602371,248Ksecdd.sys09-Dec-200222:045.0.2195.6155507,664Lsasrv.dll09-Dec-200222:045.0.2195.615533,552Lsass.exe22-Nov-200218:205.0.2195.6137109,328Msv1_0.dll09-Dec-200222:145.0.2195.5979307,472Netapi32.dll09-Dec-200222:145.0.2195.6075360,720Netlogon.dll09-Dec-200222:145.0.2195.6136921,872Ntdsa.dll09-Dec-200222:145.0.2195.6147389,392Samsrv.dll09-Dec-200222:145.0.2195.6120130,320Scecli.dll09-Dec-200222:145.0.2195.6120303,888Scesrv.dll06-Dec-200201:435.0.2195.6152146,432Sp3res.dll09-Dec-200222:145.0.2195.585948,912W32time.dll04-Jun-200221:325.0.2195.585957,104W32tm.exe09-Dec-200222:145.0.2195.6100126,224Wldap32.dll09-Dec-200222:045.0.2195.6155507,664Lsasrv.dll

Symptoms
Consider the following scenario. On a computer that has .NET Framework 3.5 Service Pack 1 (SP1) installed, you run an ASP.NET Web service application that is hosted on Internet Information Services (IIS). You use a Windows Presentation Foundation (WPF)-based application to generate content context for the Web Site or Web service, for example, images. In this scenario, when you try to access the WPF application by browsing the Web service, you may receive the following message:

A first chance exception of type ‘System.Runtime.InteropServices.COMException’ occurred in PresentationCore.dll
Additional information: The program issued a command but the command length is incorrect. (Exception from HRESULT: 0×80070018)
Resolution
When the WPF application calls the NtRequestWaitReplyPort function to dispatch a message through a local procedure call (LPC) to Windows Manager Session Manager service (UXSMS) in the DwmGetTransportAttributes function, the E_ACCESSDENIED exception is returned. Then, the DwmGetTransportAttributes function tries to decode the message. However, the message was never handled because it is not a valid packet. Therefore, the code returns E_INVALID_COMMAND_LENGTH and triggers the exception.

Symptoms
You may receive “out of memory” exception error messages, although as much as 2 gigabytes (GB) of physical memory is still available. This problem is most likely to occur when stress levels are reached and when you are using many large objects (objects that are over 85 kilobytes [KB]).
Resolution
To resolve this problem, obtain the latest service pack for .NET Framework 1.1. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
885055?(http://support.microsoft.com/kb/885055/) How to obtain Microsoft .NET Framework 1.1 Service Pack 1