Repository moved; Fisheye indexing now failing

[DI2E Licensing]

Our developers moved a repository. We updated the fisheye link. Now are getting the following error:

{quote}

Repository index failed due to error com.cenqua.fisheye.rep.RepositoryClientException: com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: fatal: Invalid revision range 262fb8392ab85a51903ccb7d5cf162d2b7cc379c..37c272c1541607ba3df69855324ca80398552ced com.atlassian.fisheye.dvcs.handler.DvcsProcessException: Error while communicating with VCS: fatal: Invalid revision range 262fb8392ab85a51903ccb7d5cf162d2b7cc379c..37c272c1541607ba3df69855324ca80398552ced com.atlassian.utils.process.ProcessException: While executing: "/usr/bin/git rev-list --reverse --date-order 262fb8392ab85a51903ccb7d5cf162d2b7cc379c..37c272c1541607ba3df69855324ca80398552ced" in [/opt/atlassian/fisheye-data/var/cache/Open-Storefront/clone] com.atlassian.utils.process.ProcessException: Non-zero exit code: 128

{quote}

Any suggestions?

thanks

[Alex Goodchild]

still the same fix as of 3.7.0 (on an individual repo)

[Alex Goodchild]

I resolved it through reindexing (Settings->Maintenance->Reindex).

[Tom Davies]

Does 'git rev-list --reverse --date-order 262fb8392ab85a51903ccb7d5cf162d2b7cc379c..37c272c1541607ba3df69855324ca80398552ced' run OK on the command line?

If the repository is not too large it would be worth reindexing it.