Search Communities:

This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
4 Replies Last post: Aug 5, 2008 5:13 PM by BigDawg

HTTP Status 500

Aug 3, 2008 2:57 PM

Click to view gregmns's profile gregmns 2 posts since
Mar 17, 2008

Hi,

I had to reinstall Linspire from a CD and when trying to update CNR Client I get a "HTTP Status 500"

"javax.servlet.ServletException: java.lang.RuntimeException: exception invoking: initialize".....error.How do I fix this? Any help would be appreciated. Greg

Click to view JDoyle's profile JDoyle 208 posts since
Nov 27, 2007
1. Re: HTTP Status 500 Aug 3, 2008 7:48 PM
Click to view gregmns's profile gregmns 2 posts since
Mar 17, 2008
2. Re: HTTP Status 500 Aug 5, 2008 1:35 PM
in response to: JDoyle

Thanks for the help JD.

However, it appears that some dependencies are not up to date:

dpkg: dependency problems prevent configuration of cnr-client:
cnr-client depends on libqt4-core (>= 4.3.0); however:
Version of libqt4-core on system is 4.2.3-0ubuntu3.
cnr-client depends on libqt4-gui (>= 4.3.0); however:
Version of libqt4-gui on system is 4.2.3-0ubuntu3.
cnr-client depends on libqt4-sql (>= 4.3.0); however:
Version of libqt4-sql on system is 4.2.3-0ubuntu3.
cnr-client depends on libssl-dev; however:
Package libssl-dev is not installed.
dpkg: error processing cnr-client (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
cnr-client

I know I'm just a linux dummy, but how do I update the dependencies.

Greg


Click to view BigDawg's profile BigDawg 64 posts since
Nov 27, 2007
3. Re: HTTP Status 500 Aug 5, 2008 5:11 PM
in response to: gregmns
The client is broken for Ubuntu 8.04 due to a change that was made to the OS. We have a new client in QA now that we hope to release soon.
Click to view BigDawg's profile BigDawg 64 posts since
Nov 27, 2007
4. Re: HTTP Status 500 Aug 5, 2008 5:13 PM
The status 500 error is usaully experienced after allowing a page to be open for a long time and then attempting to navigate away or use a feature on the standing page. The problem is that the session timed out but wasn't handled properly. If you go to the home page and navigate back you should be fine as a work around until we can fix the problem.