When starting the module (for example, ArchiveShuttle.Module.DellModule.exe), the following entries appear in the log:
2025-12-01 21:01:11Z| 3048| 39| INFO| Start|Starting component ArchiveShuttle.Modules.Common.Base.PerformanceLogger.
2025-12-01 21:01:12Z| 3048| 39|ERROR| Start|Error while starting performance logging Boolean CounterExists(System.String, System.String, System.String)
Category does not exist.
at System.Diagnostics.PerformanceCounterLib.CounterExists(String machine, String category, String counter)
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName, Boolean readOnly)
at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, Boolean readOnly)
at ArchiveShuttle.Modules.Common.Base.PerformanceLogger.Start()
Symptoms may include:
Error messages about performance logging at service startup.
Component PerformanceLogger fails to start.
In some cases the module continues to run but without performance logging; in others, startup may be impacted depending on configuration.
ArchiveShuttle uses Windows Performance Counters for internal performance logging.
The error:
Category does not exist.
indicates that the expected performance counter category is missing, corrupted, or inaccessible on the local Windows server. This can be caused by:
Corrupted or incomplete performance counter configuration in Windows.
Missing registration of specific counter categories.
OS-level issues after upgrades, patching, or role/feature changes.
Permissions or security hardening that prevents access to performance counters.
This is an environmental issue in the Windows operating system, not a bug in ArchiveShuttle.
Because the problem is environmental, the resolution is to inspect and repair the Windows Performance Counter configuration on the affected server. Recommended steps:
Verify Performance Counters on the Server
Open an elevated Command Prompt or PowerShell.
Use standard Windows tools (e.g., typeperf -q, lodctr /q) to verify that performance counter categories are present and not reporting errors.
Confirm that other applications using performance counters do not show similar issues.
Repair Performance Counters (if appropriate for your environment)
In many Windows environments, administrators use commands such as:
lodctr /R to rebuild the performance counters from backup.
These commands must be run by a Windows administrator and may require planned downtime or change control per your internal policies.
Always follow your organization’s change management, backup, and validation procedures when modifying OS-level components.
Check Permissions and Hardening
Ensure the ArchiveShuttle service account has permission to read performance counters.
Review any GPOs, security baselines, or hardening tools that might block or remove performance counter categories.
Re-test ArchiveShuttle Module Startup
After verifying/repairing performance counters:
Restart the ArchiveShuttle Dell Module (or affected module).
Confirm that the log no longer shows “Error while starting performance logging – Category does not exist”.
Verify normal operation of the module.
Engage System/OS Team if Needed
If the issue persists, share the error and findings with your Windows server/OS team or infrastructure administrators.
They may need to perform deeper OS-level diagnostics to restore the affected performance counter categories.
Important: This issue originates from the Windows environment, not from ArchiveShuttle code. The recommended remediation is to review and repair the server’s performance counter configuration and related permissions in your environment, then restart the ArchiveShuttle module and confirm that performance logging starts successfully.
