License Information: Failed to communicate with the Specops Deploy Server. Make sure that the server is installed correctly and running. Detailed error message: No connection could be made because the target machine actively refused it. Event: Performance counters is out of memory
The following warning message below is received when you try to open the Specops Deploy App Control center:
Failed to communicate with the Specops Deploy Server. Make sure that the server is installed correctly and running. Detailed error message:
No connection could be made because the target machine actively refused it.
This usually means that the Specops Deploy App service isn’t up and running.
Open up “Services” on the Specops Deploy App server and try to start the service.
If the service starts: Close Specops Deploy App Control Center and open it again, the warning message should now be gone.
If the service do not start: Check the Event Viewer’s Application log on the server, most likely you have received the following error event:
Critical error when starting the service.
Exception is ‘System.InvalidOperationException: Custom counters file view is out of memory.
at System.Diagnostics.SharedPerformanceCounter.CalculateMemory(Int32 oldOffset, Int32 totalSize, Int32& alignmentAdjustment)
at System.Diagnostics.SharedPerformanceCounter.CreateInstance(CategoryEntry* categoryPointer, Int32 instanceNameHashCode, String instanceName, PerformanceCounterInstanceLifetime lifetime)
at System.Diagnostics.SharedPerformanceCounter.GetCounter(String counterName, String instanceName, Boolean enableReuse, PerformanceCounterInstanceLifetime lifetime)
at System.Diagnostics.SharedPerformanceCounter..ctor(String catName, String counterName, String instanceName, PerformanceCounterInstanceLifetime lifetime)
at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName, Boolean readOnly)
at SpecopsSoft.SpecopsDeploy.Server.ServerPerformanceCounters.SetInstanceValue(Guid instanceName, Int32 instanceValue, DeploymentOperationClientState clientStateToSet)
at SpecopsSoft.SpecopsDeploy.Server.SpecopsDeployService.OnStart(String args)’
.Net has reached its limit for the amount of memory it is allowed to allocate to performance counters.
You need to edit the .NET machine.config file to increase the memory available to .NET
On the Specops Deploy App server, locate the machine.config file and edit it:
Go to the following rows in the file:
<performanceCounters filemappingsize=”xxxxxxxx” />
So instead of xxxxxxxx (your value) try and change it to 32900000 (32,9 mb), that will hopefully be enough.
You can set the value as high as 33554432 but we don’t want to maximize it or go over the limit, that can lead to other issues.
Save the changes in the file and reboot the server.
Try again to start the service (if it’s not already up and running) and open the Specops Deploy App Control Center.
Hopefully you will not recieve the warning message this time.