YAFLogo

yetanotherjedi
  • yetanotherjedi
  • 51.4% (Neutral)
  • YAF Forumling Topic Starter YAF Version: v2.3.1.15
4 months ago
Hi all,

Need some pointers on the above subject. My current setup is for LAB testing to assist with cloud migrations. YAF is installed on a dedicated VM and the DB is installed on its own VM. Windows Server 2019 and SQL Server 2019. The Test forum works fine.

Anytime I try to upgrade to using the instructions on Home · YAFNET/YAFNET Wiki (github.com) , including using the web.config migration too, it just breaks.

I've even tried to set up a side by side setup making sure the new DB has the same permissions etc. and It managed to run thru the install wizard and bombs on the final page.

I concede its probably something I'm doing wrong on both instances but the official instructions are exactly great and was hoping some users have got deeper insights they can share.

Thanks 

Sponsor
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.0 rc 2
4 months ago
What errors are you getting on upgrade?
yetanotherjedi
  • yetanotherjedi
  • 51.4% (Neutral)
  • YAF Forumling Topic Starter YAF Version: v2.3.1.15
4 months ago

What errors are you getting on upgrade?

Originally Posted by: tha_watcha 

Hi, thanks for replying

I've given up on the upgrade path and setup up a new Windows 2022 server to test on.

Again I get thru the same setup Wizard and it bombs with the following error when initialising the DB...

Invalid object name \'dbo.yaf_UserPMessage\'.

tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.0 rc 2
4 months ago

What errors are you getting on upgrade?

Originally Posted by: yetanotherjedi 

Hi, thanks for replying

I've given up on the upgrade path and setup up a new Windows 2022 server to test on.

Again I get thru the same setup Wizard and it bombs with the following error when initialising the DB...

Invalid object name \'dbo.yaf_UserPMessage\'.

Originally Posted by: tha_watcha 

That's a bug. Looks like not all tables are created. The issue will be fixed in 3.2.7 (release will in the next few days)