I checked the log file. The main exception is The timeout period elapsed prior to completion of the operation or the server is not responding
for SQL command.
This sounds like ABP cannot reach or find the connection string of the specified tenant. So the problem is at the DB.
From v4.3.X the connection strings are stored in SaasTenantConnectionStrings
table.
So I guess your application doesn't find the connection string for the new tenant and throws server not responding error.
Add a connection string like this to your SaasTenantConnectionStrings
table. And let's see if it works.
Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Microsoft.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
---> System.ComponentModel.Win32Exception (258): Dépassement du délai d’attente.
at Microsoft.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__169_0(Task`1 result)
at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReaderAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Query.Internal.SplitQueryingEnumerable`1.AsyncEnumerator.InitializeReaderAsync(DbContext _, Boolean result, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.SqlServer.Storage.Internal.SqlServerExecutionStrategy.ExecuteAsync[TState,TResult](TState state, Func`4 operation, Func`4 verifySucceeded, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Query.Internal.SplitQueryingEnumerable`1.AsyncEnumerator.MoveNextAsync()
at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken)
at Microsoft.EntityFrameworkCore.Query.ShapedQueryCompilingExpressionVisitor.SingleOrDefaultAsync[TSource](IAsyncEnumerable`1 asyncEnumerable, CancellationToken cancellationToken)
at Volo.Abp.Domain.Repositories.EntityFrameworkCore.EfCoreRepository`3.FindAsync(TKey id, Boolean includeDetails, CancellationToken cancellationToken)
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.Saas.Tenants.TenantStore.GetCacheItemAsync(Nullable`1 id, String name)
at Volo.Saas.Tenants.TenantStore.FindAsync(Guid id)
at Jureez.Data.JureezTenantDatabaseMigrationHandler.MigrateAndSeedForTenantAsync(Guid tenantId, String adminEmail, String adminPassword) in C:\Personnel\Developpement\Jureez\aspnet-core\src\Jureez.Domain\Data\JureezTenantDatabaseMigrationHandler.cs:line 92
ClientConnectionId:c87fd6c1-c77d-4052-9967-8c65aeb3214d
seems like duplicate of https://support.abp.io/QA/Questions/1263/abp-suite---AppUser-as-navigation-property-is-not-working
guys sorry I missed this one. I already created an issue for this. btw check out these. it's very similar
CORS works but you need to add the production server addresses when you deploy.
Also you need to configure IdentityServerClientRedirectUris
db table (this is probably configured from the UI)
sturla closing this, you can reopen at anytime.
is this fixed? can I close it?
For those migrated from 4.2.X to 4.3.X, you need to implement this: https://support.abp.io/QA/Questions/1360/Cannot-create-a-new-tenant-after-migrating-to-430
A new migration handler class has been added in v4.3.0.
Therefore you may have problem with creating new admin user and its related records.
To solve this problem; copy the following class into your project's /aspnet-core/src/Acme.BookStore/Domain/Data
folder.
Don't forget to adjust the Acme.BookStore namespace
https://gist.github.com/ebicoglu/82723d502c3bddcb70b3b77ea567c22e
reported by @chris.tune@gmail.com
Create new tenant not creating admin user
- ABP Framework version: v4.3.0 (Upgraded from 4.2.1)
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): no
- Exception message and stack trace: No error is thrown.
- Steps to reproduce the issue:
- Goto SaaS-->Tenants-->New Tenant
- Create a new tenant with the admin user and pass entered.
- Save
It looks like the tenant is created but the admin user is not added.
In the database the tenant is added but there is no user.
Potentially a problem in ObjectExtensions or TenantAppService?Chris
The issue is more pervasive than Chris reported. None of the identity components are created for the new tenant. This includes the admin user, the default admin role and the initial permission grants needed for the new admin role.
Is there a status available for this issue? Will it be addressed in the next patch?
@scott7106 track the following link https://support.abp.io/QA/Questions/1360/Cannot-create-a-new-tenant-after-migrating-to-430
Hello,
I think i'm the 4 person to report this :
With UI MVC EF Core and no tiered when we create a new tenant the user is not deployed (We cannot login in tenant and use it) We can't on boarding new customer in production :(
It's is ok with a new project. I have followed the migration steps for our project. (with compare method) but the problem is still there.
Thanks for your help.
erreur log is to long to post... timeout in :
at Volo.Saas.Tenants.TenantStore.FindAsync(Guid id) at Jureez.Data.JureezTenantDatabaseMigrationHandler.MigrateAndSeedForTenantAsync(Guid tenantId, String adminEmail, String adminPassword) in C:\Personnel\Developpement\Jureez\aspnet-core\src\Jureez.Domain\Data\JureezTenantDatabaseMigrationHandler.cs:line 92
@Nicolas did you clean your browser cache (cookies)?