Wednesday 5 August 2015

All about that Internal 500 error

We amateurs have faced many a times this cumbersome Internal 500 error while accessing maximo URL. Well, I have faced it many times. So I would like to share my experience and hopefully somebody might get some help while troubleshooting.

When you try to open the maximo url and it is really frustrating to see the Internal 500 error. We all know that this is definitely related to database connection. Don't lose your head and check the following:

  1. Database password might have expired. Try to connect to the database instance with your credentials, if it says password expired, reset the password (with DBA's help if needed) and restart your server.
  2. In case above step does not help you, check if configdb is running or admin mode is ON.
    • Run the SQL query "select varvalue from maxvars where varname='CONFIGURING'", if it returns 1, update varvalue to 0.
    • Run the SQL query "select vavalue from maxvars where varname='ADMINRESTART'", if it returns ON, update varvalue to OFF.
I know most of us have already figured out the above obvious checks by now. But I had run into 500 error beyond this too. The maximo.ear file was rebuilt and redeployed. After the server was restarted, we were ready to see the wonders our Java code has created but instead we were shown an Internal 500 error. We double and triple checked for password expiry, running configdb or admin mode ON, but could not track our culprit. Here the problem was encrypted password.

So the resolution steps followed in this case are:
  1. From the folder path [IBMSMP]\maximo\applications\maximo\properties, open the file maximo.properties. Modify the file with mxe.db.password=<database password> and set mxe.encrypted=false.
  2. Run the command encryptproperties.bat from [IBMSMP]\maximo\tools\maximo path.
  3. Rebuild the maximo.ear file and redeploy it. Restart the server.
Hopefully, you will be rid of Internal 500 error by now.

5 comments:

  1. There are additional scenarios like maximo application ear is not mapped to correct vritual hosts during deployment which can lead to similar error.

    ReplyDelete
  2. hello sir

    I tried all the above steps but am still facing the issue.

    ReplyDelete
  3. Hello Nithin,
    Please do check whether the EAR file which is running in your application server is pointing to the correct database. This error will come when your application is not able to connect to the database.

    ReplyDelete
  4. Also, as commented by Prashant above, please check if application ear is mapped to correct virtual hosts.

    ReplyDelete
  5. How to check application server is pointing to the correct database and also how to check application ear is mapped to correct virtual hosts.

    ReplyDelete