Node Service Start then stop and shows Discovery Node Faulted (4282161)

Causes of issue - Enterprise Reporter running on the same server as ChangeAuditor, or a Server that is heavily utilized by other programs.

Review the following log  C:\ProgramData\Dell\Enterprise_Reporter\reporterServer.log for the following line 

"en Quest.Reporter.Core.Node.JobManagement.SmartNode.WmiCpuInfoQuery.GetCpuInfo(CpuDataCollection collection)"

In Enterprise Reporter 2.6.1 Smart nodes were introduced. When a Node is installed onto a computer (added to a cluster) it first scans the available resources of that server. If the server fails to be able to provide enough resources, the node service can stop and show the error in the Dell Enterprise Reporter event Log.

RESOLUTION #1:

Make sure that any server that the Enterprise Reporter node is to be installed on has the available resources to run. Check the task manager to ensure the CPU and memory is not maxed. Resolve the performance issue by adding more resources or consider installing the Node onto a server that is not being heavily used by other programs

RESOLUTION #2:

Check also that .Net 3.5 SP1 and .Net 4.0 are installed on the server running the node and that Windows updates are applied.

RESOLUTION #3:

Check the Application windows event log around the time of failure for an event such as the below (event ID 3001):

"The performance counter name string value in the registry is not formatted correctly"

Open Performance Monitor and see if there are any errors loading it or adding performance monitors for CPU and memory. If there are, consider rebuilding performance counters using the following commands: