Skip to main content
All CollectionsUsing PerforceTroubleshooting
Troubleshoot Common Perforce Issues
Troubleshoot Common Perforce Issues
Toshi Dávila avatar
Written by Toshi Dávila
Updated over a week ago

I am getting the error "Partner exited Unexpectedly". What should I do?

You need to set up P4 correctly. 

Please navigate to your P4 repository in the Assembla WebApp. Then, open the Instructions sub-tab and ensure you've follow the steps there to configure your environmental variables. 


Note: When you install your p4 it asks you to select a path for your workspace. Make sure to use the same workspace directory while setting the variables.


Common Errors 

error: Submit aborted -- fix problems then use 'p4 submit -c 1543' ....

This means you have hit your perforce license limit. You either need to purchase more licenses from your Account page, or remove some of your users:

  1. Check the list of all active clients using 'p4 clients'

  2. Kill unwanted users with 'p4 client -d client_name'

Unable to connect to the server perforce.assembla.com:1666 as user [*]

Please do the following:

Windows: set P4HOST=workspace_name && “C:\Program Files\Perforce\p4v”

Mac & Linux: export P4HOST=workspace_name && /Applications/P4/p4v.app/Contents/MacOS/p4v

By doing this, you will start p4v from the same console in which you exported P4HOST var before.

I run the command "p4 info" and the line about client name says it's illegal"?

Console Perforce client will set client name to P4HOST value if P4CLIENT is not present.
Since Perforce host names in Assembla may contain slashes, it will blame the client name as illegal, but nothing prevents you from setting another client name. You can set it by using P4CLIENT env variable, or by providing -c option to console client.

I am getting very slow connection speed when trying to upload to a perforce depot on my space

You may want to try to disable TCP window auto-tuning, and see if it helps. You can do this with:

netsh interface tcp set global autotuninglevel=disabled

And to bring it back:

netsh interface tcp set global autotuninglevel=normal

There are some other tweaks to solve flaky connection issues on Windows.
You can refer to this guide.

You can also try to switch to plain TCP connection by updating your P4HOST to perforce.assembla.com:1666

What should I do if I have everything configured correctly and still doesn't work?

In that case, please contact support at support@assembla.com and mention that you have followed all of our instructions here and you are still unable to access to perforce

Have questions? Email us support@assembla.com

Did this answer your question?