Sybase: Attempted to read or write protected memory
Joined: 14-Mar-2007
Version 2.5 June 2nd 2008 (v2.0.50727 runtime ver) Sybase.Data.AseClient 1.15.152.0
When trying to insert a column into a table with a "text" field I get the following exception...
System.AccessViolationException was caught Message="Attempted to read or write protected memory. This is often an indication that other memory is corrupt." Source="Sybase.Data.AseClient" StackTrace: at ᜀ.ᜀ(IntPtr A_0, IntPtr A_1) at Sybase.Data.AseClient.AseCommand.ᜀ(Boolean A_0) at Sybase.Data.AseClient.AseCommand.ᜁ(Boolean A_0) at Sybase.Data.AseClient.AseCommand.ᜅ() at Sybase.Data.AseClient.AseCommand.Dispose(Boolean disposing) at System.ComponentModel.Component.Dispose() at SD.LLBLGen.Pro.ORMSupportClasses.Query.Dispose(Boolean isDisposing) at SD.LLBLGen.Pro.ORMSupportClasses.ActionQuery.Dispose(Boolean isDisposing) at SD.LLBLGen.Pro.ORMSupportClasses.Query.Dispose() at SD.LLBLGen.Pro.ORMSupportClasses.BatchActionQuery.Dispose(Boolean isDisposing) at SD.LLBLGen.Pro.ORMSupportClasses.BatchActionQuery.Dispose() at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.PersistQueue(List`1 queueToPersist, Boolean insertActions, Int32& totalAmountSaved) at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave, Boolean refetchAfterSave, IPredicateExpression updateRestriction, Boolean recurse) at SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.SaveEntity(IEntity2 entityToSave) at Phase3Messaging.Form1.button3_Click(Object sender, EventArgs e) in C:\work\1cid\src\2cmm\Phase3Messaging\Phase3Messaging\Form1.cs:line 417 InnerException:
Here's the code...
P3ConnectionErrorsEntity logerror = new P3ConnectionErrorsEntity();
logerror.MsgSource = "The Source";
logerror.MsgShortText = "The Short Text";
logerror.MsgLongText = "The Long long long long Long long long long Long long long long Long long long long Long long long long text";
try
{
// Now add the new log error to the Database...
using (DataAccessAdapter adapter = new DataAccessAdapter(AppConfiguration.DBConnectionString))
{
adapter.SaveEntity(logerror);
}
}
catch (Exception ex)
{
MessageBox.Show(ex.ToString());
}
Here's the Table DDL...
CREATE TABLE dbo.P3ConnectionErrors (
msgSeq numeric(18,0) IDENTITY NOT NULL,
msgDateTime datetime DEFAULT GETDATE() NOT NULL,
msgSource varchar(20) NOT NULL,
msgShortText varchar(255) NOT NULL,
msgLongText text NULL
)
If I do not set the logerror.MsgLongText (text) field, the insert succeeds.
It looks like something with cleaning up unmanaged resources, I know you are all shocked that Sybase data provider would have bugs.
Anyway, is this similar to the OleDB issure resolved here...
http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=14061&HighLight=1
Maybe through the magic of LLBLGen a work around could be provided?
Thanks!
Troy
Joined: 14-Mar-2007
David,
Thanks for the response! I was able to resolve the error you refered to in the link.
This new excpetion does have the same error message, but a different call stack. It appears like an object is being disposed of twice, similar to the OleDB thread I had linked to. Was hoping it was something you guys could easily reproduce it and potentially have a work around for it! If not, I'll need to come up with another non text table structure.
I think we all know the response I'll get from Sybase 
Thanks,
Troy
We have 1.15.320 as ase driver dll version, so they have a newer version for you. Could you try that newer ASE provider dll first please? (it's from june 2008, so I think there's likely a newer that that one)
We also found another thread which could be related, which was about a bugfix in 2.6, (which caused the issue to pop up in ms access). Could you try the latest runtime libs from 2.5 as well ? (you posted the .net version number btw ). That error only occured in selfservicing btw, so it's likely not related...
Joined: 14-Mar-2007
Joined: 14-Mar-2007
Joined: 23-Aug-2009