Do I do something wrong?

[JanOlsmar]

I have a testsite, lets call it oqtane.test.com release 5.2.3
I like to add a new site and use a new seperate databas for this site.
I name it oqtanetest.com/newsite

I fill in this

(All fields is filled correct)
I get this error
An Error Occurred Creating Site. System.InvalidOperationException: A second operation was started on this context instance before a previous operation completed. This is usually caused by different threads concurrently using the same instance of DbContext. For more information on how to avoid threading issues with DbContext, see https://go.microsoft.com/fwlink/?linkid=2097913. at Microsoft.EntityFrameworkCore.Infrastructure.Internal.ConcurrencyDetector.EnterCriticalSection() at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable1.AsyncEnumerator.MoveNextAsync() at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable1 asyncEnumerable, CancellationToken cancellationToken) at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable1 asyncEnumerable, CancellationToken cancellationToken) at Microsoft.AspNetCore.Identity.UserManager1.FindByNameAsync(String userName) at Oqtane.Repository.UserRoleRepository.UpdateSecurityStamp(Int32 userId) in C:\Source\Projects\oqtane.framework\Oqtane.Server\Repository\UserRoleRepository.cs:line 168 at Oqtane.Repository.UserRoleRepository.AddUserRole(UserRole userRole) in C:\Source\Projects\oqtane.framework\Oqtane.Server\Repository\UserRoleRepository.cs:line 75 at Oqtane.Infrastructure.DatabaseManager.CreateSite(InstallConfig install) in C:\Source\Projects\oqtane.framework\Oqtane.Server\Infrastructure\DatabaseManager.cs:line 592

The new database is created but I cant access the new site. It is Blank no log.
I am running my test site on IIS.

[thabaum]

This sounds like it may be an issue worth reporting.

[JanOlsmar]

Process making two databases. First databas was created when I installed first time. Second database was made when I submitted the form above and got the error.

[thabaum]

@JanOlsmar thank you for this information. To verify the app pool worker process has only 1 if I am not mistaken. I will verify soon as I get a moment to log into dev station to see if I can reproduce this issue.

I believe you can and should set this to 1.

[JanOlsmar]

Max 1 worker processes is my setting in the pool

[thabaum]

great thank you. I will see what I can find out. @sbwalker is in Florida, which declared a state of emergency today. I hope the best for everyone dealing with that situation. I will do my best to support until then. On the flip side other developers contributing will be awake later in the evening that may also help provide a solution.

[JanOlsmar]

I'm in no rush, just doing a little testing to see how it worked. Hope for the best regarding Idalia.

[sbwalker]

@JanOlsmar it looks like this specific scenario (ie. creating a new site in a multi-tenant environment using an isolated database) may have been affected by the recent enhancements in 5.2.2 to support SecurityStamp:

Oqtane.Repository.UserRoleRepository.UpdateSecurityStamp(Int32 userId) in C:\Source\Projects\oqtane.framework\Oqtane.Server\Repository\UserRoleRepository.cs:line 168

This method relies on the .NET Identity library - which appears to be throwing the DbContext exception. Perhaps the .NET Identity library is not using DbContextFactory (which is the recommended approach in Blazor). This will require more investigation.

[sbwalker]

@thabaum yes

[sbwalker]

@JanOlsmar I just tested this locally and I was not able to reproduce the error you encountered. One difference is that I was using LocalDB rather than a full SQL Server instance. However it would be helpful to understand if you encountered the error when running in Visual Studio - or on an IIS instance.

[thabaum]

@JanOlsmar I also updated the issue with how to reproduce so @sbwalker can do this from his laptop if needed.

[thabaum]

thanks again for reporting, I will dig into code as I can as he gave us some clues to work on with latest updates to the DB Context Factory, however I cannot verify this until I work deeper in the framework source and push tests to the example production site I have for testing things like this.

[thabaum]

This helps get the ball rolling a little faster, thanks again for reporting and please let us know if you find anything more out that may help.

[thabaum]

@JanOlsmar thanks again for additional support. one last question, sorry to ask as I have not tested via MS SQL Server but did get the error in LocalDB sub-site creation. You mentioned the database is created, is it verified a blank database in MS SQL Server Management Studio second database is created, but it is empty? Not just included Oqtane appsettings.json file but actually a database was created?

I may have time later to review this more, but I don't want to have to do this if it is unnecessary since you say you already have been through that process trying to create a second site with a second database created using MS SQL Server (not LocalDB)

[thabaum]

@JanOlsmar disregard question as I believe once issue #4667 is resolved so with this issue, thanks for reporting!

[sbwalker]

@thabaum the issue related to Installation on IIS #4667 has been resolved... however the issue of creating an additional Site with a separate Database(Tenant) which @JanOlsmar reported in this Discussion thread is unrelated, and still appears to be an issue (ie. I can reproduce it). I cannot reproduce this issue when running in Visual Studio (on IIS Express) so it is very confusing.

