Product Documentation
Abstract
Known Problems for IBM Rational Synergy 7.2.0.2
Content
APAR | Internal ID | Description/Workaround | Status |
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. |
PM42975 | R#40854 | It is possible to assign the same database twice | Possible future fix pack candidate. |
PM44759 | R#41026 | ccm dcm Synergy CLI command does not handle empty selection set gracefully | Planned for future fix pack. |
PM44981 | R#41043 | Objects added to a tset while a generate is running on this tset are not considered without a Recompute | Possible future fix pack candidate. |
PM47206 | R#42163 | Do not use the static relative subproject's real work area when accessing the file from within Synergy | Possible future fix pack candidate. |
PM47522 | R#41308 | Web Mode client hangs if operation attempted during firewall disconnect | Possible future fix pack candidate. |
PM57822 | R#42319 | The "Copy to File system" operation can be ended silently. | Possible future fix pack candidate. |
PM58030 | R#42342 | Empty windows box after clicking "Add new users" button in Synergy Admin | Possible future fix pack candidate |
PM58079 | R#42345 | plugin strips all but first "#" character when building URL | Possible future fix pack candidate. |
PM58404 | R#42370 | Select "Use Default Path", both parts of the path should be updated to conform to the template | Possible future fix pack candidate. |
PM58823 | R#42415 | Setting resolver on task to "none" does not remove task from old resolvers "My Tasks" | Possible future fix pack candidate. |
PM58859 | R#42419 | conflict detected with symlinks in Synergy 7.1.0.5 in Web mode | Possible future fix pack candidate |
PM58867 | R#42424 | Work area sync defect (in relative mode) for "prep" or "working" | Possible future fix pack candidate |
PM59748 | R#42507 | Binary incompatible installation fails when using downloaded image After downloading the Synergy 7.1 installation image from Passport Advantage, an attempt to create a secondary installation by installing it to a binary-incompatible system fails when the steps outlined in Appendix B of the Synergy Installation Guide for UNIX are followed. The problem is that the instructions in the Installation Guide are incorrect. Workaround Run $CCM_HOME/bin/gzip and $CCM_HOME/bin/tar on the downloaded image file and then mount the filesystem to the target machine (e.g. Linux client) and run ccm_install –c. | Will be fixed in upcoming update of documentation. |
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#34132 | Terminal invoked from synergy ( for editing or for exploring the directory) not able to display Unicode characters (Chinese characters). | 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. | |
R#39764 | Failure message on compare of binary objects from CLI
It files being compared have binary content in them, then the default compare tool used by Synergy is reporting an error message such as “Diff/Merge Failed.”. Workaround Replace the default Synergy compare tool with one that can properly compare the binary files. | Possible fix pack candidate. | |
R#42580 | If you create a new object in a static directory from the CLI, the new object will not show up in the newly checked out directory in the Synergy GUI. This problem also occurs if an existing object is moved to a static directory from the CLI, or if an object in a static directory is unused from the CLI. The GUI will show the newly checked out directory, but will not show the new member. This problem will also occur if the project is shared, and another user adds/moves/removes the object from another GUI or CLI. Workaround Refresh the checked out directory from the GUI, and the new object will be visible. | Possible fix pack candidate. |
Was this topic helpful?
Document Information
Modified date:
22 December 2020
UID
swg27024335