Agent Restart required, version mistmatch
We have seen agent restarts required in the past with version mismatches however they were always on the servers we were tracking and not on our collector server. Seen below I collector server shows that it is on an older version. If I look at the server info however and see which fixpack version is installed it says .8054, and not 7880. I know we have no UEM licenses for our Non-Production environment, but will that cause an agent to mismatch if we have UEM turned on?
There should be no need based on what you have described to run the Web Server Agent on the server, so I would stop the process and mark it Disabled in services so it does not get started again in the future
Hi
I think the problem here is that the "Dynatrace Web Server Agent" (which runs as a Windows Services) has received the updated version as you probable restarted that Windows Service. The Dynatrace Web Server Module that is loaded into IIS however is still running on the old version. Can you try to reset IIS or recycle your application pools and verify if this problem goes away?
Andi
IIS was restarted and we don't see errors on the IIS agent anymore however despite a restart on the collector as well, we still are seeing the DTWSagent showing under the agent groups with agent restart error. This is showing under our collector server however for development environment. We don't even have IIS installed on that server, so I am not sure what the dtwsagent would be doing on the collector server to show the agent needs restarted.
Is there a need to have the webserver agent running on the collector/server? I am not sure why the web agent is installed on ours and tihnk this iswhy we are getting agent restart required error for dtwsagent on our collector.
Below is the screen shot of all services for dynatrace running on our collector and primary server for dev:
