p4 Submit aborted Error - How to resolve

Question

A p4 check-in failed with the following error:

Submit aborted -- fix problems then use \'p4 submit -c XXXX\'.
Some file(s) could not be transferred from client.
         


        

Answer 1

Sometimes P4 fails to submit files, that contain unusual encodings. To resolve the problem, revert them, then use

p4 add -t binary <fileset>

Answer 2

When this usually happens it's because either you don't have access to the files, or rights to push them in.

When this happens to me I break up the changelist into pieces to find the offender. This can be done in a number of ways. Ask a new question if you need pointers.

Answer 3

p4 revert -a --- revert all failed files.

p4 opened --- display necessary files to submit.

p4 submit -c 'changelist'.

Answer 4

In my case, I had an "undo-undo" changelist where I was fixing an issue with a previous submit. To fix the issue I had made changes to another file which was showing in the changelist, however, it showed the error when I tried to submit (Submit aborted -- fix problems then use 'p4 submit -c xxxx'.)

I noticed on right click in the P4V client that the file was "not checked out" (even though it was showing in the changelist as modified).

The solution : I checked it out again manually, and was then able to submit fine.

Answer 5

Resolving problems for large changeset submission failures

I had to submit a changeset recently that had 400,000+ files, and it failed with the error:

Submit aborted -- fix problems then use 'p4 submit -c 11111'.

There was not enough history in the console buffer to review what failed and what succeeded. So I ran the command suggested in the error message and output stdout to a file:

p4 submit -c 11111 > p4_submit_11111.txt

When this ran, errors (stderr) was output to the commandline, allowing me to resolve the problems (as described in other answers). In my case, it was a file I'd added to the changeset but since deleted, as per the first point in Mark's answer:

open for read: /home/myUserName/yada/_files.txt: No such file or directory

So to deal with this, I just reverted it from the changeset...

$  p4 revert  /home/myUserName/yada/_files.txt
//P4Root/Proj1/yada/_files.txt#none - was add, unlocked and abandoned

... and then re-submitted the changelist using the same command:

p4 submit -c 11111 > p4_submit_11111.txt

This submit succeeded.

Answer 6

Perforce may also not like the naming of your file.

e.g. example@somefile.txt: The system cannot find the file specified.