Harweb cannot connect to the Database.
The database instance name, schema name and password remained the same.
Type Exception report
The server encountered an internal error () that prevented it from fulfilling this request.
javax.servlet.ServletException: harweb.HServlet.service(): error while processing CMD=null<br>javax.servlet.ServletException: harweb.HServlet.getHDB(): Can't get hDB from pool. Check your 'harweb.cfg' and restart your servlet server.<br>java.lang.NullPointerException
at harweb.HServlet.getConnectionPool(Unknown Source)
at harweb.HServlet.getHDB(Unknown Source)
at harweb.HServlet.service(Unknown Source)
Release: SCMNCR99000-12.5-Harvest-Software Change Manager-Named User-Competitive Replacem
Windows, Unix/Linux installation
1. Check if you can connect to the Database via CA Harvest Workbench.
2. If this is working then the database connectivity is valid, therefore the problem
is with the Harweb configuration.
3. Review the harweb.cfg file, it should contain the following lines as an example for database connectivity:
4. In a command prompt, try tnsping harvtest - to see if it resolves the SID from the TNSNames.ora file properly.
If the tnsping is successful then continue to the next step else contact your DBA to resolve the SID.
5. Insert the following lines (without the < >) into the harweb.cfg file to test the connectivity credentials:
6. Save the harweb.cfg changes and restart the web application and Harweb, if this is successful then most likely the problem is the credentials in the harweb.dfo file are incorrect, use the command line "svrenc" to recreate the harweb.dfo file with the same credentials that you used in step 5, remove the User= and Password= from the harweb.cfg file, save the changes and then restart the web application and Harweb again. If the credentials in step 5 do not work then contact your DBA to resolve the proper database credentials.
These steps can also help to solve the problem if the harvest.cfg file is incorrect:
1. Insure the bit level of the web application server install (ie Tomcat, JBoss, etc), the JDBC driver, the CA Harvest Client install, and the Harweb install are all at the same bit level. You cannot mix 32bit and 64bit combinations in this regard.
2. The Harweb installation also requires the CA Harvest Client install because sub-components are shared.
3. Check if the web application server (ie Tomcat, JBoss, etc) is working properly without Harweb in the picture.
If the web application page does not display then the install for this is suspect.
4. Confirm the correct JDBC Driver and bit level of the driver is used for your database Version.
5. Try reinstalling the web application server and completely delete it's directory before reinstalling it (Example):
- Uninstall Tomcat
- Delete Tomcat directory
- Clear any references of Tomcat from registry entries and environment variables.
- Do a fresh install of Tomcat
6. Do a fresh install of Harweb, not a reinstallation.
7. The "svrenc" command line utility information may be found in the CA Harvest Command Reference Guide.