Unable to connect to SQL Server #7926

5 Answer(s)

• 

  0

  liangshiwei created 3 months ago

  Support Team Fullstack Developer

  Hi,

  I guess these databases do not exist yet. You need to run dbmigrator to create them

  Save Cancel
• 

  0

  castcrewit created 3 months ago

  Yes the database do not exists and when we run any microservice solution it should create the database automatically.

  Doesn't this line of code expected to do that :

  public override async Task OnPreApplicationInitializationAsync(ApplicationInitializationContext context)
  {
      using var scope = context.ServiceProvider.CreateScope();
      await MigrateDatabase(scope.ServiceProvider);
  }
  

  However we used the Abp Studio to run the Migration as we get the below error

  0:20:44.265 	 Information  	 Starting task execution: "Updating the database: IntegrationServices.AdministrationService"20:22:24.503 	 Information  	 CLI command executed. Command: "dotnet ef database update"
   Working directory: "C:\SourceCode\integration-microservices\services\administration\IntegrationServices.AdministrationService" 
   CommandResult { ExitCode: 1, IsSuccess: False, StartTime: 09/17/2024 20:20:44 -07:00, ExitTime: 09/17/2024 20:22:24 -07:00, RunTime: 00:01:40.2136695 }
  20:22:24.505 	 Information  	 Failed task execution: "Updating the database: IntegrationServices.AdministrationService"
  20:22:24.505 	 Information  	 ERROR: "An error has occured!"
  20:22:24.505 	 Information  	 ERROR DETAILS: "Failed to update database in project IntegrationServices.AdministrationService"
  20:22:24.505 	 Warning      	 Exception of type 'Volo.Abp.Studio.AbpStudioException' was thrown.
  20:22:24.507 	 Warning      	 Code:AbpStudio:EfCoreUpdateDatabaseFailed
  20:22:24.507 	 Warning      	 Details:
  20:22:24.507 	 Warning      	 ---------- Exception Data ----------
  ProjectName = IntegrationServices.AdministrationService
  

  <br> <br> <br>

  <br> Then i went ahead and tried toe apply migration like the below

  dotnet ef database update --project IntegrationServices.AdministrationService --context AdministrationServiceDbContext

  No migrations were applied. The database is already up to date.

  When I went to the database this is what I see , only the migration history table gets created when the code is getting built :

  

  I am very confused how things should work, you mentioned run the migrator, where is the migrator project , it doesn't come by default.

  We never had such issues while using MySQL, why the process will be any different and if its different what's the correct process. I am doubting it may be to do with the code template or somehwere in the code, have you tried the project i sent you

  Save Cancel
• 

  0

  liangshiwei created 3 months ago

  Support Team Fullstack Developer

  microservice solution it should create the database automatically.

  yes, the microservices will create database.

  No migrations were applied. The database is already up to date. When I went to the database this is what I see , only the migration history table gets created when the code is getting built :

  I guess there are no db migrations files?

  you can create it manually

  dotnet ef migrations add Initial -c ....

  Save Cancel
• 

  0

  castcrewit created 3 months ago

  Thank You and that was the cause of the issue. There should be a troubleshooting guide for this, the Abp Studio is in Beta and doesn't work at times properly, like migration not getting created. You should put a guide on things to watch out when you create a project for the first time

  Save Cancel
• 

  0

  liangshiwei created 3 months ago

  Support Team Fullstack Developer

  Hi,

  we will

  Save Cancel