Hey Maliming,
Yeah, that seems to have worked for me at this time, if I have any more issues, I will let you know. Otherwise thank you very much I really do appreciate the help :)
Sorry about the delay, was about to get JetBrains Rider now for you was just getting home haha, but sounds like you don't need me to now, best of luck, keep me updated, if there's anything I can do to assist let me know, otherwise thank you I appreciate the help.
Oh yip, nah that's all good, feel free to try to reproduce locally otherwise let me know if you wanna try remotely again or want help to try to reproduce it on your machine etc. Appreciate they help, thank you.
That's weird, the only thing I can suggest is hopping on a call and work on reproducing it for you or fixing it for me together, that way we can compare environments etc. As I have no clue why you are not experiencing the issue like we are.
Yeah, our other developers are having the same issue, in addition to have a very simular issue when hosting on azure.
Hey,
It seems to be random for me, running it with visual studio debug, and duplicating tables and mass refreshing them seems to make the occurrence more likely, but still occurs at random either way. My current project is pretty much identical to what I last sent you as it was a test project for this issue, but it may still be easier for us to call and try reproduce this issue for you locally otherwise solve it for me by looking for environment differences etc. Since it seems to occur quite often for me.
Regards, Josh.
Hey,
I don't believe you can do this part async sadly, and the AsyncHelper didn't help, it still was occuring.
Regards, Josh.
Hey,
I added it since then I haven't seen the other issue but the disposed is still occuring, the Dispose call was only added as a test as that was already occuring and once removed it continues to occur, it occurs at random but not highly frequant, I did notice when in debug it seems to occur faster.
[16:24:03 ERR] StartBuild error
System.AggregateException: One or more errors occurred. (Error when trying to populate the datasource. The following exception was thrown:
Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'BookStoreDbContext'.)
---> DevExpress.XtraReports.DataRetrievalException: Error when trying to populate the datasource. The following exception was thrown:
Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'BookStoreDbContext'.
---> System.AggregateException: One or more errors occurred. (Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'BookStoreDbContext'.)
---> System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'BookStoreDbContext'.
at Microsoft.EntityFrameworkCore.DbContext.CheckDisposed()
at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()
at Microsoft.EntityFrameworkCore.DbContext.get_ChangeTracker()
at Volo.Abp.EntityFrameworkCore.AbpDbContext`1.Initialize(AbpEfCoreDbContextInitializationContext initializationContext)
at Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider`1.CreateDbContextAsync(IUnitOfWork unitOfWork, String connectionStringName, String connectionString)
at Volo.Abp.Uow.EntityFrameworkCore.UnitOfWorkDbContextProvider`1.GetDbContextAsync()
at Volo.Abp.Domain.Repositories.EntityFrameworkCore.EfCoreRepository`2.GetDbSetAsync()
at Volo.Abp.Domain.Repositories.EntityFrameworkCore.EfCoreRepository`2.GetQueryableAsync()
at Castle.DynamicProxy.AsyncInterceptorBase.ProceedAsynchronous[TResult](IInvocation invocation, IInvocationProceedInfo proceedInfo)
at Volo.Abp.Castle.DynamicProxy.CastleAbpMethodInvocationAdapterWithReturnValue`1.ProceedAsync()
at Volo.Abp.Uow.UnitOfWorkInterceptor.InterceptAsync(IAbpMethodInvocation invocation)
at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter`1.InterceptAsync[TResult](IInvocation invocation, IInvocationProceedInfo proceedInfo, Func`3 proceed)
at Volo.Abp.Domain.Repositories.RepositoryAsyncExtensions.FirstAsync[T](IReadOnlyRepository`1 repository, CancellationToken cancellationToken)
--- End of inner exception stack trace ---
at DevExpress.DataAccess.Native.ObjectBinding.ObjectDataSourceFillHelper.BrowseForResult(Object instance, String dataMember, ParameterList parameters)
at DevExpress.DataAccess.ObjectBinding.ObjectDataSource.GetFillResult(IEnumerable`1 sourceParameters, Boolean schemaOnly, Object dataSource, String dataMember, ParameterList parameters, ObjectConstructorInfo constructor)
at DevExpress.DataAccess.ObjectBinding.ObjectDataSource.Fill(IEnumerable`1 sourceParameters, Boolean schemaOnly)
at DevExpress.DataAccess.ObjectBinding.ObjectDataSource.Fill(IEnumerable`1 sourceParameters)
at DevExpress.DataAccess.ObjectBinding.ObjectDataSource.DevExpress.Data.IListAdapter.FillList(IServiceProvider servProvider)
at DevExpress.XtraReports.Native.ListAdapterFiller`1.ExecuteCore()
at DevExpress.XtraReports.Native.DataSourceFiller.Execute()
--- End of inner exception stack trace ---
at DevExpress.XtraReports.Native.DataSourceFiller.Execute()
at DevExpress.XtraReports.UI.XtraReportBase.FillDataSources(Boolean skipIfFilled)
at DevExpress.XtraReports.UI.XtraReport.FillDataSources()
at DevExpress.XtraReports.UI.XtraReport.DevExpress.XtraReports.IReport.CreateDocumentCore(Single progressRange, Boolean buildForInstantPreview)
at DevExpress.XtraReports.Native.DocumentCreator.Create(Single progressRange, Boolean buildForInstantPreview)
at DevExpress.XtraReports.UI.XtraReport.CreateDocument(Single progressRange, Boolean buildForInstantPreview)
at DevExpress.XtraReports.UI.XtraReport.CreateDocument(Boolean buildForInstantPreview)
at DevExpress.XtraReports.UI.XtraReport.CreateDocument()
at DevExpress.XtraPrinting.Caching.CachedReportSourceBase.CreateDocumentCore()
at DevExpress.XtraReports.Web.WebDocumentViewer.Native.BuildTaskFactoryWeb.<>c__DisplayClass9_0.<CreateTask>b__0()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of inner exception stack trace ---
Regards, Josh.
Hey,
I don't believe I have MultipleActiveResultSets=True in the connection strings, how you like me to try it with it?
Also, I believe I have already tried those examples as they seem to be the same as the examples I mentioned above which was the original base of the project. There are just a few changes from testing things, but yeah.
Regards, Josh.
Here are a few errors and stack traces I managed to quickly get for you, some in debug and some not:
Disposed of error out of debug: https://pastebin.com/uuajyzsF
Disposed of error in debug: https://pastebin.com/F7MZK388
Another random error: https://pastebin.com/ck1da3tn
Thanks, Josh.