Go to Settings>Notification Server>Site Server Settings>Site Servers.

Note: If someone wants to specifically select a Task Server to register to itself, the manual assignment will be the method. The SMP was the available one to be selected with fewer connections. In this scenario, the SMP itself had only 94 connections/shares at that point of time, while the Task Server itself had already 100 connections/shares established.

And then attempt to connect to the one with fewer shares, which in this case is.

Then it checks which one has fewer connections/shares:.

The Task Server is asking for a list of available Task Servers:.

Ordering servers by task server load sharesĬTaskServerNetCommsConnection::_readServerListDocument(): Task Server:, Http:, Https:, Active: ĬTaskServerNetCommsConnection::_readServerListDocument(): Found servers. Task Server:, Active:, Http:, Https:, Value:, Shares: Pending Task Server Registration - initial timeout 15 sec, max timeout 300 sec, max retries 5. ĬTaskServerNetCommsConnection::_buildTaskServerUrl(): url: ĬTaskServerNetCommsConnection::_buildTaskServerUrl(): Server:, Http:, Https:, Use Https: So, Task Server selection algorithm is always used to find the Task Server to assign agent to.įor example, here are some agent log entries (top entries are the most recent ones) while trying to register to a Task Server. is the SMP and is the Task Server that we want to register to itself:Īttempting to register on Task Server over. The Client Task Agent knows nothing about the Task Server plug-in, even if they both installed on the same box.

The assumption that a Task Server will register to itself automatically is incorrect.

Notification dll not registered