Shot in the dark here, but after your upgrade did your "Umbraco.Core.ConfigurationStatus" appSetting contain the Umbraco version number or was it blank? This typically causes the installation window to show.
after deployment is done, tried to open Umbraco, it shows me the installation window as we go through the installation process.
when I restore DB, it's working fine, but again when I deploy changes, it shows the same window.
Cause of Above two points, means your local or Staging Umbraco Database base having different versions of Umbarco DB.
This is not necessarily the reason at all, it is more likely the SQL user is not set as the dB owner which is why it creates a new set of tables with a different schema name. Th remot dB user needs to be assigned the dnowner mapping.
When I deploy changes on server, every time showing installation process. is there something configuration to avoid this?
I just installed Umbraco 8.12.2. set up a project and deployed on a staging server. I set up everything.
Anyone help me to fix this issue?
Thank you in advance, HK
Are you absolute certain thar your connection string is pointing to the correct database?
yes. it creates all database table in same database.
See these images.
It creates duplicate tables.
Shot in the dark here, but after your upgrade did your "Umbraco.Core.ConfigurationStatus" appSetting contain the Umbraco version number or was it blank? This typically causes the installation window to show.
Yes, the version is up to date. in local works, fine but the same on the server won't work.
I think it is dbowner issue. this DB user is not DB owner so might be it restore all tables again.
Yes it looks like a dB owner issue as it appears to have created another set of tables using the username as the schema
Hi HariKrishna,
Cause of Above two points, means your local or Staging Umbraco Database base having different versions of Umbarco DB.
Thanks, Shekhar
This is not necessarily the reason at all, it is more likely the SQL user is not set as the dB owner which is why it creates a new set of tables with a different schema name. Th remot dB user needs to be assigned the dnowner mapping.
is working on a reply...