# Perforce Error Message - Can't Clobber Writable File

**URL:** <https://forums.unrealengine.com/t/perforce-error-message-cant-clobber-writable-file/281818>\
**Category:** Audio\
**Tags:** version-control, unreal-engine, Perforce, question\
**Created:** [April 27, 2014, 3:32pm UTC](https://forums.unrealengine.com/t/perforce-error-message-cant-clobber-writable-file/281818 "2014-04-27T15:32:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ohmk](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ohmk](https://forums.unrealengine.com/u/ohmk)\
**Post date:** [April 27, 2014, 3:32pm UTC](https://forums.unrealengine.com/t/perforce-error-message-cant-clobber-writable-file/281818/1 "2014-04-27T15:32:48Z")

</div>

![4991-clobber.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/0/f/d/0fd2dd70a48e368cea7ad0ddbb218c76e3169d78.png)

Getting an issue when my friend uploads a file to perforce and I right click to sync, it says it cannot clobber the writable file when trying to open the BP and the editor says ‘Failed to load assets’. I just found out that the Path error at the top is just a warning and can be ignored, thought that may have been part of the issue.

EDIT: And now I’ve found this in my saved/logs file:

```
[2014.04.27-16.16.13:864][912]LogUObjectGlobals:Warning: Failed to find object 'Object /Game/Blueprints/Caleb/LargeFan.LargeFan'

```

Why is the path looking in /game/? there’s no such folder! It’s UnrealDemo1/Content/Blueprints/Caleb/Largefan! Secondly, why LargeFan.LargeFan and not LargeFan.uasset?

---

<div class="post-metadata">

**Author:** ![TomSarkanen](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tomsarkanen/32/918655_2.png) [@TomSarkanen](https://forums.unrealengine.com/u/TomSarkanen)\
**Post date:** [April 27, 2014, 5:04pm UTC](https://forums.unrealengine.com/t/perforce-error-message-cant-clobber-writable-file/281818/2 "2014-04-27T17:04:41Z")

</div>

Hi,

This sounds like a bug, could you post some detailed repo steps please?

Also, did you have the Blueprint open at the time? Can you sync when you restart the editor?

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_f54268a3](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_f54268a3](https://forums.unrealengine.com/u/anonymous_user_f54268a3)\
**Post date:** [April 27, 2014, 5:28pm UTC](https://forums.unrealengine.com/t/perforce-error-message-cant-clobber-writable-file/281818/3 "2014-04-27T17:28:26Z")

</div>

As a workaround, try opening the file properties, right click menu on the file in windows explorer, set it to read only.

That may let you get past it. I think Perforce likes to control the read and write settings of files, and if they get changed it can mess it up sometimes. I’ve had this, or something similar, a few times over the last couple years with using Perforce.

---

<div class="post-metadata">

**Author:** ![ohmk](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@ohmk](https://forums.unrealengine.com/u/ohmk)\
**Post date:** [April 27, 2014, 6:23pm UTC](https://forums.unrealengine.com/t/perforce-error-message-cant-clobber-writable-file/281818/4 "2014-04-27T18:23:18Z")

</div>

I’m not exactly sure what fixed it, whether making it read only, editing my workspace → Advanced and changing Clobber settings to overwrite writable workspace files when getting revisions. It may have been a combo of the two and a restart of the editor but I’m not entirely sure. But it’s working!

---

<div class="post-metadata">

**Author:** ![kikillokun1111](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@kikillokun1111](https://forums.unrealengine.com/u/kikillokun1111)\
**Post date:** [August 21, 2025, 10:15am UTC](https://forums.unrealengine.com/t/perforce-error-message-cant-clobber-writable-file/281818/5 "2025-08-21T10:15:37Z")

</div>

Thanks, I was having the same issue and toggling on Read-only in windows explorer solved the issue for me
