Access Violation errors

Discuss a software development with IBProvider

Access Violation errors

Postby Evangelia » 13 Feb 2019, 00:47

Hi, we get an error from a vb.net app connectiong to Interbase 2017 . Anyone seen something like this, any suggestions? The same app runs correct in other servers and it has the problem only with IB 2017. With previous versions Interbase we never had the same issue.

Exception Info: System.AccessViolationException
at System.Data.Common.UnsafeNativeMethods+ICommandText.Execute(IntPtr, System.Guid ByRef, System.Data.OleDb.tagDBPARAMS, IntPtr ByRef, System.Object ByRef)
at System.Data.OleDb.OleDbCommand.ExecuteCommandTextForSingleResult(System.Data.OleDb.tagDBPARAMS, System.Object ByRef)
at System.Data.OleDb.OleDbCommand.ExecuteCommandText(System.Object ByRef)
at System.Data.OleDb.OleDbCommand.ExecuteCommand(System.Data.CommandBehavior, System.Object ByRef)
at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(System.Data.CommandBehavior, System.String)
at System.Data.OleDb.OleDbCommand.ExecuteReader(System.Data.CommandBehavior)
at System.Data.OleDb.OleDbCommand.System.Data.IDbCommand.ExecuteReader(System.Data.CommandBehavior)
at System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet, System.Data.DataTable[], Int32, Int32, System.String, System.Data.IDbCommand, System.Data.CommandBehavior)
at System.Data.Common.DbDataAdapter.Fill(System.Data.DataTable[], Int32, Int32, System.Data.IDbCommand, System.Data.CommandBehavior)
at System.Data.Common.DbDataAdapter.Fill(System.Data.DataTable)
at TransformXml.FMain.GetNext_ID(System.String)
at TransformXml.FMain.Transfer_BetradarLivescoreData(Int32 ByRef, System.String ByRef)
at TransformXml.FMain.DoAction()
at TransformXml.FMain.Timer_Tick(System.Object, System.EventArgs)
at System.Windows.Forms.Timer.OnTick(System.EventArgs)
at System.Windows.Forms.Timer+TimerNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(System.String[])
at TransformXml.My.MyApplication.Main(System.String[])
Evangelia
 
Posts: 3
Joined: 17 Sep 2014, 15:31

Re: Access Violation errors

Postby Kovalenko Dmitry » 13 Feb 2019, 09:52

Hello,

You can reproduce this problem in small, isolated program?

Try to get stack with list of all DLLs (not only managed).
Kovalenko Dmitry
Site Admin
 
Posts: 846
Joined: 17 Nov 2005, 20:51
Location: Russia, Lipetsk

Re: Access Violation errors

Postby Kovalenko Dmitry » 13 Feb 2019, 11:31

Try to use another gds32.dll / ibclient64.dll modules.

You may define server client through following initialize properties: dbclient_library, dbclient_library_64.
Kovalenko Dmitry
Site Admin
 
Posts: 846
Joined: 17 Nov 2005, 20:51
Location: Russia, Lipetsk

Re: Access Violation errors

Postby Evangelia » 13 Feb 2019, 16:12

Hi Dimitri, thank you for helping, we are in progress to create a reproduce example together with a database. For your other suggestion, to define a different client library: there is only one clent version installed but we will try just in case. Will send reproduce results as soon as we have it ready.
Evangelia
 
Posts: 3
Joined: 17 Sep 2014, 15:31

Re: Access Violation errors

Postby Evangelia » 14 Feb 2019, 20:55

Hi, update on this issue: To avoid the possibility of .net versions mismatch being the reason, the programs have been rebuild to exactly the same .net version as in the production server. After rebuild there are no new errors, but we need to wait 2-3 days to conclude that .net framework version was the problem. Thanks again for trying to help and sorry if it the problem was irrelevant with ibprovider
Evangelia
 
Posts: 3
Joined: 17 Sep 2014, 15:31


Return to Programming with IBProvider

Who is online

Users browsing this forum: No registered users and 1 guest

cron