Diagnostic |
Description |
|---|---|
Client version mismatch Message: The application <app_name> with PID (<app_pid>) is a different version to the iCDB Server for project <project_path>. You cannot connect an iCDB Client with <version_diff_type_name> <client_version> of software to an iCDB Server with <version_diff_type_name> <server_version> of the software. Please contact your system administrator for advice. |
Issue Type: Error Configuration File: None Keys: None Description: Reports when a client machine has a different version of software from the server machine. |
Project server address change Message: The iCDB Server for project <project_path> was run on a different machine. Current address is <current_server_address>. Previous address was <previous_server_address>. Please verify the change was intentional. |
Issue Type: Warning Configuration File: None Keys: None Description: Reports when server for the project changes. This happens when multiple users work on the project, but not at the same time. Use the Remote Server Configuration Manager to ensure that the project is configured the same for all users. It has the additional benefit of allowing multiple users to work on the project at the same time. |
Project location change Message: The project location has changed. The current project path is <current_project_path>. The previous project path was <previous_project_path>. Please verify the change was intentional. |
Issue Type: Warning Configuration File: None Keys: None Description: Reports when the project location changes. If the copy was not intentional and multiple users were working concurrently, the users can be confused as to which location is the correct one. Also, changing the location of the database can decrease performance. Note: This message also appears in a mixed-platform environment when you switch operating systems and cause a change in path format from POSIX to UNC or UNC to POSIX. |
Project RSCM change Message: The iCDB Server for project <project_path> was started by a different RSCM Server. The current RSCM address is <current_rscm_address>. The previous RSCM address was <previous_rscm_address>. Please verify the change was intentional. |
Issue Type: Warning Configuration File: None Keys: None Description: Reports when the RSCM Server associated with the project changes. If the change was not intentional the performance can be diminished because the server would be started on different machine and the access to client or the file server could have changed. |
Project RSCM enabled Message: The last project <project_path> session did not use RSCM Server. Now <rscm_address> as RSCM Server is used. Please verify the change was intentional. |
Issue Type: Warning Configuration File: None Keys: None Description: Reports when an RSCM Server is detected on a project that previously was not associated with an RSCM Server. If the change was not intentional the performance could be diminished because the setup (client, server, and filer) has changed. |
Project RSCM disabled Message: The last project <project_path> session used RSCM Server <rscm_address>. Now usage of RSCM Server for this project is disabled. Please verify the change was intentional. |
Issue Type: Warning Configuration File: None Keys: None Description: Reports when an RSCM Server is no longer detected on a project that previously was associated with an RSCM Server. Any project that has at least two users working on it, whether at the same time or not, should be set up with the Remote Server Configuration Manager. This ensures the same setup (client, server, filer) for all users. It allows for predictable startup, and it eliminates problems when a user opens a project that is already opened by another user. |