Upgrading database to 3.7 doesn't match entity model for 3.7 [Resolved]

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Il y a 8 ans
I just upgradedfrom nopCommerce 3.3 to 3.7 using the upgrade scripts.  All upgrade scripts ran perfectly with no errors.  

When I run the website, I get an entity framework error.  Apparently the entity model does not match the upgrade scripts?  Did I do something wrong or is this a known issue?   Please help, thank you.

These were the messages I got in the exception:

{"An error occurred while executing the command definition. See the inner exception for details."}
{"Invalid column name 'LeasedByMachineName'.\r\nInvalid column name 'LeasedUntilUtc'."}

The error occurred on ScheduleTaskService.cs line 88 in nopCommerce 3.7

---------------------------------

Update: Solved.
Be sure after you upgrade you're pointing to the newly upgraded database and not your previous copy of your old database.  Gotta remember how nopCommerce uses the settings.txt file for the database connection string.
Il y a 8 ans
swsdev wrote:
I just upgradedfrom nopCommerce 3.3 to 3.7 using the upgrade scripts.  All upgrade scripts ran perfectly with no errors.  

When I run the website, I get an entity framework error.  Apparently the entity model does not match the upgrade scripts?  Did I do something wrong or is this a known issue?   Please help, thank you.

These were the messages I got in the exception:

{"An error occurred while executing the command definition. See the inner exception for details."}
{"Invalid column name 'LeasedByMachineName'.\r\nInvalid column name 'LeasedUntilUtc'."}

The error occurred on ScheduleTaskService.cs line 88 in nopCommerce 3.7


Is nopCommerce 3.3 fresh or customize? if customized  then change source code 3.7   like 3.3
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.