Loading Profile...
This afternoon I upgraded our 4.5.1 installation to 5.1. Installation succeeded, but after installation I cannot connect to Scrumworks anymore using the http://hostname:8080 url. Not from the server itself through localhost, nor from any remote machine. Where previously with the 4.5.1 installation we did not have any problems connecting to the server.
I could only find a boot.log file. It can be found here:
http://dl.dropbox.com/u/59534783/boot...
Help get this topic noticed by sharing it on
Twitter,
Facebook, or email.
Twitter,
Facebook, or email.
I’m
nervous
Cannot connect to Scrumworks 5.1 after upgrading from 4.5.1
-
This morning, after getting back in the office, I noticed that I could contact the server, but immediately when opening a page, the website says: "Session closed".
Now, the logs directory does contain a server.log. It can be found here:
http://dl.dropbox.com/u/59534783/serv...Comment -
-
Today, completely reinstalled Scrumworks. No results. After starting the service, only a boot.log is available in the logging directory and browsing to http://hostname:8080 results in a "Oops! Google Chrome could not connect to ...".
-
-
It seems solved now. The server was still running on 512 MB of memory. Increased to 2 GB to meet the minimum ScrumWorks Pro 5.1 requirements.
-
-
So, after a few days of using the 5.1 version I can conclude that I'm not very happy with the upgrade. Every few hours we can't connect anymore to ScrumWorks and need to restart the server. Then it takes approximately half an hour for the webserver to be started (boot.log appears half an hour before server.log appears). And while operating ScrumWorks it's very very very slow. So, although we managed to connect to ScrumWorks, it's far from useable at this moment.
All in all, I'm considering a downgrade to the previous version again. -
-
Hello,
I received your support request from our Ticket system. Please be on the lookout for a ticket from us with a request for some more system information.
Thank You! -
EMPLOYEE
