Appendix A: Known Issues

These are the major known issues currently known for all Code Collaborator components.

Smart Bear announces new publicly-available versions of Code Collaborator using a mailing list.

If you want to sign up to receive these e-mails, you can do so with our secure sign-up form:

•

Case 34564: Reports have missing data. When the server is running on Linux systems, there can be issues with unavailable fonts or available fonts with sufficiently different font metrics that can cause the reporting engine to not render content. Workaround: Install the Microsoft True Type fonts (msttcorefonts on Debian-based systems).

•	Server will not launch on 64-bit Windows if 64-bit JVM is used. Workaround: Use the 32-bit VM on 64-bit Windows.

•	Case 26177: Chat log incorrectly encodes leading spaces, so sometimes when entering e.g. code snippets the text doesn't come out as expected. Workaround: Put a little character (e.g. a period) at the beginning of the line.

•	Case 43101: When clicking on the link of a file in the Review Overview page the file will not be displayed at front if IE is set up to open pop-ups in tabs. Workaround: Go to Tools -> Internet Options -> Tab Settings -> Select "Always open pop-ups in a new window.

•	Sometimes, after an upgrade, when a user logs in she sees a CSS page dump in the browser instead of going to the home page. Workaround: Just go directly to the homepage. Because you are already authenticated, that will work.

•	Case 30131: In some very special cases the intra-line difference-engine doesn't properly highlight the inside of the line. The entire line is still highlighted, so users are still properly shown the main lines of the differences.

•	Case 27502: Increasing the default font size in FireFox v1.5.0.7 or IE 7 can result in a very distracting (but still functional) user interface. Workaround: Change back to the default font size.

•	Google Chrome is not supported, due to lack of support in Ext JS. However, submit any (non-beta) Chrome defects to us, and we'll try to address them.

•	When running FireFox with the Firebug or Greasemonkey plug-in, the Side-by-Side view is sluggish to load. This is even true when Firebug is marked "disabled."

•	Search results may not return all results without noting the truncation. This can happen if many results match the search but are inaccessible to the user.

•	Diff viewer keyboard shortcuts do not work in Opera. In general, Opera is not a supported browser. While most functionality is available, some features, such as keyboard shortcuts do not work.

•

When upgrading from 2.1 to 4.0 the server sometimes starts up with a JDBC error. Solution: Check the database and LDAP password fields in installation-directory/tomcat/conf/Catalina/localhost/ROOT.xml. Repeated dollar signs ('$'), necessary in Code Collaborator 2.1, are not required. Remove them and restart.

•

Custom reports with a large number active columns or filters; or with long filter text can break the bookmark, SQL, Printable, and CSV links in Internet Explorer. Because the links contain all the filter information, the URL's can exceed the IE's maximum URL length (2083 characters). Workaround: Use FireFox for complex reports

•	Character set differences that change the location or number of line breaks can change the way comments get promoted. Workaround: If necessary, use the auto-detected character set to make comments and mark conversations read.

•	Character set differences that change the location or number of line breaks result in metrics that may not be perfectly correct. The metrics for files are computed using the auto-detected character set.

•	If there are multiple files with the same filename (but different paths) in a review the automatically linked filenames in review text (custom fields, chat, etc.) may not link to the intended file.

•	Case 31758: Can get an ClassCastException using the new v2.0 client against a v1.x server with certain commands and with certain v1.x servers. Workaround: Make sure your client and server versions match.

•

Case 24209, 23958: The system PATH variable is not always updated properly by the installer, or the PATH variable is updated but running applications are not notified, so it takes the user logging out of Windows or even rebooting before the command-line client can be used.
Workaround: Reboot your machine. Or try just logging out and logging back in to Windows.

•	Case 34477: Command-line echo passwords back when you type them. Workaround: Use Java v1.6.

•	Dock Icon on MacOS: The tray notifier process creates an icon in the MacOS dock. If you launch the GUI Client it creates another copy of the same dock icon.

•

Case 42393: Error initializing Add to Review Wizard occurs with reason 'CVSROOT may only specify a postive, non-zero integer port'. This is an error reported by the CVS command line client (cvs.exe) when there is an unexpected colon in the the CVSROOT value. The Collaborator client requires that cvs.exe work normally on the repository. Using a different CVS client, such as the Cygwin client, can fix this problem.

•	Case 34890: Files on certain changelists show up as new files -- without a "previous version" diff. Workaround: This is known to happen with certain 2005 versions of Perforce. Upgrading to the latest Perforce client fixes this issue.

•	Directory entries are ignored - so adding an entire directory does not show up in a review.

•	Symlinks are not supported pre-commit - a Symlink uploaded pre-commit will show invalid content in a review.

•

Cases 37383, 42625: Adding changes does not find modified Vault source files, and reports many or no modified files. This is a known issue with the SourceGear Vault client that can be resolved by setting the "Detect modified files using CRC's instead of modification times" in the Vault client options for "Local Files".

•	Case 42153: "Unable to determine the source control server" error can occur when adding modified files. There must be a corresponding Team Foundation Server working folder for the directory configured in the GUI client, or the directory specified for the command line client to avoid this error.

•	Case 42787: Team Foundation Server integration will not work with non-English installations of Visual Studio .NET. Regional settings for other locales are supported, but installing a non-English Visual Studio prevents correct parsing of tf.exe output.