Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> Yet another Sybase ASE issue
 

Pages: 1
Bugs & Issues
Yet another Sybase ASE issue
Page:1/1 

  Print all messages in this thread  
Poster Message
kerpal
User



Location:

Joined on:
16-May-2008 07:32:34
Posted:
14 posts
# Posted on: 17-Jun-2008 09:14:02.  
I have a table with a few fields of type "text". When trying to read/write to these I get the following exception:

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Line 252:            using (DataAccessAdapter adapter = new DataAccessAdapter())
Line 253:            {
Line 254:                adapter.FetchEntityCollection(sectionQuestion, filter, 0, sortQ, pathSQ);
Line 255:            }
Line 256:

Stack Trace:

[AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.]
?.?(IntPtr A_0, IntPtr A_1) +0
Sybase.Data.AseClient.AseCommand.?(Boolean A_0) +164
Sybase.Data.AseClient.AseCommand.?(Boolean A_0) +359
Sybase.Data.AseClient.AseCommand.?() +25
Sybase.Data.AseClient.AseCommand.Dispose(Boolean disposing) +109
System.ComponentModel.Component.Dispose() +14
SD.LLBLGen.Pro.ORMSupportClasses.Query.Dispose(Boolean isDisposing) +363
SD.LLBLGen.Pro.ORMSupportClasses.Query.Dispose() +28
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.FetchEntityCollectionInternal(IEntityCollection2 collectionToFill, IRelationPredicateBucket& filterBucket, Int32 maxNumberOfItemsToReturn, ISortExpression sortClauses, ExcludeIncludeFieldsList excludedIncludedFields, Int32 pageNumber, Int32 pageSize) +994
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.FetchPrefetchPath(IEntityCollection2 rootEntities, IRelationPredicateBucket filterBucket, Int64 maxNumberOfItemsToReturn, ISortExpression sortClauses, IPrefetchPath2 prefetchPath, Boolean forceParameterizedPPath) +1742
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.FetchEntityCollection(IEntityCollection2 collectionToFill, IRelationPredicateBucket filterBucket, Int32 maxNumberOfItemsToReturn, ISortExpression sortClauses, IPrefetchPath2 prefetchPath, ExcludeIncludeFieldsList excludedIncludedFields, Int32 pageNumber, Int32 pageSize) +363
SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.FetchEntityCollection(IEntityCollection2 collectionToFill, IRelationPredicateBucket filterBucket, Int32 maxNumberOfItemsToReturn, ISortExpression sortClauses, IPrefetchPath2 prefetchPath) +53


I realise this is probably another Sybase ASE adapter bug ... Can you recommend any way to work around this issue?

Many thanks in advance.
  Top
Walaa
Support Team



Location:

Joined on:
21-Aug-2005 16:03:48
Posted:
14572 posts
# Posted on: 17-Jun-2008 10:39:24.  
Quote:
Sybase.Data.AseClient.AseCommand.Dispose(Boolean disposing) +109

That's a nasty one, in the Dispose() of the AseCommand, I don't think there is anyhing we can do from our side.


  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.