Forums : Error upgrading from Pro 1.3 to Pro 1.4
This page last changed on Dec 23, 2015 by mike.schmidt.
I have been running Pro 1.3 without issue. I run OR on a full Tomcat installation and just put the controller app in the webapps folder. This normally works well. When i replace the 1.3 folder with the 1.4 folder, i get an error trying to sync. The error states "An attempt was made to access service context before it was initialized."
I also noticed that when i load the controller webpage that it does not seem to try and connect to the cloud to see if the controller is associated to my account. When i use 1.3, the webpage indicates that the controller is associate to an account, or will tell me to register using the server MAC address. With 1.4, i do not get either of those messages on the web interface.
It appears that maybe i am missing something with the config of 1.4. I read in the change logs that 1.4 introduces a new method of connecting to beehive, so maybe i need to add some information to the configuration parameters. Can anyone help point me in the right direction?
Disregard this post. I have resolved the issue. I copied the config.properties file from the 1.3 controller to the 1.4 folder and everything is fine. I noticed that some of the URLs for the Beehive rest service are different in the 1.4 config, and my pro user account was getting access denied when browsing to the 1.4 URLs. With the !.3 config file, everything seems to work as expected.
|Document generated by Confluence on Jun 05, 2016 09:33|