too many 'Web Server' agents connected,license exhausted;
Hello everyone!
First, what we have done:
We upgrade our dynaTrace from 5.0 to 5.6:
- We upgrade our license, like Upgrade and Migration to 5.6 (Prerequisites)
- After upgrading the license, i have done server, collector and client upgrade (Upgrade and Migration to 5.6#Server,CollectorandClientUpgrade/MigrationUsingdtmigration , Point 3)
- Than my department looked at the client and der is no agent. So, oh, we forgot to install the new agent version.
- On the webserver, the new agent version (5.6) is now installed. We looked again in the Client. Oh, there are to many agents connected, why?
- So, we uninstall the old agent version (5.0) from server.
Now:
On the local machine is the client 5.6, on server 1 are the new versions from collector, server etc of dynaTrace and on server 2, we is dynaTrace Agent 5.6 installed.
The license overview looks like:
The agent overview looks like:
Oh, i have one information:
Yesterday we had this issue. Today, i logged on my local machine and start the client. There was only one agent, without issue, but no application. The application manager says me: " 3 auto-detected applications" (client -> edit system profile -> application) . after a little time, i saw one of this 3 is shown in the application overview. For a short time, i can see throughput, but not for long, and in the agent connection status now the issue;
Too many 'Web Server' agents connected;license exhausted;
(also after client start for some time, agent is without issue, than i have the issue)
Now my question, how to solve the issue? What can we do?
Hi Thomas
Thanks for the very detailed explanation. The main problem that I see here is that your license seems to only include 1 Windows .NET Server. Which means that you can connect as many .NET Agents from a single Windows Server as you want. But - in your example you talk about the Web Server Agent which requires a separate license.
I would reach out to our licensing team and figure out if something went wrong during the license upgrade. I assume that you had a different license with 5.0 which included all the web server agents you needed.
If you solve this problem your web server agents will connect successfully - they wll start PurePaths and applications should be detected correctly.
Andi
I used the dynaTrace Web Server Agent 5.6, because, on our server, where the old Agent was installed, it was dynaTrace Web Server Agent 5.0. So, i installed the new version of the Agent like the collector, server, analyses server...
i installed the new software versions of all components after upgrading our dynatrace license from 5.0 to 5.6 . so, i'm not understand, why after correct license upgrade, the new software version not do there work.
Mh, our license status in eService:
I forgot some detail:
I looked up, to see, how the agent is called correctly. The configuration tool 'dragentconf.exe' in C:\Program Files (x86)\dynaTrace\dynaTrace Agent 5.6.0 says: it is a dynaTrace .NET Agent 5.6.0 .... the old version dynaTrace .NET Agent 5.0.0...
The old agent service is deactivated. the new one is activated. all new version components are working, only the new agent version not.
Thanks for the details. I will ask somebody to look into your license file and see what the issue might be. I dont think you made a mistake on your agent configuration.
Hi,
Your license is for a .NET agent, the installed windows service is for the Web Server agent. Please open the .NET Configuration Tool you referenced from the Start Menu -> All Programs -> dynaTrace and select your application worker process (probably "w3wp.exe" with argument of "-ap <your-app-pool-name>"
Rick B
FYI, I just looked up your old license. This was also for one .NET agent. Please follow the above instruction and you should be all set 
Hello Richard!
Before i installed the new Agent , i copied agent details from the old agent in '.txt' file, so that i'm not forgot a config entry.
After i copied the details, i installed the new agent and the checked the Agent values. It looks like:
You can see, the copied details from the old version in .txt and the entry of the agent in the new version.
You see, i done your instruction before i saw, that i have an issue....(Too many 'Web Server' agents connected;license exhausted; ).
Any ideas?
It looks like that specific configuration is not active, there are a couple of reasons why this might be:
- There is no activity on the application so IIS has shut down the worker process. Try sending a request (fully authenticated if applicable) to the app and see if the agent comes up.
- the argument you have hard-coded (-ap "ASP.NET v4.0") has changed and is not exact. Use the '+' to select manually from a list of running .net processes, as long as you can verify your app pool worker process is running (again, send traffic to the application).
So long as you have the windows service on, you will have that error. You are not licensed for the Web Server type of license so this is not relevant so much as getting the agent to appear in the lower part of the configuration tool ("Running .NET process matching your Agent Configuration").
Rick B
Hi Rick!
Your idea "use the +" was nice! 
and i deactivated the windows service "dynaTrace Web Server Agent 5.6.0". Now my agent connection state looks like:
I think, now the agent worked correctly. I got application throughput!
Thanks for help!
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
October 2017
Announcing Dynatrace's Community Member of the Month for October 2017, Ram S.! Click here to read more! 