Collector Error
We added a separate collector to our dynaTrace set up. After doing so we turned on an agent pointing to the separate collector. For the most part everything works fine, every so often a user will get this error. This error only started showing up after adding the separate collector. Is there some kind of configuration that needs to be done on the collector side to handle the load coming from a production web server?
Field not found: 'System.Exception.dynatrace_invocationCount'.
System.Web.HttpException..ctor(String message, Exception innerException) +0
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +633
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +90
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +191
I've ran into this before. In my environment it was because the Collector was "over worked" by having too many Agents pointed to it. Is there only one agent pointed to this new Collector?
For a while there where two agents pointed at the one collector but one was turned off. There could of been an agent from a developer computer pointed at the collector off and on after the second production agent was shut off. Could a production agent and a developer agent still cause the error?
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
September 2017
Announcing Dynatrace's Community Member of the Month for September 2017, Tarun A.! Click here to read more! 