Product Documentation
Abstract
Known Problems for IBM Rational Synergy 7.1.0.6
Content
|
APAR | Internal ID | Description/Workaround | Status |
| PM00514 | R#34527 | The installation guide for Synergy 7.1 does not specify correct entries for Solaris 10 pam.conf. The pam_unix.so.1 module is no longer supported under Solaris 10. Workaround: cmsynergy auth requisite pam_authtok_get.so.1 cmsynergy auth required pam_dhkeys.so.1 cmsynergy auth required pam_unix_cred.so.1 cmsynergy auth required pam_unix_auth.so.1 cmsynergy account required pam_unix_account.so.1 | Fixed in Fix Pack 7.2.0.1. |
| PM06267 | R#35173 | wastebasket directory defaults to %USERPROFILE% from the Synergy (Java) client There is no way to specify a user-specific alternative path for the work area wastebasket | Fixed in Fix Pack 7.2.0.2. |
| PM14645 | R#36426 | Intermittent ESD Failures ESD is crashing sporadically. The effects are: - Synergy sessions are unable to start at times. - Change becomes unusable until the host is reenabled. Workarounds:
2. Use web mode, which doesn’t require ESD. | No plan to fix. |
| PM23430 | R#37984 | Conflict detection returns conflicts which are not real conflicts Conflict detection will always report "Bad task" for any fix task even though the "bad task" is included in the project's update properties. | Fixed in Fix Pack 7.2.0.2. |
| PM25711 | R#38463 | Synergy is reporting an implicitly included conflict because of renamed object The issue is that Synergy reports an implicitly included conflict for an object version in the baseline if that object version has been renamed in the current project. | Fixed in Fix Pack 7.2.0.2. |
| PM27642 | R#38773 | Deleted file does not get deleted from all work areas If a modifiable directory is used in multiple projects and these projects are handled by different clients, a change of the membership of the directory done in one project will not update the other projects work area. Workaround: A Sync can be used to detect the work area conflict created by the membership change in the other project and the conflict can be resolved to add or remove the files from the work area. | No plan to fix. |
| PM29242 | R#39008 | "Out of Memory" error occurred after the network was disconnected and recovered during synchronizing | Fixed in Fix Pack 7.2.0.1. |
| PM34480 | R#39894 | Better error messaging when using web mode without Unix account | Fixed in Fix Pack 7.2.0.2. |
| PM35621 | R#40088 | Synergy copied Unix format files to Windows format during compare | Fixed in Fix Pack 7.2.0.1. |
| PM42975 | R#40854 | It is possible to assign the same database twice | Planned to be fixed in Fix Pack 7.2.0.3. |
| PM44759 | R#41026 | ccm dcm Synergy CLI command does not handle empty selection set gracefully | Planned to be fixed in Fix Pack 7.2.0.3. |
| PM44981 | R#41043 | Objects added to a tset while a generate is running on this tset are not considered without a Recompute | Planned to be fixed in Fix Pack 7.2.0.3. |
| PM50584 | R#41679 | Unnecessary part in Synergy admin guide for UNIX. The Admin Guide describes how to distribute cache files with symbolic links to different locations. This configuration is no longer supported. Therefore, this section should be removed from the documentation. | Planned to be fixed in Fix Pack 7.2.0.3. |
| PM58404 | R#42370 | Select "Use Default Path", both parts of the path should be updated to conform to the template | Planned to be fixed in Fix Pack 7.2.0.3. |
| PM53127 | R#41985 | Cannot remove database from Archive Conversion screen in Synergy Admin Interface Database whose archive conversion is 100% complete cannot be from Archive Conversion screen in Synergy Admin Interface if archive conversion did not remove all traces of the older archives. An old archive file will not be removed if there is an un-referenced archive entry in it because it is non-empty when the last referenced archive entry is removed during conversion. The only intervention is manual removal of such entries. Workaround: To fix this problem start a Classic CLI session and run the ccm fs_check command. This will report the warning messages for such unused archive entries which should look like the one mentioned as below: INFO: unused archive entry Archive file path: \\win2k3r2-64vive\ccmdb\ibmdb\st_root\archive\source\project\ccm_rcs\1\36\editor,v Revision number: 1.1 Delete the file manually from the above location after ensuring that the data is not needed. Once after fixing all the warnings reported from fs_check, it should be able to remove the database from archive tab. | No plan to fix. |
| PM59748 | R#42507 | Binary incompatible installation fails when using downloaded image | Planned to be fixed in Fix Pack 7.2.0.3. |
| PM61987 | R#42747 | There are no parallel warnings in Synergy client when you add or remove an object to a static directory. | Planned to be fixed in Fix Pack 7.2.0.3. |
| R#30479 | Cannot change work area properties on inconsistent project hierarchy If you have a project hierarchy with inconsistent work area properties - for example, some projects in the hierarchy have options such as 'Include project-specific directory in work area path' set and some have them unset - then attempts to change the work area properties for the entire hierarchy from the Synergy GUI or CLI will fail. Workaround: Do any of the following: a) Make the desired work area property changes individually on each project b) Change individual work area properties to make the hierarchy consistent, and then set the desired properties on the entire hierarchy | Deferred to future release. | |
| R#30637 | Installation of Synergy on UNIX systems may give the message: bsdtar: Failed to set default locale Workaround: In the absence of any other errors or warnings, this message about the locale may safely be ignored. | Deferred to future release. | |
| R#30657 | Checked in files are modifiable in the work area even after unchecking the option 'Make all Files Modifiable'
When turning off the option "Make all files modifiable" in traditional mode, the files for all checked-in objects in the project will be made read-only. However, for web mode, checked-in files that have been modified will not have their permissions changed. In both cases the conflict will be detected and reported to the user. | Deferred to future release. | |
| R#32369 | When moving a database from UNIX to Windows, the ccmdb unpack command leaves all cache files marked as read-only When moving a database from UNIX to Windows, the ccmdb unpack command leaves cache files marked as read-only. This prevents Synergy from adjusting the access and modify times of the cache files to match the times stored in the database, which in turn will cause warnings from ccm fs_check. Workaround: To avoid these warnings, the CM administrator must bring up the Windows Properties dialog for the database’s st_root directory, unset the read-only flag, click Apply, and then check the option to apply to all subfolders and contents in the resulting prompt. See also R#31030 - newlines in files must be converted when moving a database between Windows and UNIX. So, when moving from UNIX to Windows in 7.1, the user needs to run ccmdb upgrade -w AND clear the read-only Windows property as described in this CR. | Deferred to future release. | |
| R#32673 | No error to command line when trying to start a server when one is already running on the same host and port If the server port is already in use by another process when server starts, the process fails with the following message in the server log file. (The server log file is located in $CCM_HOME/log/synergy_<host>_port.log): 2009-06-09T15:49:34.364-0700 WARNING: Failed to start: SocketListener0@0.0.0.0:8300 {org.mortbay.util.ThreadedServer} | Deferred to future release. | |
| R#34784 | Warnings are reported when a database is upgraded in synergy_<database>_<server_port_number>.log After upgrading a database, you might see error in the log that look like the following: 2009-12-03T12:58:14.167+0530 INFO : Server running in share session mode as user 'tester' for database \\win2k3r2-64vive\ccmdb\ibm. {sessionmgr} 2009-12-03T13:01:15.436+0530 SEVERE : Error allocating session {asyncarchiver.AsynchronousArchiver} com.telelogic.cm.errorapi.CcmResourceException During normal behavior, Synergy kicks off an asynchronous archiver automatically five minutes after the first user session is started, which in turn attempts to start a back-end session to serve its requests. While a database is being upgraded, Synergy attempts to kick off its asynchronous archiver but the back-end session startup fails, leaving these warning messages in the server log file. The messages, when occurring during upgrade, are harmless and the database upgrades successfully. | Deferred to future release. | |
| PM04471 | R#34995 | "Getting error: ""UpdateCcmRegistryValues: GetShortPathName failed (3)"" when trying to isntall Synergy 7.1" | Fixed in Release 7.2. |
| PM07009 | R#35302 | cannot checkout objects using ""ccm co @"" in web mode CLI." | Fixed in Release 7.2. |
| PM07933 | R#35417 | Copy task does not get disassociated from change request. | Fixed in Release 7.2. |
| PM08685 | R#35566 | Log Files and uidb written to two paths | Fixed in Release 7.2 |
| PM14826 | R#36471 | Multiple parallel ccmdb operations result in hung oncheck processes | Fixed in Release 7.2 |
| PM16267 | R#36826 | Synergy Online Help won't display if Firefox 3.6.3 is the default browser Workaround: 1. In Firefox, go to Tools->Options. 2. Click Tabs. 3. Uncheck the box next to "Open new windows in a new tab instead". | Fixed in Release 7.2 |
| PM21298 | R#37596 | ccmdb check should detect duplicate bindings in a project | Fixed in Release 7.2 |
| PM26024 | R#38513 | Editing multi Line text fields by setting the text_editor fails in webmode | Fixed in Release 7.2 |
| PM26026 | R#38514 | Unable to modify upboolean attribute on a non-work area related object in Java CLI Webmode | Fixed in Release 7.2 |
| PM27162 | R#38684 | Double-click on browsing panes expands and immediately collapses object | Fixed in Release 7.2 |
| PM27612 | R#38766 | Uninstalling Windows Synergy client 7.1 to 7.1.0.2 does not clean the registry | Fixed in Release 7.2 |
| PM28671 | R#38947 | URE during the workarea conflict detection while synchronizing a workarea | Fixed in Release 7.2 |
| PM29256 | R#39014 | Error synchronizing an object in Web mode, when the object is declared twice in the same project. | Fixed in Release 7.2 |
| PM30066 | R#39152 | Workarea Filters do not work as documented - Synergy Help needs correction | Fixed in Release 7.2 |
| PM31501 | R#39400 | URE when user shows project | Fixed in Release 7.2 |
| PM32454 | R#39558 | ccmdb copy doesn't register copied database with web server | Fixed in Release 7.2 |
| PM32852 | R#39630 | Synergy 7.1 Web CLI help mentions obsolete command "ccm update_properties" | Fixed in Release 7.2 |
| PM35778 | R#40115 | Rational Synergy Administration Guide for UNIX (Informix) incorrectly states limits on length of database name | Fixed in Release 7.2 |
| PM36238 | R#40168 | Incorrect documentation in the DCM Guide about unpacking Windows db on UNIX | Fixed in Release 7.2 |
| R#40429 | I/O problem when attempting to show Change Requests for baseline compare There is a timeout that is elapsing before all the information from Change is received for change requests. Workaround: Find the following line in CCM_HOME/etc/ccm.properties: ccm.properties:ccm.changerequesttool.timeout = 30000 Change the timeout from 30 seconds (i.e,. 30000 millisecnds) to 1 hour as follows: ccm.properties:ccm.changerequesttool.timeout = 3600000 | Fixed in Fix Pack 7.2.0.1. | |
| R#43118 | A user is able to start two Java Client sessions in web mode with case - insensitive login. A user can start two Windows clients on the same machine, for the same database, if the user name is specified in a different case. This is not a supported feature, and could cause work area problems. Users should not take advantage of this loophole. | Planned to be fixed in Fix Pack 7.2.0.3. | |
| R#43117 | Synergy server may use up lots of threads if one of the backend session is not responding | Planned to be fixed in future 7.1 Fix Pack. | |
| R#43149 | Marking source file as a product causes 'Missing changes' conflicts | Planned to be fixed in Fix Pack 7.2.0.3. | |
| R#42035 | Work-area is not moved to new location when it is turned ON (from OFF) with new path value specified. Turning on work area maintenance at the same time as changing the work area path will not change the path, in a specific case. The specific case involves turning on work area for a subproject in a relative hierarchy. Workaround: If this occurs, change the work area path after the work area is turned on. | Planned to be fixed in Fix Pack 7.2.0.3. |
[{"Product":{"code":"SSC6Q5","label":"Rational Synergy"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Documentation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.1.0.6","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
22 December 2020
UID
swg27027466