This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error during update from 7.0 / 7.0.1 to 7.1

yahya.said over 7 years ago

Hello guys, i have an error which keeps on occurring whenever i try upgrading from version 7.0 or 7.0.1 to 7.1

When doing the upgrade, i made sure to stop processing of any job servers and stop all services running on machines

Any help on how to prevent this issue would be appreciated

Where the error occurs

After pressing Ok on the error dialog

Thanks

Yahya

0 Paul Walker over 7 years ago

What's your starting position is it 7.0 or 7.01, have you also tried going to 7.02 first ? Ensure that theres no activity in the Dbqueue and all jobs complete as well before you attempt to migrate.
Cancel
Up 0 Down

Cancel
0 yahya.said over 7 years ago

This error occurred for both Version 7.0 and 7.01 however this specific error in the screenshot was from Version 7.0. I made sure that the Job Queue and DBQueue was empty before carrying out the upgrade
Cancel
Up 0 Down

Cancel
0 Paul Walker over 7 years ago

Can you go to 7.02 first?
Cancel
Up 0 Down

Cancel
0 Paul Walker over 7 years ago

Can you go to 7.02 first? Also be worth running the database integrity checks from the manager first.
Cancel
Up 0 Down

Cancel
0 Tomi Kääriäinen over 7 years ago

Going to 7.0.2 will most likely not help. The column was deleted in 7.1. Why it is trying to query the column is the issue. Maybe we haven't thought of everything? Do you have a custom column for example in the QBMColumnTranslation.UID_DialogColumnSource?

I'm just trying to figure out what could generate the error. One thing could also be that the migration was started with 7.0 assemblies.
Cancel
Up 0 Down

Cancel
0 yahya.said over 7 years ago

I will give it a go and give you an update as soon as
Cancel
Up 0 Down

Cancel
+1 carsten.paul over 7 years ago

What Version is the configuration wizard from you're using to run the upgrade? It should be the 7.1 configuration wizard. That should also know that the column is no longer existing in the target database schema.
Cancel
Up 0 Down

Cancel
0 yahya.said over 7 years ago

Thank you very much, it updated cleanly. I must have been using the wrong config wizard

Yahya
Cancel
Up 0 Down

Cancel