Article ID: 2417591 - Last Review: October 15, 2010 - Revision: 2.0

An application that establishes a RAS connection on a Windows Embedded CE 6.0 R3-based device may crash after an access violation occurs in the Ndsil.dll component

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

On This Page

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:
  • You run an application that establishes a Remote Access Service (RAS) connection on a Windows Embedded CE 6.0 R3-based device.
  • The application calls the RasHangUp function immediately after it calls the RasDial function.

In this scenario, an access violation exception may occur in the Ndsil.dll component, and then the application crashes.

CAUSE

This problem occurs because the Network Driver Interface Specification (NDIS) code in the RasHangUp function drops all pending requests before the Layer Two Tunneling Protocol (L2TP) handler in the RasDial function finishes the OID_TAPI_MAKE_CALL pending request. Then, the access violation exception occurs.

RESOLUTION

Software update information

A supported software update is now available from Microsoft as Windows Embedded CE 6.0 Platform Builder Monthly Update (September 2010). You can confirm this by scrolling to the "File information" section. The package file name contains the product version, date, Knowledge Base article number, and processor type. The package file name format is as follows:
Product version-yymmdd-kbnnnnnn-processor type
For example: Wincepb50-060503-kb917590-armv4i.msi is the ARMV4i Windows CE 5.0 Platform Builder fix that is documented in KB article 917590 and that is contained in the May 2006 monthly update. To resolve this problem immediately, click the following article number for information about how to obtain Windows CE Platform Builder and core operating system software updates:
837392  (http://support.microsoft.com/kb/837392/ ) How to locate core operating system fixes for Microsoft Windows CE Platform Builder products

Prerequisites

This update is supported only if all previously issued software updates for this product have also been applied.

Restart information

To resolve this problem, apply this update. After you apply this update, you must perform a clean build of the whole platform.

To do this, use one of the following methods:
  • On the Build menu, click Clean Solution, and then click Build Solution.
  • On the Build menu, click Rebuild Solution.
You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update 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.

Files that are included in this update package
Collapse this tableExpand this table
File nameFile sizeDateTimePath
Windows embedded ce 6.0_update_kb2417591.htm7,87027-Sep-201018:38100927_kb2417591
Ppp.c59,72321-Sep-201014:52Private\Winceos\Comm\Ppp2\Ppp\App
L2tp.lib905,96021-Sep-201014:51Public\Common\Oak\Lib\Armv4i\Debug
Ppp2app.lib502,63021-Sep-201014:51Public\Common\Oak\Lib\Armv4i\Debug
Ppp2app.res76821-Sep-201014:51Public\Common\Oak\Lib\Armv4i\Debug
L2tp.lib529,39621-Sep-201014:51Public\Common\Oak\Lib\Armv4i\Retail
Ppp2app.lib316,10021-Sep-201014:51Public\Common\Oak\Lib\Armv4i\Retail
Ppp2app.res76821-Sep-201014:51Public\Common\Oak\Lib\Armv4i\Retail
L2tp.lib861,93821-Sep-201014:51Public\Common\Oak\Lib\Mipsii\Debug
Ppp2app.lib481,66221-Sep-201014:51Public\Common\Oak\Lib\Mipsii\Debug
Ppp2app.res76821-Sep-201014:51Public\Common\Oak\Lib\Mipsii\Debug
L2tp.lib525,89421-Sep-201014:51Public\Common\Oak\Lib\Mipsii\Retail
Ppp2app.lib313,40021-Sep-201014:51Public\Common\Oak\Lib\Mipsii\Retail
Ppp2app.res76821-Sep-201014:51Public\Common\Oak\Lib\Mipsii\Retail
L2tp.lib862,16821-Sep-201014:51Public\Common\Oak\Lib\Mipsii_fp\Debug
Ppp2app.lib481,75821-Sep-201014:51Public\Common\Oak\Lib\Mipsii_fp\Debug
Ppp2app.res76821-Sep-201014:51Public\Common\Oak\Lib\Mipsii_fp\Debug
L2tp.lib526,15021-Sep-201014:51Public\Common\Oak\Lib\Mipsii_fp\Retail
Ppp2app.lib313,47821-Sep-201014:51Public\Common\Oak\Lib\Mipsii_fp\Retail
Ppp2app.res76821-Sep-201014:51Public\Common\Oak\Lib\Mipsii_fp\Retail
L2tp.lib868,59221-Sep-201014:52Public\Common\Oak\Lib\Mipsiv\Debug
Ppp2app.lib485,90621-Sep-201014:52Public\Common\Oak\Lib\Mipsiv\Debug
Ppp2app.res76821-Sep-201014:52Public\Common\Oak\Lib\Mipsiv\Debug
L2tp.lib531,76821-Sep-201014:51Public\Common\Oak\Lib\Mipsiv\Retail
Ppp2app.lib317,35421-Sep-201014:52Public\Common\Oak\Lib\Mipsiv\Retail
Ppp2app.res76821-Sep-201014:52Public\Common\Oak\Lib\Mipsiv\Retail
L2tp.lib868,82421-Sep-201014:52Public\Common\Oak\Lib\Mipsiv_fp\Debug
Ppp2app.lib486,00621-Sep-201014:52Public\Common\Oak\Lib\Mipsiv_fp\Debug
Ppp2app.res76821-Sep-201014:52Public\Common\Oak\Lib\Mipsiv_fp\Debug
L2tp.lib532,02421-Sep-201014:52Public\Common\Oak\Lib\Mipsiv_fp\Retail
Ppp2app.lib317,43621-Sep-201014:52Public\Common\Oak\Lib\Mipsiv_fp\Retail
Ppp2app.res76821-Sep-201014:52Public\Common\Oak\Lib\Mipsiv_fp\Retail
L2tp.lib733,57821-Sep-201014:52Public\Common\Oak\Lib\Sh4\Debug
Ppp2app.lib434,67021-Sep-201014:52Public\Common\Oak\Lib\Sh4\Debug
Ppp2app.res76821-Sep-201014:52Public\Common\Oak\Lib\Sh4\Debug
L2tp.lib484,95221-Sep-201014:52Public\Common\Oak\Lib\Sh4\Retail
Ppp2app.lib294,97621-Sep-201014:52Public\Common\Oak\Lib\Sh4\Retail
Ppp2app.res76821-Sep-201014:52Public\Common\Oak\Lib\Sh4\Retail
L2tp.lib751,46821-Sep-201014:50Public\Common\Oak\Lib\X86\Debug
Ppp2app.lib428,06621-Sep-201014:50Public\Common\Oak\Lib\X86\Debug
Ppp2app.res76821-Sep-201014:50Public\Common\Oak\Lib\X86\Debug
L2tp.lib495,88421-Sep-201014:50Public\Common\Oak\Lib\X86\Retail
Ppp2app.lib287,57221-Sep-201014:50Public\Common\Oak\Lib\X86\Retail
Ppp2app.res76821-Sep-201014:50Public\Common\Oak\Lib\X86\Retail

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

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


APPLIES TO
  • Windows Embedded CE 6.0 R3
Keywords: 
kbqfe kbhotfixserver kbfix kbexpertiseinter kbprb kbsurveynew kbbug KB2417591