What does Windows error code 1172 (ERROR_NO_TRACKING_SERVICE) mean?

 
Previous Next
ERROR_POINT_NOT_FOUND ERROR_NO_VOLUME_ID

ERROR_NO_TRACKING_SERVICE

The Distributed Link Tracking workstation service is unavailable.

ERROR_NO_TRACKING_SERVICE has value 1172 (0x494). Windows uses distributed link tracking and NTFS object identifiers to help references survive file or directory moves. This result says the workstation-side tracking service needed by the operation is not running.

Relevant Windows component

The Distributed Link Tracking Client service is named TrkWks. Microsoft describes it as maintaining links between NTFS files within a computer or across computers on a network. Whether a particular application should depend on it must be determined from the API and deployment contract, not merely from the error text.

Possible causes

  • TrkWks is stopped, disabled, or missing from the expected system image
  • service startup failed because of dependency or system damage
  • a hardening baseline disabled the service without accounting for the application
  • the operation runs during boot, shutdown, or service transition
  • the caller converted a related NTSTATUS/HRESULT and lost the original context

Evidence to collect

  • failing API and source/destination file or link operation
  • TrkWks state, startup type, exit code, and recent Service Control Manager events
  • filesystem type and whether NTFS object identifiers are involved
  • machine/domain/workgroup context and whether the operation crosses volumes or computers
  • original code domain before any conversion to Win32 or HRESULT

Administrator actions

Verify the service state and the organization's service policy. If link tracking is a required feature, correct the startup failure or policy conflict and start the service through normal service-management tools. Do not enable it solely because the code exists if the application can use a documented fallback and the environment intentionally disables tracking.

Application handling

For optional link-repair behavior, continue using the known path and warn that automatic tracking is unavailable. For an operation whose correctness depends on durable object tracking, fail before recording an incomplete tracking relationship. A retry is reasonable after the service reaches a running state; a tight loop while it remains stopped is not.

Developer guidance

Log the service dependency explicitly and avoid presenting 1172 as a generic network outage. Where possible, design references with stable application identifiers or database records rather than relying exclusively on filesystem path repair. Tests should cover tracking enabled, service stopped, moved object, and missing object identifier.

Difference from related codes

ERROR_NO_VOLUME_ID says the volume identifier required for tracking could not be found even if the service is running. ERROR_SERVICE_NOT_ACTIVE is a generic service-state result. Error 1172 identifies the tracking workstation service needed for link-tracking functionality.

Example

A document application records an NTFS link-tracking reference before moving a source file. A security baseline has disabled TrkWks, so the tracking operation returns 1172. The deployment owner either restores the required service policy or configures the application to use its own stable document identifiers instead of silently assuming automatic link repair.

References

Looking for a different code? Search another status or error code.