BUG: UnrealInsights: Error: Failed to connect to the store client.

General Feedback & Requests
, ,
1

Can’t run profiler using Unreal Insights and UnrealTraceServer, I tried to run manually UnrealTraceServer and it shows:

I:\Epic Games\UE_5.2\Engine\Binaries\Win64>UnrealTraceServer.exe daemon
Setting working directory
Succeeded setting ‘I:\Epic Games\UE_5.2\Engine\Binaries\Win64’ (gle=0)
Creating some shared memory
Creating a quit event
Writing shared instance info
Starting the store

Im able to run manually Unreal Insights Browser but it shows nothing, While I try to run any trace Editor complains about connection:

UnrealInsights: Error: Failed to connect to the store client.

2

Same issue. Unfortunately the only “temporary fix” for me was to restart the PC. When restarting the UnrealTraceServer I got the same issue, so it was useless.

EDIT: As I mentioned on another post (Unreal Insights Does not Connect to Server - #4 by Scienziatogm), maybe I’ve found a fix: disable all the network adapters except the main ethernet/wifi adapter, terminate the UnrealTraceServer.exe process, close the editor and open it again. These steps worked for me without restarting the PC.

3

I’m sending this to those who couldn’t find the answer. (I hope this helps you
in Unreal Engine 5.3, if you get this message you need to open UnrealTraceServer.exe (from the installation folder \UE_5.3\Engine\Binaries\Win64)

if the issue is solved, congratulations. if not you need to open the CMD (if you are using Windows)

run this in the command prompt to stop the current service:
UE_5.3\Engine\Binaries\Win64>UnrealTraceServer.exe kill

and then run this command to start the unreal trace server:
UE_5.3\Engine\Binaries\Win64>UnrealTraceServer.exe fork

note that if you open the UnrealTraceServer.exe without any switches you will see something like this:

UnrealTraceServer v1.17 / Unreal Engine / Epic Games

Usage; <cmd>
Commands;
  fork            Starts a background server, upgrading any existing instance
  daemon    The mode that a background server runs in
  kill              Shuts down a currently running instance

UnrealTraceServer acts as a hub between runtimes that are tracing performance
instrumentation and tools like Unreal Insights that consume and present that
data for analysis. TCP ports 1981 and 1989 are used, where the former receives
trace data, and the latter is used by tools to query the server's store.

Store path; [storage folder for your traces]
1 Like
4

Run this if you are still facing the same problem then restart the engine.

UnrealTraceServer.exe fork --sponsor-mode=0

Explanation:
When trying to run any trace from the editor, I got a pop-up saying

Failed to connect to the store client.

Running the UnrealTraceServer with fork didn’t work for me. I was greeted with this error:

Error: Deamon is configured to run in sponsored mode, but no sponsor pid has been specified.

Using the --help for fork command, UnrealTraceServer.exe fork --help we can see the –sponsor-mode argument

      --sponsor-mode arg  Set sponsor mode. Zero to disable, non-zero to
                          enable.

So, setting the mode to false and restarting the engine seems to fix it for me.

UnrealTraceServer.exe fork --sponsor-mode=0

To make sure it’s working, open the task manager and there should be something like this when Unreal is up and running.

image
image612×175 5.06 KB

For those who don’t know where to run the command, navigate to the Engine install directory then Binaries, then Win64

...\UE_5.5\Engine\Binaries\Win64

Then shift right click in any empty area and open CMD or Powershell whatever you have. If you opened powershell, type start cmd then press enter to start the CMD in the same exact path and you can continue from there.

1 Like