Hello, I upgraded 2 PVS Servers from 1912 to 2203C...
# citrix-provisioning
l
Hello, I upgraded 2 PVS Servers from 1912 to 2203CU5 and I have these error when I tried to show Usage tab in vDisk Version : Someone had these error ? Farm seems ok and TDS balancing between servers is ok. Thanks
b
Yess. Update your DB compability level.
l
I have this :
in KB it's written to change it to 131, is this right ?
b
right click on your database and check your compability level
l
150
image.png
b
should be fine. I suggest you create CDF traces and a support case.
l
OK thank you for your help.
Can I continue to upgrade the Citrix farm so with upgrade half of delivery controller ? (the 2 PVS servers are up to date).
b
Sure, that are separate databases.
👍 1
For the DDCs: VirtualChannel blocking is the new default with 2203. Please consider this.
l
Yep, I noted that because it has impact on ThinPrint. Thanks 🙂
So I have to add a policy for these settings after DDC are upgraded.
b
correct.
s
It depends on which 1912CU you upgraded from -- there was an issue in 1912CU5 that caused upgrade problems later on -- this was addressed in CU6 (so an upgrade to CU6 will fix the error and ensure future upgrades are OK). If you've done the upgrade already, then applying the workaround in the CTX402846 article should work.
l
Hello, I opened a case and i'm waiting. I was on 1912CU5 and finished my upgrade to 2203CU5 for all the core components. (I have TDS, VDA and WEM agent to be upgraded this after noon).
s
Unfortunately then you will need to apply the workaround. Upgrading to 1912-CU6 first would have avoided this. Hopefully someone from support can help walk you through this.
l
I hope too, thank you. I hope that I will not have any other issue on PVS farm because of this...
s
Should be fine once you fix the database schema upgrade... sooner the better though.
l
image.png
s
TBH, if you follow the steps in the CTX that will be a permanent fix -- we just dont test it with every possible combination of to release so if something were to break you would need to revert to the second approach and restore your server(s) and database to 1912-CU5.