Problem with SwarmAgent - Please help

Hi Everyone,
I ran into this error message in swarm agent today and I have no idea how to fix it so that swarm agent will re-build the lighting in my level. Please help!

09/06/2015 UE 4.8.3 Project on Window 10 platform, 16G memory

8:37:11 AM: Starting up SwarmAgent …
8:37:11 AM: … registering SwarmAgent with remoting service
8:37:11 AM: … registering SwarmAgent network channels
8:37:11 AM: … initializing SwarmAgent
8:37:11 AM: … certificate check has failed
8:37:11 AM: … initializing cache
8:37:11 AM: … using cache folder ‘C:/Users/Bruce Oberleitner/AppData/Local/UnrealEngine/4.8/Saved/Swarm\SwarmCache’
8:37:11 AM: … recreating SwarmAgent cache staging area
8:37:11 AM: … initializing connection to SwarmCoordinator
8:37:11 AM: … using SwarmCoordinator on RENDER-01
8:37:13 AM: … SwarmCoordinator failed to be initialized
8:37:13 AM: … initializing local performance monitoring subsystem
8:37:16 AM: … initialization successful, SwarmAgent now running
8:37:22 AM: [Interface:TryOpenConnection] Local connection established
8:37:23 AM: [Job] Accepted Job 1FCF59B5-465A61A1-F63019BF-922C0BDB
8:37:37 AM: [Interface:OpenChannel] Error: System.IO.IOException: The process cannot access the file ‘C:\Users\Bruce Oberleitner\AppData\Local\UnrealEngine\4.8\Saved\Swarm\SwarmCache\AgentStagingArea\8487AD2E5DBA413C81373D29B2915895.C6E70FEB4BA9D33343FE04B19A9C8B92.mtrlgz’ because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream…ctor(String path, FileMode mode, FileAccess access, FileShare share)
at NSwarm.FSwarmInterface.OpenChannel(String ChannelName, EChannelFlags ChannelFlags) in D:\Perforce\Epic\UE4\Engine\Source\Editor\SwarmInterface\DotNET\SwarmInterface.cs:line 1590

The error says that Swarm is being used by another process. This can usually indicate that there are two of them open. Try checking the task manager to see if there are two processes for Swarm Agent running and closing them both down. When you go to build lighting again only one should open.

Well, as far as I can tell there is only one process trying to run. What’s odd is that it seems to work with other levels just fine. Since this is the only level I started fresh in 4.8.3, could that be the problem?

Here’s another strange thing. Swarm agent is still “running” and processing something. It looks like its trying to process the Exporting scene part of the job. Could it be that this part of the process is taking too long and causing some sort of confusion in swarm agent?

So here’s so more information from the log files

Starting up SwarmAgent …
… registering SwarmAgent with remoting service
… registering SwarmAgent network channels
… initializing SwarmAgent
… checking certificate
… certificate check has failed
… initializing cache
… using cache folder ‘J:/Data/SwarmCache’
… recreating SwarmAgent cache staging area
… initializing connection to SwarmCoordinator
… using SwarmCoordinator on RENDER-01
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] Coordinator ping failed
… SwarmCoordinator failed to be initialized
… initializing local performance monitoring subsystem
… initialization successful, SwarmAgent now running
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Interface:TryOpenConnection] Local connection established
[Job] Accepted Job D47B06D1-4317996A-0B6EA4A9-8A03D3AF
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false
[Maintain Jobs] Job is AGENT_JOB_UNSPECIFIED
[PingCoordinator] Determined that we couldn’t ping the coordinator
[PingCoordinator] CoordinatorResponding is false

There are a ton more of these “Ping Coordinator” statements in the logfile. I have no idea what it’s talking about…

I am beginning to think that this is a Windows 10 specific bug. Just a hunch on my part.

Hello,
we have installed the UE4.24 and the GPULightmass 4.24.
When we try to build a scene the GPU Renderer crashes with the message “Illegal Memory access was encountered”
I already tried all the versions and the same thing happens to me, help please, GTX 1070 ASUS 8GB, MEMORY RAM 16 GB

https://forums.unrealengine.com/core/image/png;base64