Upgrade script failing from 2.6 to 2.65 and onwards to 2.7

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Hace 11 años
Making the jump from 2.6 to 2.7.
As an interim Im going back over the SQL script from 2.6 to 2.65 first, and then doing the 2.65 to 2.7 script.

Why am I doing it this way? Because jumping from 2.6 to 2.7 with the upgrade script throws tons of errors! So I revert my VM back to the way it was before and start from pristine 2.6.

So I run the 2.6 to 2.65 upgrade script. Still errors. Here's what I get:

(15 row(s) affected)
Msg 208, Level 16, State 1, Line 69
Invalid object name 'Language'.
Msg 208, Level 16, State 1, Line 4
Invalid object name 'Setting'.
Msg 208, Level 16, State 1, Line 3
Invalid object name 'Setting'.
Msg 1088, Level 16, State 12, Line 5
Cannot find the object "ProductTag" because it does not exist or you do not have permissions.

Are these expected? Surely not right?
Hace 11 años
Aha. Think I worked it out. The script isnt specifying the DB to be used.
Once I specified "Use MyNopDB" it was all good.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.