We are in the testing and preparation stage of our Tessitura v12.5 to v12.5.1 upgrade. We need to install .NET Framework 4.6 on couple of servers and many workstations in different locations. So we are planning to do it in advance of our v12.5.1 upgrade. I have few questions to those who already upgraded to v12.5.1:
1. Did you have any issue with upgrading to .NET Framework 4.6 in advance? We actually have to do it in advance anyway. So this question is somewhat redundant. But any feedback will be helpful.
2. Is there any advantage or disadvantage of upgrading the servers first and then the client workstations or vice versa, or order doesn’t matter? I am assuming after upgrading to .NET Framework 4.6, the servers will require restart, so there will be some downtime.
3. In the intermediate time (while waiting for v12.5.1 upgrade to happen), did you add [Defaults] section with “ServiceDatabaseCheck=No” only in the master ini or all client ini files prior to install .NET Framework 4.6, as suggested in the upgrade document to avoid an error with the v12.5 Clients and Report Server? Is there any advantage or disadvantage other than additional workload of adding/removing this to all client ini files vs only in the master ini file?
4. Any other advice?
Advance thanks for any comment or suggestion.
Best,
Mo
National Ballet of Canada
Hi Mo,
We installed .NET 4.6 as part of our upgrade process; however, we run multiple test environments and I had at least one that was still on v12.5 running under .NET 4.6 after we started our v12.5.1 testing process. So from what I could tell, .NET 4.6 was compatible with v12.5.
We placed ServiceDatabaseCheck=No only in the master INI file for any v12.5 environment running under .NET 4.6. We removed it once that environment was upgrade to v12.5.1.
I hope this helps!
_______________________________________________________ David Frederick Database Applications Analyst Segerstrom Center for the Arts 600 Town Center Drive, Costa Mesa, CA 92626 T (714) 556-2122 x 4067 E DFrederick@SCFTA.org
Thanks David. This is helpful.
The main thing is to watch out for sneaky systems or computers. We had a situation where - after we head already upgraded to 12.5.1 we found that our Remote Desktop server (which quite a few staff use to access Tessitura when they're working offsit or at home) was set up with an ancient version of Windows Server 2003 which is incapable of working with .NET 4.6. So overnight, we lost the ability to use Tessitura offsite.
Thankfully, our tech guys were able to build a new Remote Desktop system fairly quickly, but it was a tricky couple of weeks.
Thanks Matthew for the heads up. This is very helpful. Now I am going to check with our network team.