-
Type:
Bug
-
Resolution: Answered
-
Priority:
Medium
-
Affects Version/s: None
-
Component/s: Indexing
-
Severity 2 - Major
-
0
An incorrect perforce configuration can lead to the following error:
Perforce Server Version: P4D/DARWIN80U/2009.2/249896 (2010/06/04) Perforce Server Time: 2010/08/17 12:06:28 +1000 EST Non-zero exit status determining latest revision: Unable to login: Command failed to execute - non-zero exit code: 1 - Fatal client error; disconnecting! EOF reading terminal. Error testing connection. com.cenqua.fisheye.config.ConfigException - Problem communicating with repository : Unable to determine latest revision. No revision information was returned - check path exists, permissions and output encoding com.cenqua.fisheye.perforce.client.P4ClientException - Unable to determine latest revision. No revision information was returned - check path exists, permissions and output encoding Connection failed.
The error message isn't very helpful, but it is thrown when you are using ticket based authentication and do not provide a password in the FishEye repository configuration.
Executing the p4 commands in a terminal reveal:
The message coloured in red goes to stderr. We should read this when something goes wrong.