Can't connect project to perforce?

Development Platform & Builds
, , ,
1

One of our team members is having trouble connecting a project to perforce. We’re using a custom build based off of 4.6.1. Other team members can connect fine, and he’s been able to connect other projects using stock UE4 engines without a problem either.

None of the modifications we’ve made to the engine should affect perforce - they’re all rendering related.

When he tries to connect, it looks like everything is working fine. It even says connection successful. However, it does not actually behave as if it’s connected, and if he returns to the source control window it says “working disconnected.”

How can we debug this issue? There’s not a lot to go on in the logs.

Thanks!

Info Client username_Users-Mac-Pro_5486

Info Update 2014/08/07 14:32:27

Info Access 2015/02/05 10:15:00

Info Owner username

Info Host Users-Mac-Pro.local

Info Description Created by username.

Info Root /Users/uname/Perforce

Info Options noallwrite noclobber nocompress unlocked nomodtime rmdir

Info SubmitOptions revertunchanged

Info LineEnd local

Info View0 //depot/… //username_Users-Mac-Pro_5486/…

Info View1 -//depot/Branches/… //username_Users-Mac-Pro_5486/Branches/…

Info specFormatted

Info func client-FstatInfo

Info Source control is disabled

2

Hi,

Since you are using a source build, if you can connect a debugger you should look at what is happening in FPerforceConnectWorker::Execute. When the RunCommand call is made, any errors will be reported in the InCommand.ErrorMessages array.

The log messages you have pasted are from the (less verbose) message log. The output log may reveal more information. If you follow the instructions here to enable verbose logging you should get more info out of the output log.

First things I would expect this to be would be a problem with permissions or ticketing, but I cant be sure without verbose logs.

3

Hi Tom,

Thanks for your help working through this. I added the following lines to my DefaultEngine.ini to try to add more verbose logging:

[Core.Log]
LogActor=VeryVerbose

But the output in “Source Control Log” in the Source Control Login window is unchanged - same as what I posted above.

I stepped through FPerforceConnectWorker::Execute, but didn’t see any errors. When it reaches the last line to return InCommand.bCommandSuccessful, it returns true. I tried stepping out to try to see if the problem was further upstream, but I reached what looks like some threadpool/worker/dispatch code and lost the thread…

Any further suggestions would be appreciated!

4

Oops, apologies I should have been more detailed. The lines you should be adding are

[Core.Log] 
LogSourceControl=VeryVerbose

If connection seems to be working fine, then please post a log from when another operation fails (check in, add etc.).