Open Closed

Users of Tenants is not having any featurs or permissions #4583


User avatar
0
viswajwalith created
  • ABP Framework version: v7.1
  • UI type: MVC
  • DB provider: EF Core / MongoDB
  • Tiered (MVC) or Identity Server Separated (Angular): yes
  • Exception message and stack trace:
  • Steps to reproduce the issue:"

We just created a sample micro service solution on ABP 7.1 and when creating a tenants. tenants are getting created and default user also created. but when we are logging in with tenant user not able to see any applications, are we missing anything??

also we observed there is entries in below table , as per us it should not be empty

Markdown supported.
Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

4 Answer(s)
  • User Avatar
    0
    liangshiwei created
    Fullstack Developer

    Can you share the error logs? (each service and authserver)

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    viswajwalith created

    logs shared to liming.ma@volosoft.com

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    liangshiwei created
    Fullstack Developer

    inequivalent arg 'x-dead-letter-exchange' for queue 'AppV3_AdministrationService' in vhost '/': received none but current is the value 'AppV3_dead_letter' of type 'longstr''

    That means that you have a AppV3_AdministrationService queue on the broker already and it is without an 'x-dead-letter-exchange' argument. Probably you have created it before with that state.

    You can remove all RabbitMQ queues and try again.

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
  • User Avatar
    0
    viswajwalith created

    inequivalent arg 'x-dead-letter-exchange' for queue 'AppV3_AdministrationService' in vhost '/': received none but current is the value 'AppV3_dead_letter' of type 'longstr''

    That means that you have a AppV3_AdministrationService queue on the broker already and it is without an 'x-dead-letter-exchange' argument. Probably you have created it before with that state.

    You can remove all RabbitMQ queues and try again.

    Thanks for the response, yes we found the issue is with queues, after clearing those it worked perfectly. Thanks

    Markdown supported.
    Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 23, 2026, 09:57
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.