LLBLGen Pro Support System Bugs & Issues feed

The process was terminated due to an unhandled exception. Info.SD.LLBGen.Pro.ORMSupportCLasses.ORMTransientRecoveryFailedException Gen.Pro.ORMSupportClasses.RecoveryStrategyBaseExecute(...) by Otis

Otis — Sat, 16 May 2026 05:12:45 GMT

greenstone91 wrote:

SD.LLBLGen.Pro.ORMSupportClasses.dll is file version 5.8.3.0 9/24/2021 SD.LLBLGen.Pro.DQE.OracleODPNet.dll is file version 5.8.3.0 9/24/2021 LLBLGen Pro 5.8.3

I will ask the user to give me a more full stack trace...including the most inner exception.

the transient error recovery handler passed to the adapter in your app couldn't handle the exception. So also check that. usually this occurs if an exception occurs that falls outside the list of transient errors that can be recovered so it's bubbled upwards and then no handler is in place and it ends up in the app's general handler. Can literally be anything, from server inaccessable, to a program error etc.

The process was terminated due to an unhandled exception. Info.SD.LLBGen.Pro.ORMSupportCLasses.ORMTransientRecoveryFailedException Gen.Pro.ORMSupportClasses.RecoveryStrategyBaseExecute(...) by greenstone91

greenstone91 — Fri, 15 May 2026 13:58:52 GMT

SD.LLBLGen.Pro.ORMSupportClasses.dll is file version 5.8.3.0 9/24/2021 SD.LLBLGen.Pro.DQE.OracleODPNet.dll is file version 5.8.3.0 9/24/2021 LLBLGen Pro 5.8.3

I will ask the user to give me a more full stack trace...including the most inner exception.

The process was terminated due to an unhandled exception. Info.SD.LLBGen.Pro.ORMSupportCLasses.ORMTransientRecoveryFailedException Gen.Pro.ORMSupportClasses.RecoveryStrategyBaseExecute(...) by Otis

Otis — Fri, 15 May 2026 05:42:07 GMT

a bit more info would help... https://www.llblgen.com/tinyforum/Thread/7717/1

So what's the entire stacktrace including the inner exception and what's the version etc.

The process was terminated due to an unhandled exception. Info.SD.LLBGen.Pro.ORMSupportCLasses.ORMTransientRecoveryFailedException Gen.Pro.ORMSupportClasses.RecoveryStrategyBaseExecute(...) by greenstone91

greenstone91 — Thu, 14 May 2026 13:58:59 GMT

Hi, With my program .NET 4.7.2 command-line executable program (<TargetFrameworkVersion>v4.7.2</TargetFrameworkVersion>) WebApiClient.exe, this error occasionally happens occasionally.

Thoughts on the cause?

