Does UE4 / Swarm Require a "D" Drive?
I am currently experiencing issues with building lighting. When I initiate a build, Unreal gets stuck at "Gathering Scene Geometry" I looked toward the Swarm Agent and discovered this error in the log:
2:25:20 PM: [ERROR] Channel registration failed. Reason: An attempt was made to access a socket in a way forbidden by its access permissions , Callstack: at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at System.Net.Sockets.TcpListener.Start(Int32 backlog) at System.Runtime.Remoting.Channels.ExclusiveTcpListener.Start(Boolean exclusiveAddressUse) at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object data) at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.SetupChannel() at Agent.AgentApplication.Main(String args) in D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.10\Engine\Source\Programs\UnrealSwarm\Agent\AgentApplication.cs:line 133
I see that it appears to be looking for this directory: D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.10\Engine\Source\Programs\UnrealSwarm\Agent\AgentApplication.cs
My current machine only has a "C" drive as of right now. I am wondering if a D drive is required and what exactly the swarm agent is looking for here.
asked Jan 20 '16 at 07:50 PM in Installation & Setup
From the logs it looks like either Swarm does not have administrative permissions on your computer or you have a firewall blocking an needed socket for the computation. I would try to run Swarm Agent as an administrator, then open the editor and try building lighting.
You can also take a look at our Swarm Agent Troubleshooting Guide here:
The reference to D drive in the logs is from an internal usage of the Program and will have no effect on your build.
Let me know if you need any additional assistance -
answered Jan 20 '16 at 08:43 PM
Lovecraft_K ♦♦ STAFF
This error can be caused by another application already using the port. The swarm agent uses ports 8008 and 8009 by default, you can see if these are already in use and by what application using the command "netstat -o" or by using the windows Resource Monitor.
Faced with the same problem Swarm Agent. TCPView showed running NvStream processes that seemed strange. After removal of NVidia Experience app finally it worked.
answered Feb 19 '16 at 02:02 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here