SqlCeException thrown with NO information on a particular device type

Discussion in 'microsoft.public.sqlserver.ce' started by news.microsoft.com, Jun 22, 2009.

  1. We are currently fighting with a really strange error using SQLServer CE
    under a particular type of device running Windows CE 5 and .NET compact
    Framework 2.0 SP2.
    The problem occurs with SQLCE 3.1 and also with 3.5.

    At a particular stage of our aplication (which is always located at the
    exact same location in the code. but, could occur between 1 and 10 minutes
    of activity) the following exception is thrown by the SQL Engine:
    type=System.Data.SqlServerCe.SqlCeException ; message= <NULL>
    Stack Trace ...
    at System.Data.SqlServerCe.SqlCeCommand.ProcessResults()
    at System.Data.SqlServerCe.SqlCeCommand.InitializeCommand()
    at System.Data.SqlServerCe.SqlCeCommand.ExecuteCommand()
    at System.Data.SqlServerCe.SqlCeCommand.ExecuteNonQuery()
    at ....... <our own stack...>

    Detail exception is: SqlCeException details: Message:<NULL> ;Native Error:
    0; ToString(): System.Data.SqlServerCe.SqlCeError

    The query making the problem is: UPDATE Configuration SET value =
    (@counterValue) WHERE ROWID = (@idRow) AND value = (@oldValue)
    where @counterValue value:1 type:Int64 | name:mad:idRow value:10 type:Int64
    | @oldValue value:0 type:Int64

    Our dB is located on an SD card. To be sure it is not related to a problem
    accessing the card, we moved the dB to the SRAM (removed at each startup).
    The exact same problem occured as well.

    Does anyone have a clue when a SqlCeException with no information at all can
    be thrown can be thrown!

    news.microsoft.com, Jun 22, 2009
    1. Advertisements

  2. news.microsoft.com

    space_cowboy Guest


    I have noticed that I get empty exception messges when sqlceerxxEN.dll is
    either not properly installed or unavailable. xx would be 30 in the case of
    SQLCE3.1 and
    35 in the case of SQLCE 3.5
    space_cowboy, Jun 22, 2009
    1. Advertisements

  3. Laxmi Narsimha Rao Oruganti [MSFT], Jun 29, 2009
  4. Sorry for not replying earlier to this thread...

    In fact, after further analysis, we have found the cause of our problem:
    This was occuring when the Virtual Memory available was nearly 0.

    In such a situation, it will be really good if the exception thrown will be
    a kind of "out of memory" exception :)

    news.microsoft.com, Aug 6, 2009
  5. In this particular case, my *super wild* guess is that may be we were not
    able to allocate memory to load the error string :(.

    Laxmi Narsimha Rao Oruganti [MSFT], Aug 19, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.