BUG: WebClass Application with Japanese Templates May Fail

This article was previously published under Q304071
This article has been archived. It is offered "as is" and will no longer be updated.
If a WebClass application uses templates that contain Japanese characters and runs on a system where the default language is Japanese, the WebClass application may fail under heavy load. When this occurs, the following entry (or similar) appears in the Application Event log:
WebClass Runtime (0x800A2328)
An internal exception has occurred
NOTE: This error may occur for reasons other than the specific problem that is described in this article. To determine if you are experiencing this specific problem, attach a native code debugger such as Microsoft WinDBG to the process that hosts the WebClass application while it is running to catch the exception on first chance. The call stack should look similar to the following call stack:
0108cc0c 2764a744 0014fd76 00000159 OLEAUT32!SysAllocStringLen+0x7a0108cc24 2764a989 00000003 0014fd76 mswcrun!CTemplItem__SetItem+0x240108cc50 2764b122 00000003 0014fd76 mswcrun!CTemplItems__Add+0x1290108ccf8 2764bc2a 00154e48 03100000 mswcrun!CTemplateFile__ScanTemplate+0x2720108cd8c 27644e6f 00154e48 00110010 mswcrun!CTemplateFile__SendToClient+0x15a0108d02c 3b0c9c6c 00134b3c 00000008 mswcrun!CWebItem__WriteTemplate+0x21f					
Even if you do not have debug symbols available, the main indicator for this problem is that OLEAUT32 appears in the top stack frame, and MSWCRUN appears in a few stack frames below.
This problem occurs because of a bug in the WebClass runtime. The problem may not be reproduced consistently. Although the problem has only been seen on a system in which Japanese is set as the default language and when WebClass applications use templates that contain characters with Shift_JIS encoding, the same problem may occur on systems that are configured for other bi-directional character sets and other character encodings.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

Note You must have a Visual Studio license agreement to obtain this hotfix.

To resolve this problem, 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:Note In 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 should have the following file attributes or later:
   Date       Time    Version      Size     File name        ----------------------------------------------------   3-Jul-2001 01:04    299,008  MSWCRUN.DLL   				

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
WebClass templates are saved as ANSI-encoded files, regardless of whether they contain text that is defined by using a charset such as Shift_JIS. Do not save these templates in Unicode or UTF-8 format, or else they will not render correctly.


The latest version of WinDBG is available from the following Microsoft Windows Debuggers Web site:
bidi crash av access violation 0x800A2328

Article ID: 304071 - Last Review: 02/27/2014 21:09:35 - Revision: 2.3

Microsoft Visual Basic 6.0 Enterprise Edition, Microsoft Visual Basic 6.0 Professional Edition

  • kbnosurvey kbarchive kbbug kbqfe kbwebclasses kbpending KB304071