While scanning a repository, FishEye makes calls to the version control system client (e.g. git or hg) and passes filenames, branch names and tag names as command line arguments. On Windows, there is a known bug in the Sun JVM that causes unicode characters (that are not part of the 1252 codepage) in command line arguments to be replaced by '?' characters.

This typically results in errors like:

java.lang.Exception: Problem with slurp - Repository index failed due to error - 
class com.atlassian.fisheye.dvcs.handler.DvcsProcessException: 
Error while communicating with VCS: ????c????????e??oa?a: No such file in rev 8de7550ee45b

In the Sun bug report a workaround is suggested using environment variables instead of command line arguments but that does not seem to work either.

This issue does not affect Subversion and CVS, as FishEye does not use the command line client when scanning the repository.

A workaround for this issue is to run FishEye on a different operating system.