I keep having random workstations getting the errors below in the event logs. They show up in the Admin Kit as online, but they aren't controllable. Everything shows running, but you can't for instance, start/stop any tasks or applications from the AK. It doesn't download updates at all, automatic or manually. The only thing to do is to restart the network agent service, or reboot and then everything works fine. I noticed this happening on some workstations last week, and today I had 2 more do it at the same time. Any ideas?

Event Log Info:
1:
Source: klnagent
Failed to connect to the administration server
Error information: 1262/0 (The maximum number of connection was exceeded.), O:\CS AdminKit\development2\transport\tr\transportimp.cpp, 2162

2:
Source: klnagent
Failed to connect to the administration server
Transport level error communicating with 'http://10.10.10.10:13000': timeout expired.
Error information: 1255/0 (Error was occured in trasnport layer. Error code - '0'.), O:\CS AdminKit\development2\transport\trf\socket\transfersocket.cpp, 435

How many nodes are on the network?

Is there server accessible for other services when this happens?

I noticed the IP address down below, do you have the network agents pointing to the admin kit by name or by IP? If by name, use klmover on the problematic pcs and point to the admin kit by IP.

-We have 46 nodes.

-Yes, the server is accessible to all other services from the problematic PC.

-All network agents use the IP of the AK.

I ran a troubleshooting task from the klnagchk utility on the network agent. the results are below:



What's up with the error 2 lines up?

Also, the update task gave the following error until I finally restarted the network agent:


All clients are working now since I restarted the network agent on those that had problems, but that's not to say it won't happen again. Any ideas?

Thanks

Are you using the latest version of the AK? What SQL are you using (msde, mysql, mssql)?

Yes, using AK 6.0.7010 and MSDE 2005.

AK 1710 has some issues. Another thread suggests to force the UDP port. That didn't work for me. I created a Network Agent policy, applied my settings and nothing worked. If I removed the policy things started working again. After a week of dorking around with every setting I could think of I noticed that the policy is defaulting a 24 hour sync period. Changed that to 15 mins to match the client default and I've been good ever since. That, or an auto update from KL fixed something in the interim .

Hello,
I'm facing the same issue with the same error messages.

Except restarting network agent(which is working), has anyone found a solution that prevent this kind of events to happen again?

I'm using Administration kit 6.0.1710

Thanks a lot.