.NET agent setup timed out due to bad FMS performance (4242558)

Chat now with support

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

.NET agent setup timed out due to bad FMS performance
Description

.NET agent setup process timed out. .NET counter agent setup task result indicate "Unknown - max timeout reached.".
Cause

Foglight Management Server (FMS) performance is bad resulting in delay when communicating with the Foglight Agent Manager (FglAM) where the .NET agent is to be installed.
Resolution
1. Delete the existing .NET agent from the Application Server Administration dashboard.
2. Go to the Administration | Manage Registry Variables dashboard.
3. Set the global default value of the "TaskTimeoutHint_Seconds" variable to 100 seconds.
4. Re-install the .NET agent.

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title