This question is locked. New answers and comments are not allowed.
Hello,
on one PC we get the following error:
Error executing query: System.AccessViolationException: Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist.
bei Telerik.OpenAccess.RT.Adonet2Generic.Impl.PreparedStatementImp.executeQuery()
bei OpenAccessRuntime.Relational.conn.PooledPreparedStatement.executeQuery()
bei OpenAccessRuntime.Relational.fetch.FetchResultImp.Execute()
It just happens on one PC. It is not a debug Version. We use a SQL Server 2008 R2 as database. We testet it with different Telerik OA Versions:
With the Version 2010.3.1125.1 in the past the error did not occur. Maybe it is because of the version, maybe because of any Change in the program.
Since Version 2011.2.1021.1 the error occurs. We also tested the version 2012.2.xxx, the error is still there.
The SQL is not complex and the result would be small, so it is not because of a lot of data.
Any suggestions what can cause this error?
Kind Regards
Andreas
on one PC we get the following error:
Error executing query: System.AccessViolationException: Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist.
bei Telerik.OpenAccess.RT.Adonet2Generic.Impl.PreparedStatementImp.executeQuery()
bei OpenAccessRuntime.Relational.conn.PooledPreparedStatement.executeQuery()
bei OpenAccessRuntime.Relational.fetch.FetchResultImp.Execute()
It just happens on one PC. It is not a debug Version. We use a SQL Server 2008 R2 as database. We testet it with different Telerik OA Versions:
With the Version 2010.3.1125.1 in the past the error did not occur. Maybe it is because of the version, maybe because of any Change in the program.
Since Version 2011.2.1021.1 the error occurs. We also tested the version 2012.2.xxx, the error is still there.
The SQL is not complex and the result would be small, so it is not because of a lot of data.
Any suggestions what can cause this error?
Kind Regards
Andreas
1 Answer, 1 is accepted
0
Hi Andreas,
while googling/binging this up (http://social.msdn.microsoft.com/Forums/en-US/sqlce/thread/fd60ba69-e4d6-441a-901f-947ac7a46d3c/), I came to the idea that this could be caused with by mismatch between the managed and the unmanaged parts of the MS SqlClient. In OpenAccess, we are not using unmanaged code, all is MSIL. However, if a driver consists of parts in both worlds, a mismatch could lead to such effects.
Can you check that, and ensure also that the failing maching has all updates? Maybe you can see the version numbers of the assemblies too.
Greetings,
Thomas
the Telerik team
while googling/binging this up (http://social.msdn.microsoft.com/Forums/en-US/sqlce/thread/fd60ba69-e4d6-441a-901f-947ac7a46d3c/), I came to the idea that this could be caused with by mismatch between the managed and the unmanaged parts of the MS SqlClient. In OpenAccess, we are not using unmanaged code, all is MSIL. However, if a driver consists of parts in both worlds, a mismatch could lead to such effects.
Can you check that, and ensure also that the failing maching has all updates? Maybe you can see the version numbers of the assemblies too.
Greetings,
Thomas
the Telerik team
Telerik OpenAccess ORM Meets ASP.NET Web API. Read more.