Difference between revisions of "1 HTTP Status 500"

From MicroFocusInternationalWiki
Jump to: navigation, search
 
Line 1: Line 1:
 
'''One cause of HTTP Status 500 in https://serverIP:2200'''
 
'''One cause of HTTP Status 500 in https://serverIP:2200'''
  
Version:
+
'''Version:'''
 
NW6.5 sp4a, maybe earlier versions
 
NW6.5 sp4a, maybe earlier versions
  
  
Symptom:
+
'''Symptom:'''
  
 
1st) Go to https://serverNameorIP:2200
 
1st) Go to https://serverNameorIP:2200
Line 40: Line 40:
 
--------------------------------------------
 
--------------------------------------------
  
Possible Cause/Fix:
+
'''Possible Cause/Fix:'''
  
 
In ConsoleOne, select properties of the LDAP Server Object for the server in question,
 
In ConsoleOne, select properties of the LDAP Server Object for the server in question,

Revision as of 00:31, 9 March 2006

One cause of HTTP Status 500 in https://serverIP:2200

Version: NW6.5 sp4a, maybe earlier versions


Symptom:

1st) Go to https://serverNameorIP:2200

2nd) Login with valid credentials

3rd) Get:


HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

java.lang.NullPointerException at com.novell.application.welcome.UserLogin.setInfo(UserLogin.java:243) at com.novell.application.welcome.UserLogin.createLogin(UserLogin.java:118) at com.novell.application.welcome.LoginPage.doGet(LoginPage.java:118) at com.novell.application.welcome.LoginPage.doPost(LoginPage.java:17) at javax.servlet.http.HttpServlet.service(HttpServlet.java:716) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) . . . OMITTED . . . Apache Tomcat/4.1.31


Possible Cause/Fix:

In ConsoleOne, select properties of the LDAP Server Object for the server in question,

Under LDAP Server General Tab, Ensure that "Return operational attributes when all user attributes are requested" is checked. In our case, checking this box, click apply, click OK, unloading nldap.nlm, and reload ing nldap.nlm on the server fixed this issue on at least 3 different servers.

[Rant ON] Not happy the whole web management tool suite is so fragile. [Rant OFF]

Hope this helps someone.