An Error Occurred Migrating The Database For Tenant test. This Is Usually Related To Database Permissions, Connection String Mappings, Or The Database Not Being In A Supported State. System.InvalidOperationException: No database provider has been configured for this DbContext. A provider can be configured by overriding the 'DbContext.OnConfiguring' method or by using 'AddDbContext' on the application service provider. If 'AddDbContext' is used, then also ensure that your DbContext type accepts a DbContextOptions<TContext> object in its constructor and passes it to the base constructor for DbContext.
   at Microsoft.EntityFrameworkCore.Internal.DbContextServices.Initialize(IServiceProvider scopedProvider, DbContextOptions contextOptions, DbContext context)
   at Microsoft.EntityFrameworkCore.DbContext.get_ContextServices()
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.DbContext.Microsoft.EntityFrameworkCore.Infrastructure.IInfrastructure<System.IServiceProvider>.get_Instance()
   at Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.Microsoft.EntityFrameworkCore.Infrastructure.IInfrastructure<System.IServiceProvider>.get_Instance()
   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.GetRelationalService[TService](IInfrastructure`1 databaseFacade)
   at Microsoft.EntityFrameworkCore.RelationalDatabaseFacadeExtensions.Migrate(DatabaseFacade databaseFacade)
   at Oqtane.Infrastructure.DatabaseManager.MigrateTenants(InstallConfig install) in C:\Source\Projects\oqtane.framework\Oqtane.Server\Infrastructure\DatabaseManager.cs:line 377 

[thabaum]

this way you can rule out "permissions" as an issue.
edited:
I always wondered how LocalDB permissions would work in this experience FYI this is something worthy of reviewing for production IIS/Apache database support. I will try to add our findings to the Oqtane Documentation along with a few more issues we are now aware of with WebDAV enabled in control panels for example if no one beats me to it... ;)

[thabaum]

https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/sql-server-express-localdb?view=sql-server-ver16

The LocalDB setup program uses the SqlLocalDB.msi program to install the necessary files on the computer. Once installed, LocalDB is an instance of SQL Server Express that can create and open SQL Server databases. The system database files for the database are stored in the local AppData path, which is normally hidden. For example, C:\Users<user>\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\LocalDBApp1. User database files are stored where the user designates, typically somewhere in the C:\Users<user>\Documents\ folder.

[sbwalker]

@thabaum #4676 fixes this issue (logged as #4675). Basically the problem was that when creating a new database it dynamically adds a new connection string to appsettings.json - however the call to the AddOrUpdateSetting() method was not setting the "reload" parameter to true. As a result, when it tried to create the DbContext it could not retrieve the connection string (because it was using an older cached version of IConfiguration). What I don't understand is why this did not throw an exception in Visual Studio. Perhaps when debugging it automatically reloads appsettings.json changes.

[thabaum]

@sbwalker gotcha, glad you found the issue. This makes sense and I believe VS probably is working as you described which maybe related to hot reload? Maybe running without hot reload would create this error?

[thabaum]

The permission issue if using integrated security permissions and should have all permissions needed. So that would rule that out.

[JanOlsmar]

I have done a couple of test of my original error IIS and Sql Server. I never use LocalDB on IIS.
I have tested folder and subsite. Same result and error.
The databases that are created is populated and fine. I can change connectionstrings and get a site running.
the appsetting file is updated with new connection string.
But when browsing the new site eg sub.domain.com or www.domain.com/folder a blank page is displayed

No error in any logs (IIS and Site) whe browsing the new site.

[sbwalker]

@JanOlsmar are you saying that you got the latest code from the Dev branch (with the latest fix), compiled it, deployed it to an IIS instance, and you are still experiencing the problem?

[JanOlsmar]

No was not aware there was a fix for this issue. Still on 5.2.3.
Will try test latest code.

[sbwalker]

I posted this above but it probably got lost in all the other posts "#4676 fixes this issue (logged as #4675). Basically the problem was that when creating a new database it dynamically adds a new connection string to appsettings.json - however the call to the AddOrUpdateSetting() method was not setting the "reload" parameter to true. As a result, when it tried to create the DbContext it could not retrieve the connection string (because it was using an older cached version of IConfiguration). What I don't understand is why this did not throw an exception in Visual Studio. Perhaps when debugging it automatically reloads appsettings.json changes."

[JanOlsmar]

No problem :) Works fine with Dev branch.

[sbwalker]

I am happy this problem is resolved. Thank you for reporting it!

[mdmontesinos]

FYI, the same also happens when trying to deploy in Azure (Web App + SQL Server)

This is with the Install zip from version 5.2.3, so it's not possible to deploy that version in Azure. An urgent 5.2.4 release (that contains the mentioned fix) is required.