cannot publish my build with Unreal BuildPatch Tool on windows 10 64 bit

International
, ,
1

I cannot publish my build with Unreal BuildPatch Tool on windows 10 64 bit , it shows an error like “acess denied , you cannot run this program on this machine”.

2

I run this command and i have already verified the ids are correct

C:\Users\jorda\Desktop\BuildPatchTool\Engine\Binaries\Win64>BuildPatchTool.exe -OrganizationId="o-4jspkplymbak2d27rgywwaynj7lfm9" -ProductId="43dc0bd2e2d948c0980791d7f4f015df" -ArtifactId="814208e7305b47b3a82e94af7a2438b9" -ClientId="xyz***" -ClientSecret="6/4MqTk***" -mode=UploadBinary -BuildRoot="C:\Users\jorda\Desktop\BabyAdventurePackaged\\" -CloudDir="C:\Users\jorda\Desktop\CoudDir\\" -BuildVersion="1.0.0" -AppLaunch="C:\Users\jorda\Desktop\BabyAdventurePackaged\demonic.exe" -AppArgs=""
Beginning chunk generation of version 1.0.0 of artifact 814208e7305b47b3a82e94af7a2438b9. Build root: C:/Users/jorda/Desktop/BabyAdventurePackaged
Failed to retrieve list of binaries from Epic services. Please check your provided OrganizationId, ProductId and ArtifactId are correct, and that you should have access to create binaries for this artifact.
LogBuildPatchTool: Error: Tool exited with: 6
Tool exited with: 6
3

Did u find any solution?!!

4

Hey there Kongratz,

Looking over the code you supplied it looks like the wrong ClientSecret is being utilized, you’ll want to look under product settings > BPT credentials to locate this.

This should resolve your issue, if not, please let me know!

5

BuildPatchTool.exe -OrganizationId=“o-lafe5ugbtf4n4pg9clbx74ss7p2jvk -ProductId=“a6653f7af0864fc7b5c713f08c00ec66” -ArtifactId=“352cad09a5284c9ea7c2dd0839d9d643” -ClientId=“7891********0” -ClientSecret=“igj8****************” -mode=UploadBinary -BuildRoot=“C:\Users\HaZem\Desktop\Windows” -CloudDir=“C:\Users\HaZem\Desktop\CLOUD” -BuildVersion=“1.5.1” -AppLaunch=“Street Pursuit.exe” -AppArgs=”" , Here we go
Access is denied

6

Hello

I have the same issue, did you find a fix for this?

Thanks

7

Hey there @MrStaggan & @Kongratz

If this issue is still persisting, please write in with a private case as we will need to dig in deeper into coding to find out more information on the error.

Thanks!