FIX: Access violations occur when you run an application under heavy load conditions after you install the 64-bit version SQL Server Compact 3.5 Service Pack 1

Extended support for SQL Server 2005 ended on April 12, 2016

If you are still running SQL Server 2005, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
Consider the following scenario:
  • You install the 64-bit version of Microsoft SQL Server Compact 3.5 Service Pack 1 (SP1) on a computer that has more than 4 GB of memory.
  • You have an application that accesses the SqlCeDataReader object.
  • The application runs under heavy load conditions.
In this scenario, access violations may occur intermittently. Additionally, when these access violations occur, you receive the following error message:
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
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: 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.

Prerequisites

You must have the 32-bit version of SQL Server Compact 3.5 Service Pack 1 installed on your computer before you install this hotfix.

To obtain the 32-bit version of SQL Server Compact 3.5 Service Pack 1, visit the following Microsoft Download Web site:

http://www.microsoft.com/downloads/details.aspx?FamilyId=DC614AEE-7E1C-4881-9C32-3A6CE53384D9

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

How to install this hotfix

To install this hotfix, follow these steps:
  1. Uninstall the 64-bit version of SQL Server Compact 3.5 Service Pack 1.
    Note After you uninstall the 64-bit version of SQL Server Compact 3.5 Service Pack 1, the 32-bit version of SQL Server Compact 3.5 Service Pack 1 is still installed on your computer.
  2. Install the hotfix.

File information

The 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.
SQL Server Compact 3.5 64-bit version
File nameFile versionFile sizeDateTimePlatform
Sqlceca35.dll3.5.5692.9573,85608-May-200921:25x64
Sqlcecompact35.dll3.5.5692.9117,66408-May-200921:25x64
Sqlceer35en.dll3.5.5692.9146,84008-May-200921:25x64
Sqlceme35.dll3.5.5692.986,42408-May-200921:25x64
Sqlceoledb35.dll3.5.5692.9258,46408-May-200921:25x64
Sqlceqp35.dll3.5.5692.91,131,93608-May-200921:25x64
Sqlcese35.dll3.5.5692.9642,97608-May-200921:25x64
System.data.sqlserverce.entity.dll3.5.5692.9228,27208-May-200920:33x86
System.data.sqlserverce.dll3.5.5692.9269,23208-May-200920:33x86
System.data.sqlserverce.dll3.5.5692.9269,23208-May-200920:34x86
System.data.sqlserverce.entity.dll3.5.5692.9228,27208-May-200920:34x86
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More information

Stack dump information

at System.String.wcslen(Char* ptr)at System.String.CtorCharPtr(Char* ptr)at System.Data.SqlServerCe.Accessor.get_Value()at System.Data.SqlServerCe.SqlCeDataReader.FetchValue(Int32 index)at System.Data.SqlServerCe.SqlCeDataReader.IsDBNull(Int32 ordinal)at System.Data.SqlServerCe.SqlCeDataReader.GetValue(Int32 ordinal)at System.Data.SqlServerCe.SqlCeDataReader.get_Item(Int32 index)
References
For more information about the Incremental Servicing Model, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
AccessViolationException memory SqlCeDataReader
Properties

Article ID: 970269 - Last Review: 01/16/2015 03:45:00 - Revision: 3.0

Microsoft SQL Server Compact 3.5

  • kbnosurvey kbarchive kbsurveynew kbHotfixServer kbautohotfix kbexpertiseadvanced kbqfe kbfix KB970269
Feedback