XWEB: Access Violation in Exprox.dll File on Front-End Server

Article translations Article translations
Article ID: 277903 - View products that this article applies to.
This article was previously published under Q277903
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


When you use Microsoft Outlook Web Access (OWA) to log on to a front-end server and check your mailbox, the Inetinfo process may receive an access violation in the Exprox.dll file. The call stack looks like the following:
ChildEBP RetAddr Args to Child
0dfbf100 0e8bb373 0dfbf134 0e006f6b 000003f2 exprox!CCache<CRCSzi, unsigned short const *>__Lookup+0xb
0dfbf15c 0e8b15c7 0552adfa 00000002 43006f6b exprox!ScNormalizeUrl+0x183
0dfbf288 0e8afa03 0e7f2128 05535360 0e33cb60 exprox!CEcbBaseImpl<IEcb>__LpszRequestUrl+0x157
0dfbf29c 0e8b08eb 00000001 00000000 77e52ee0 exprox!CEcb__FInitialize+0x13
0dfbf2c0 0e8a3f87 0e7f2128 00000001 0dfbf2f8 exprox!NewEcb+0x6b
0dfbf310 0e898448 0e7f2128 00000001 0e7f21f4 exprox!CDAVExt__DwMain+0x67
0dfbf444 657b2468 0e7f2128 0e7f21f4 0e7f2128 exprox!DwExproxExtensionProc+0xa8
0dfbf458 657b29d4 0e7f2128 0e7f21f4 0e7f2128 wam!HSE_APPDLL__ExecuteRequest+0x93
0e7f21f4 00000000 00000000 00000000 00000000 wam!WAM__InvokeExtension+0x35


This problem occurs if the URL contains a character that is not a Ucs Transformation Format 8 (UTF 8) character. The Exprox.dll file checks the language-ID to code page-ID mapping cache for the code page ID. Because the cache is not initialized, the Exprox.dll file stops responding.


To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: HTTP-DAV

Collapse this tableExpand this table
File nameVersion


Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.


Article ID: 277903 - Last Review: October 21, 2013 - Revision: 1.3
  • Microsoft Exchange 2000 Server Standard Edition
kbnosurvey kbarchive kbbug kbfix kbqfe KB277903

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com