Log in to Rational Focal Point client results in Error "404"

The following symptoms may be seen:

• A 404 error appears on the client log-in screen
  
  
• In Tomcat stdout_yyyymmdd.log, the following error is logged
  
  
"Critical: Context initialization failed
  org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'server' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.RuntimeException: Focal Point node Server-name[A1D2AD84284C38EDF9BA18A610389999] startup failed.

  Caused by: java.lang.RuntimeException: Focal Point node Server-name[A1D2AD84284C38EDF9BA18A610389999] startup failed. ..."
  

Nodeid is conflicting with other nodeid.

In the example above [A1D2AD84284C38EDF9BA18A610389999]

Generally this is caused by concurrent shutdown of both the Application server and Database server Application server needs to clear a flag in the database, when shutting down application. If Database server is already shut down, the flag remains in the database, and will cause conflict or duplication.

This issue occurs on a PostgreSQL Database and Tomcat Application Server running on Microsoft Windows.

To resolve this issue, follow these steps on the server where the Rational Focal Point and database server are installed:

1. Stop the Tomcat service for Rational Focal Point
   
   
2. Click Start > Programs > PostgresSQL 8.x > pgAdminIII
   Login to Postgres database
   
   
3. Right click on the server entry
   
   
4. Click Connect
   Enter the password for the postgres user
   
   
5. Click on the Focal Point database
   
   
6. Click Tools > Query Tool
   
   
7. Execute the sql query:
   
"select * from node;"
. The list of nodeid is displayed
   
   
   
8. Execute the sql query:
   
"delete from node;"

   
   The list of nodeid is cleared
   
   
9. Restart the Tomcat service for Focal Point

Note: To avoid this error, it is recommended to shut down the Application server first. Once shutdown is completed, then shut down the Database server.