Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Upgrade 2012 to 2019
#1
I have seen a couple of other posts on upgrading but neither helped.  We have a .vrb file from 2012 that we would like to import into 2018.  I have tried to "import" as I would have moving from one computer to another with 2012 and I have tried to upgrade, but neither option will take the .vrb file.  How do I transition my 2012 .vrb file to 2018.

Thanks,

Jay Tyo
Reply
#2
You need to install version 2012 - imprtyour vrb file and afterwards you can upgrade your datasource to version 2018/19
Regards/Gruss
Oliver
Reply
#3
Having similar issue, have upgraded DB from 2010 to 2012 with no issue.
However trying to use the "2012 upgrade wizard" in 2019 version does not discover environment from .config?
Reply
#4
You can also enter the data manually if it is not found in config file...
Regards/Gruss
Oliver
Reply
#5
(29-03-2019, 10:11 AM)DevOma Wrote: You can also enter the data manually if it is not found in config file...

How is that possible?  There is no manual option using the upgrade wizard?

[Image: VSNOYPi.png]
Reply
#6
Check the config file in ProgramData Directory
Regards/Gruss
Oliver
Reply
#7
(29-03-2019, 09:22 PM)DevOma Wrote: Check the config file in ProgramData Directory

Config looks correct to me?  Contains env data and connection string to SQL DB
[Image: QGjjGCB.png]
Reply
#8
I think Oliver means that you can enter all infos manually if you not choose to use the old environment-file, instead, in the pull down menu of the "Upgrade of 2012 environment window, choose "Specify database access directly". Here you just need the database server name, the database name and the credentials to access them.
Best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --
Reply
#9
Michael,
Thanks, but I do not have the "Specify database access directly" option?
Am I missing something else here?

[Image: RPYwY4c.png]
Reply
#10
Hi,

Hmm it seems your working in file based mode. Then you get the dialogue you see. If you create a new environment as DATABASE then you should see the option to "Specify the database access" ;-)
Best regards,
Michael
best regards,
Michael -- michael.scholz@asg.com --
Reply
#11
Thanks Michael, will try that.
Reply
#12
Worked like a charm now, thanks!
Reply




Users browsing this thread: 1 Guest(s)