Migration not start on publish

Question

My application was published on local folder and then published on server. The initial deploy worked well. After I made some updates, the migration does not start after updating the files on server.

The EFSQLScripts folder contains the sql script including all migrations and it was automatically created during publish process

I am using Visual Studio Community 2019. My publish settings are

Naimish Makwana · Answer

Hello Marius, Please check below possiblity for the exception: SQL scripts in the EFSQLScripts folder and search for the column names mentioned in the error message. Verify if the column exists in the relevant table. Verify if the model in your application matches the schema in the database. Ensure that the entity framework configuration is set up correctly, especially if you have made any changes to the model or database schema. Ensure that the migration history table in the database is up to date and contains information about all the previously executed migrations. If you are still unable to identify the issue, try running the SQL scripts manually on the server to see if you get the same error. This could help you isolate the issue and identify the root cause. Verify if the database schema on the server matches the schema in your application. Ensure that the relevant tables and columns exist in the database. Thanks Naimish Makwana

Naimish Makwana · Answer

Hello Marius, Please check the server logs. Please see if there are any error messages related to the migration process. This could give you some clues. Please check below link which might help you. https://stackoverflow.com/a/59184689/3054222 Thanks Naimish Makwana

Marius Vasile · Answer

Thank you all for suggestions, The error window is below. To answer other questions I am using a shared server services. I created the database but I don't have full access to it, is on a shared drive. EFSQL script is created at publish and contains the migration. I will send a message to admin to check database

Marius Vasile · Answer

Naimish If you are still unable to identify the issue, try running the SQL scripts manually on the server to see if you get the same error. This could help you isolate the issue and identify the root cause. How can I do that? Verify if the database schema on the server matches the schema in your application. Ensure that the relevant tables and columns exist in the database. Database on server is Initial migration, I try to add three consecutive migrations with my update

Marius Vasile · Answer

So, I checked my sql file and it has all new added info like IF NOT EXISTS(SELECT * FROM [__EFMigrationsHistory] WHERE [MigrationId] = N'20230216055759_Rev3') BEGIN ALTER TABLE [ProgCMPs] ADD [CMDone] bit NOT NULL DEFAULT CAST(0 AS bit); END; of course from first to migration no.3

Vishal Joshi · Answer

Hello Marius, Can you please check the output window for errors or response messages? Please share if any warning or error in output window. Thanks

Tuhin Paul · Answer

Hi Marius, It seems like there could be a few potential reasons why the migration is not running after the application has been updated on the server. Please check the following pointers : 1. Check the database connection string: Make sure that the database connection string in the web.config file is correct and matches the settings in the server environment. If the connection string is incorrect, the migration will not run. 2. Verify the Migrations configuration: Check that the database context has migrations enabled and that the migration configuration is correct. Ensure that there is a MigrationHistory table in the database. 3. Check if the automatic migration is enabled: If the automatic migration is disabled, then the migration will not run. Ensure that the AutomaticMigrationsEnabled property is set to true in the database context configuration. 4. Ensure that the EFSQLScripts folder is correctly deployed: The EFSQLScripts folder must be included in the deployment package and copied to the server. Double-check that the folder is being copied to the correct location on the server and that it is not being blocked by any security settings. 5. Check the server environment: Make sure that the server environment meets the requirements for the application to run correctly. 6. Check the migration logs: Check the application logs to see if there are any errors related to the migration. These logs can help identify the root cause of the issue.