Article ID: 928452 - Last Review: December 3, 2007 - Revision: 1.5 FIX: In IIS 6.0, Script Debugger breaks on an incorrect line of code when you debug an ASP page that contains double-byte characters
On This PageSYMPTOMSConsider the following scenario. You debug an Active Server Pages (ASP) page that is running in Microsoft Internet Information Services (IIS) 6.0. The ASP page contains double-byte characters. In this scenario, Microsoft Script Debugger breaks on an incorrect line of code. CAUSEThis problem occurs because the double-byte characters cause the Asp.dll file to return an incorrect offset. The number of double-byte characters that the ASP page contains directly affects the offset that the Asp.dll file returns. For example, if an ASP page contains many double-byte characters, the debug breakpoint occurs on a line of code that is far away from the expected line of code. RESOLUTIONHotfix informationA 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 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.PrerequisitesYou must be running either Windows Server 2003 with Service Pack 2 (SP2) or Windows Server 2003 with Service Pack 1 (SP1) 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.Windows Server 2003, x86-based versionsCollapse this table
Windows Server 2003, x64-based versionsCollapse this table
Windows Server 2003, Itanium-based versionsCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about character sets, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/library/ms776430.aspx
(http://msdn2.microsoft.com/en-us/library/ms776430.aspx)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
