 <p>When running a <code>p4 integrate</code>, the destination for the integration should be mapped in your <code>perforce client workspace</code> which is what this error indicates:</p> <p><code>provide a branch view that maps this file, or use -Di to disregard move/deletes</code></p> <p>Using <code>p4 client</code> or <code>p4v</code>, map the following perforce depot <code>//depot/MyDemoInfo/1.0/Server/My_Service</code> into your client workspace to some directory on your machine say: <code>/myp4workspace/MyDemoInfo/1.0/Server/My_Service</code></p> <p>Then do this:</p> <pre><code>cd /myp4workspace/MyDemoInfo/1.0/Server/My_Service p4 integrate //depot/MyDemoInfo/trunk/Server/My_Service/... ... # This is optional, but a regular workflow to make sure you resolve all the conflicts # Display any conflicts (there shouldn't be any since this is the first time you're integrating into this location) p4 resolve -n ... # If there are any, use p4 resolve -as ... , p4 resolve -am ... , and then p4 resolve ... # Submit your changes after verifying it is correct p4 submit ... </code></pre> <p>And one more thing you might want to take care of is, run <code>p4 integrate</code> with the <code>-t -d</code> option so that it preserves file-types, and brings in any deleted file changes (although these 2 options might not be really required in your case but nothing wrong in specifying them).</p> <p>Also you can run <code>p4 where</code> to confirm that you're in the right perforce depot location before doing any integrations.</p>