Activities of "alper"

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:

1. Goto SaaS-->Tenants-->New Tenant
2. Create a new tenant with the admin user and pass entered.
3. 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)?

Blazor 4.3 preview

unable to generate, is it backend template name is wrong spelling "o" and "e" ?

@Leaf, this is fixed in the patch version wait for 2021-05-21

Hello Alper,

Sorry to come back with this but we still couldn't create a new tenant and use them because the user is not created. There are several of us in this situation since switching to 4.3 and this is a major problem for us because we can no longer have a new customer ...

I tested that on a new 4.3 project the problem does not appear, yet we did the migration well (via file comparison) but impossible to have a user on the creation of a new tenant.

The situation is becoming critical for us. Thank you in advance for your precious help.

Nicolas.

@Nicolas,

I created a new issue about this, can you please write all the findings you have into this issue (exception logs) https://support.abp.io/QA/Questions/1360/Cannot-create-a-new-tenant-after-migrating-to-430

Greetings;

I am going through the Bookstore tutorial with a fresh download of Abp.io 4.3 Angular EF

After adding the entity Book, as per the directions I am setting the Default project to src<MyAppName>.EntityFrameworkCore.DbMigrations

running the command: Add-Migration "MyMigrationName"

I receive the following error:

More than one DbContext was found. Specific which one to use. Use the '-Context' parameter for PowerShell commands and the '--context' parameter for dotnet commands.

I think in your latest release documentation you state you have dynamic dbContext options now... Would this have anything to do with this?

Please advise,

--Dave

hi the samples are being updated. you can set the context with the -Context parameter

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:

1. Goto SaaS-->Tenants-->New Tenant
2. Create a new tenant with the admin user and pass entered.
3. 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

I have the same problem here, ABP Framework version:* v4.3.0 from new Template.

at Volo.Abp.Castle.DynamicProxy.CastleAsyncAbpInterceptorAdapter1.InterceptAsync[TResult](IInvocation invocation, IInvocationProceedInfo proceedInfo, Func3 proceed) at Volo.Saas.Tenants.TenantStore.GetCacheItemAsync(Nullable`1 id, String name) at Volo.Saas.Tenants.TenantStore.FindAsync(Guid id) <<<---- Error

@arifharsono

the stack trace show that it doesn't find the tenant. did you clean your browser cookies? sometimes old cookies from other databases may break the new project.

30 days to release

I have not tested Suite when project names are changed, because it assumes that ABP project names and directory names will not change. but you can try this; your project structure is saved to %UserProfile%\.abp\suite\appsettings.json. you can edit this file according to your new changes

I created a new project with the latest version and I couldn't reproduce it. if you copy paste the json file from another project, it will not compile because there's a namespace of other project.

I think you disable the validation on the controller but in the controller method also calls the application service method. application service methods are also being validated automatically. so you need to replace the UserAppService and add [DisableValidation] attribute to the UserAppService CreateAsync method.