| Previous | Next |
| FRS_ERR_INVALID_API_SEQUENCE | FRS_ERR_STOPPING_SERVICE |
FRS_ERR_STARTING_SERVICE
The file replication service cannot be started.
FRS_ERR_STARTING_SERVICE is Win32 error 8002 (0x00001F42).
What to verify
Verify whether NtFrs can initialize its database, RPC endpoints, replica-set state, and required directories. Check File Replication Service event log, Service Control Manager status and exit code, and NtFrs database and staging paths.
Likely causes
- the service database is damaged or locked.
- dependencies or RPC are unavailable.
- the service identity lacks access.
- SYSVOL or replica paths are missing.
- startup is blocked by pending recovery.
Troubleshooting steps
- Collect File Replication Service event log.
- Record Service Control Manager status and exit code.
- Correlate NtFrs database and staging paths with the File Replication Service event log, Service Control Manager, Directory Service and Netlogon events, RPC diagnostics, and replica-set state.
Handling, retry, and recovery
Fix the first startup event, preserve the FRS database until recovery choice is known, and migrate SYSVOL to DFS Replication when the domain still relies on legacy FRS.
Related errors
FRS_ERR_SERVICE_COMM means the service is running but cannot be contacted; this code means startup itself failed
Example
NtFrs stops after database recovery events following a disk incident. The administrator captures the event sequence and performs the supported nonauthoritative recovery instead of repeatedly starting the service.
References
Looking for a different code? Search another status or error code.