Application: WebApiClient.exe Version v4.0.30319 The process was terminated due to an unhandled exception. Info.SD.LLBGen.Pro.ORMSupportCLasses.ORMTransientRecoveryFailedException Gen.Pro.ORMSupportClasses.RecoveryStrategyBaseExecute(System._Canon, mscorlib, Version=4.0.0.0,Culture=neutral, PublicKeyToken……. . . . . Info:GRB.Platform.Core.Exceptions.FrameworkBusinessException

Inform.FrameworkBusess.SystemManager.GetSystemEntity(SD.LLBL.Gen.Pro.ORMSUpportClasses.DataAccessAdapter.SD.LLBLGen.Pro.ORMSupportClasses.ExcludeIncludeFieldsList) Inform.Frame

Followed by this error: Faulting application name: WebApiCLient.exe, version 1.2.165.44 Faulting modeul name: KERNERBASE.dll, version: 10.0.17763.8510 Exception code: 0x043452

Issues on FetchEntityCollection's Parameter (maxNumberOfItemsToReturn) by Otis

Otis — Tue, 05 May 2026 07:20:15 GMT

If you use the paging api, you get what you asked for: the page size in records. the limiter is ignored

Dynamic Prefetch Path Setup by Otis

Otis — Tue, 05 May 2026 07:19:25 GMT

User001 wrote:

Otis wrote:

The EntityType enum value is to make sure what the root type is of the path. You can obtain the entity type enum from an entity instance, cast it to IEntityCore and then read the LLBLGenProEntityTypeValue property. You can pass that to a PrefetchPath2 constructor (as that's for adapter). To get an instance you could obtain the factory using the EntityFactoryFactory by passing the class type. You can then create a dummy instance (which is very fast) and obtain the type value that way. You can also obtain the value using the Enum API from .net, and use the string to obtain the value.

Be aware that by dynamically setting up a prefetch path you might run into a lot of fetches you don't need. After all the data is used somewhere, and that code also has to be aware of which data was fetched.

Sorry, I think is like this, I wanted to dynamically create IPrefetchPathElement, not the RootType. Because let's say want to fetch Customer Entity to prefetch Order Entity, Address Entity (Order Entity and Address Entity are subEntities of Customer Entity), my function can let caller to choose which one to prefetch. It just doesnt seem to have any way to find and get the IPrefetchPathElement or IPrefetchPathElement2 to add. So, my function used Reflection instead.

If you have a function that accepts a parameter to determine what to prefetch, why not pass in the prefetch path to use? So the caller passes the prefetch path they want to be applied to the fetch

Issues on FetchEntityCollection's Parameter (maxNumberOfItemsToReturn) by User001

User001 — Tue, 05 May 2026 03:37:57 GMT

Hi everyone, I tested DataAccessAdapterCore.FetchEntityCollection() with this parameter

adapter.FetchEntityCollection(collection, filter, 100, sorting, prefetch, 2, 111);

I thought it should return top 100 of the next 111 records but it somehow still returned 111 records. Although SQL doesnt accept OFFSET with TOP but no exeception thrown. Is it a bug?

Dynamic Prefetch Path Setup by User001

User001 — Mon, 04 May 2026 07:44:39 GMT

Otis wrote:

The EntityType enum value is to make sure what the root type is of the path. You can obtain the entity type enum from an entity instance, cast it to IEntityCore and then read the LLBLGenProEntityTypeValue property. You can pass that to a PrefetchPath2 constructor (as that's for adapter). To get an instance you could obtain the factory using the EntityFactoryFactory by passing the class type. You can then create a dummy instance (which is very fast) and obtain the type value that way. You can also obtain the value using the Enum API from .net, and use the string to obtain the value.

Be aware that by dynamically setting up a prefetch path you might run into a lot of fetches you don't need. After all the data is used somewhere, and that code also has to be aware of which data was fetched.

Sorry, I think is like this, I wanted to dynamically create IPrefetchPathElement, not the RootType. Because let's say want to fetch Customer Entity to prefetch Order Entity, Address Entity (Order Entity and Address Entity are subEntities of Customer Entity), my function can let caller to choose which one to prefetch. It just doesnt seem to have any way to find and get the IPrefetchPathElement or IPrefetchPathElement2 to add. So, my function used Reflection instead.

QueryParameters Usage when dont want the Entities from Context be affected by User001

User001 — Mon, 04 May 2026 07:17:34 GMT

For the FetchEntityCollection: Oh I see. I get it now. Basically, ObjectId is used for keeping same reference to that of Entity instance from Context and it is just for the internal process when FetchEntityCollection() identify previous Entity (which already in the Context) and update back the new field value fetched from database (of course cannot change the PrimaryKey or UniqueKey Field value otherwise could not find) while at the same time, maintaining the Entity instance of the same ObjectId.

For the QueryParameters: I see, it was used for LLBL internal processes to call with QueryParameters and not public for users. If I used QueryParameters, might skip some processes. Thanks I understand now.

Dynamic Prefetch Path Setup by Otis

Otis — Mon, 04 May 2026 06:52:09 GMT

The EntityType enum value is to make sure what the root type is of the path. You can obtain the entity type enum from an entity instance, cast it to IEntityCore and then read the LLBLGenProEntityTypeValue property. You can pass that to a PrefetchPath2 constructor (as that's for adapter). To get an instance you could obtain the factory using the EntityFactoryFactory by passing the class type. You can then create a dummy instance (which is very fast) and obtain the type value that way. You can also obtain the value using the Enum API from .net, and use the string to obtain the value.

Be aware that by dynamically setting up a prefetch path you might run into a lot of fetches you don't need. After all the data is used somewhere, and that code also has to be aware of which data was fetched.