We upgraded from 3.0 to 3.1 and have run into an issue. It seems that while upgrade shows no error, in effect it did not pick the upgrade. None of the new features of 3.1 seems to be working.
We have a dedicated BO server on Windows and Tomcat Apache webserver on a seperate server. We had upgraded only the BO server and not the Tomcat. I am thinking this might be the issue. Can someone confirm that the upgrade needs to happen on both?
BO_TN (BOB member since 2008-07-30)
Did you reboot the BOXI server after the install?
Did you stop Tomcat, although the upgrade should have stopped all the services for you.
I can’t see that you would have to upgrade the Tomcat, if you are running a supported version?
Mak 1 
(BOB member since 2005-01-06)
We had installed 3.1 SP2 on the CMS servers but (by oversight) didn’t have SP2 on the tomcat servers and ran into Java issues, for example.
So I would say yes that there can be problems with having different installation versions on the servers.
KimberlyJ (BOB member since 2008-10-28)
Thanks for your reply Kimberley and Mak. A quick update on this.
Our deployment includes a dedicated BO server, Tomcat is loaded on a different server. As part of upgrade/update only the BO server was upgraded. The Tomcat server was not touched as per advice from SAP tech support. Turns out the war file needs to be redeployed from the upgrade package and we had to do that on our Tomcat server.
Once that was done everything fell into place. Its all good now.
xxx
BO_TN (BOB member since 2008-07-30)
Excellent.
I couldn’t see the need to actually upgrade the Tomcat version, unless it was unsupported :).
Deploying the new War files always happens automatically when you upgrade a single box, but, obviously, having a distributed environment you would need to do this step separately.
Mak 1 (BOB member since 2005-01-06)