Devart Forums

Hello,

Using the latest Entity Developer version & latest Azure version, i can successfully connect to a database. Neverthless, when i try to Update Model from Database i get a "Invalid object name 'sys.extended_properties'." error.

Exception Info: System.AccessViolationException
Stack:
at Devart.Data.Linq.Provider.DataProvider.ExecuteQuery(CompiledQuery, System.Object[], System.Object[], System.Object)
at Devart.Data.Linq.Provider.DataProvider.ExecuteAllQueries(CompiledQuery, System.Object[])

Exception Info: System.InvalidOperationException
Stack:
at Devart.Common.DbConnectionInternal.d(System.Object)
at Devart.Common.DbConnectionPoolGroup.a(Devart.Common.DbConnectionPool)
at Devart.Common.DbConnectionPoolGroup.a(System.Object)
at System.Threading.ExecutionContext.runTryCode(System.Object)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode, CleanupCode, System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading._TimerCallback.PerformTimerCallback(System.Object)


Exception Info: System.AccessViolationException
Stack:
at Devart.Data.Linq.Provider.ObjectReader`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].k()
at Devart.Data.Linq.Provider.k+a.d()
at Devart.Data.Linq.Provider.k.e()
at Devart.Data.Linq.Provider.DataProvider.Dispose(Boolean)
at Devart.Data.Linq.DataContext.Dispose()

After a long testing of this personalized version in out heavy-duty production system, i still get these errors but with a lot less frequency. Now, i get them maybe 1 every week or something. You are definitely seem to be on the right track but not quite there yet. Can you do something better?

I found the cause of the bug. In the lqml xml file, the default value attribute was saved as :

DefaultValue="1
"

instead of DefaultValue="1". I don't know how this ended up in there! In the entity developer designer, the default value property looks correctly to be '1'. Maybe after the first Update Model from Database, when the new property or entire class is generated for the first time? It seems to be it. Anyway, i replaced all the aforementioned instances in the text file, and everything works ok now.

I know it's a bit odd, but it's true! And it is very annoying because i used to generate code in my project folder and now i switched back to generating the code to an other folder and copy only the entities that changed, because the number of broken files is too big to fix it by hand.

The template is the LinqConnect C#. I generate each entity per file. I don't know if this helps, and is a bit odd, but for a property that the default enum value is '0' everything works as expected! Only for the ones that the default value is '1' it brakes.

Also, it changes the Name of the property back to the auto-generated one from the name of the column.

Hello,

Using the latest Entity Developer, when updating the Model from Database in an Oracle system, and a minor change for an Enum property is propagated, the Entity looses the assigned Enum Type and changes back to the original Boolean type for a NUMBER(1) server type. E.g. I have a NUMBER(1) column and i set the type of the relevant property in Entity Developer to a custom Enum i created and maintained. Afterwords, i had to change the Default value of the column from none to '1'. I try to Update Model from Database and Entity Developer correctly recognizes the change. Nevertheless, it looses the Enum type already set and it changes my property type back to System.Boolean.

Hello,

Using the latest version of LinqConnect, for some Enum-typed properties that a default value is specified, the generated code is falsely broken in 2 lines e.g. as follows:

private CompanySubtypeEnum _Subtype = (CompanySubtypeEnum)Enum.Parse(typeof(CompanySubtypeEnum), "1
");

First line goes up to and the rest goes to a second line that brakes the code.

Next line on stack trace is my LINQ to SQL query that uses this table. Same line is executed successfully in 1000 times and in 1 of them, i get this error.

Query is the following:

var invoices = from objInvoice in context.Invoices
where objInvoice.CuId == anonmeter.CustomerId
&& objInvoice.AffBal == "1"
&& (from objUdfValue in context.UdfsValues
where objUdfValue.UdfId == InvoiceSupplyNoUDFId
&& objUdfValue.Value.Substring(0, 4000) == anonmeter.Meter
select objUdfValue.RefId).Contains(
objInvoice.Id)
select new
{
TransactionValue = objInvoice.TotalCharge,
TransactionDate = objInvoice.Date,
TransactionType = TransactionTypeEnum.Invoice,
TransactionDueDate = objInvoice.DueDate.Value
};

This is enclosed in a function and in a foreach statement and therefore called hundreds of times. In maybe 100 calls of this function that calls 1000 times this LINQ to SQL, i get 1 that gives the error.

Hello,

Using the latest 2.50.X version of LinqConnect and in a heavy duty environment, i occasionally get a weird exception during a call to a LINQ to SQL statement:

System.ArgumentException: The method 'Exis.eXray.Domain.ExrayDataContext.get_UdfsValues' is not a property accessor
at System.Linq.Expressions.Expression.GetProperty(MethodInfo mi)
at System.Linq.Expressions.Expression.Property(Expression expression, MethodInfo propertyAccessor)

Of course, the property is right over there and used in the same system in 1000's of places! It is rather unusual and rare. So, is there maybe an internal cache of MethodInfos that you keep for performance reasons, that maybe for some reason is cleared or not properly synchronized, that results to a small time window where this property is requested but not present? Could there be something in my code that invalidates this cache?

Got the test build.

How do i use it?

Im using version 6.30.202 of dotConnect or 2.50.30 of LinqConnect. Can i have a test build of one of this? I really dont want to get into possible breakdowns due to the newer minor version...

Hello,

I switched to Direct connection to a node of my RAC for some days and everything worked as expected. But it's time i go back to my full RAC functionality and the problem persists. Do you want me to send you a crash dump with the relevant information? I don't know what else to do!

Hello,

For the time being, we do not still encounter this error. We had some changes in our RAC configuration and setup and it seems that the problem went away.

I have an unusual observation to make that may help with the situation. Apparently the error emerges when i try to dispose a datacontext. My application server hosts 15 WCF services and every call to their functions, opens a new datacontext and finally disposes it to the the pool. The really odd thing is that ONLY A SINGLE function call errors all the time. The stack is :
Stack:
at Devart.Data.Linq.Provider.ObjectReader`1[[System.Decimal, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].k()
at Devart.Data.Linq.Provider.k+a.d()
at Devart.Data.Linq.Provider.k.e()
at Devart.Data.Linq.Provider.DataProvider.Dispose(Boolean)
at Devart.Data.Linq.DataContext.Dispose()
at Exis.eXray.WorkflowEngine.WorkflowService.ProcessCaseInt(Int64)
at Exis.eXray.WorkflowEngine.WorkflowService.ProcessCaseOneWay(Int64)

Can you make something out of this? Is there a way to help you by providing the code of this function? There are a number of WCF timeouts when the clients call this function. The reliable session times out on the server, do you think this has something to do with the problem? An other characteristic is that this function is marked as a OneWay WCF function. I do not know if any of this info is helpful but it is really odd that the same function errors in datacontext disposal. Code of the relevant function follows:

public void ProcessCaseOneWay(long CaseId)
{
try
{
ProcessCaseInt(CaseId);
}
catch (Exception)
{

}
}


private void ProcessCaseInt(long CaseId)
{
try
{
LockMutex = new Mutex(false, "Exis.eXray.WorkflowEngine." + ServicePort + ".Mutex." + CaseId);
if (!LockMutex.WaitOne(10000))
{
throw new Exception("Case with Id = " + CaseId + ": Could not obtain lock.");
}
try
{
if (SiAuto.Si.GetSession(CaseId.ToString()) == null) SiAuto.Si.AddSession(CaseId.ToString(), true);
dataContext = new ExrayDataContext(DBConnectionString);
if (SiAuto.Si.Level == Level.Debug)
dataContext.Log = new SmartInspectLinqToSqlAdapter(SiAuto.Si.GetSession(CaseId.ToString()))
{TitleLimit = 0, TitlePrefix = "WorkflowService: "};
Case objCase = Case.WorkflowService_ProcessCaseInt(dataContext, CaseId).SingleOrDefault();
if (objCase == null)
{
SiAuto.Si.GetSession(CaseId.ToString()).LogError("Case with Id = " + CaseId +
" does not exist.");
return;
}
if (objCase.Status == CaseEventStatusEnum.Closed || objCase.Status == CaseEventStatusEnum.Expired)
{
SiAuto.Si.GetSession(CaseId.ToString()).LogError("Case with Id = " + CaseId +
" is closed.");
return;
}

Event objCurrentEvent = null;
Event_EventType Event_EventType = GetCurrentEvent(dataContext, objCase.Id).FirstOrDefault();
if (Event_EventType != null)
{
objCurrentEvent = Event_EventType.Event;
objCurrentEvent.Type = Event_EventType.EventType;
objCurrentEvent.context = dataContext;
}
objCase.context = dataContext;
ProcessWorkflow(objCase, objCurrentEvent);
}
finally
{
if (dataContext != null) dataContext.Dispose();
if (LockMutex != null) LockMutex.ReleaseMutex();
if (SiAuto.Si.GetSession(CaseId.ToString()) != null)
{
SiAuto.Si.DeleteSession(SiAuto.Si.GetSession(CaseId.ToString()));
}
}
}
catch (Exception e)
{
HandleException(null, e);
throw;
}
}