Today I was performing an in-place upgrade to R2 and that was an adventure on it’s own
First let’s start of by saying that the in-place upgrade documentation on MSDN was really helpful and well written!
But anyway, I wanted to tell you about two specific issues that I’ve encountered :
- Database and AOS on different machines
- AOS and locating the Model Store
Database and AOS on different machines
When I ran the installer to configure the existing database, the new R2 models from Microsoft were installed in the Model Store database, but the ‘old’ models were not copied from the other database to the new model store. The white paper mentions possible trouble, but I just performed the data upgrade on a single machine and that was that.
AOS and locating the Model Store
The other issue was a bit more interesting. When the data upgrade was done, I restore the database over the existing one on the target environment. But when I started the AOS server, I received a huge amount of DB sync issues. At first I was surprised since I am used to restoring databases and connecting the AOS to them. Once done, you should have the same situation but here it was not the case.
Further investigation pointed out that the installer forgot some things when upgrading the AOS. Namely, updating the existing configuration of the AOS. Since R2, there are two new parameters in the configuration files : ModelDBServer and ModelDatabase. But they have been left blank.
So at this point, the AOS starts and since the isntaller did not remove the old models from the data database, it is still a valid model store and Ax starts!
Filling in these values with the correct model store database solved the issue.
PS: The same is happening for the Max Buffer Size parameter (Left at 24kb and R2 need 40kb)