Totumservice Private
↗ Repo

# 10. Troubleshooting

Work through the section that matches what you see. After each fix, re-check sc query TotumService and http://localhost:55000.

# Service will not start (error 1067)

Symptom: net start TotumService fails with The process terminated unexpectedly / system error 1067.

Meaning: The executable crashed during startup.

Common cause: Broken or incomplete single-file publish (SQLite native library not available inside the bundle).

What to do

  1. Open Event Viewer → Windows Logs → Application, source TotumService, and read the latest Error.
  2. Look for DllNotFoundException / SQLitePCL / SqliteConnection.
  3. From the repo root, republish cleanly:
check-prerequisites.bat
publish.bat
  1. Reinstall/update the service so it points at the new exe (install.bat or your redeploy process).
  2. Start again: net start TotumService.

You can also run the published TotumService.exe from a console to see the crash text immediately.

# Dashboard will not open

Service running, browser cannot connect to port 55000

  1. Confirm listening:
netstat -ano | findstr 55000
  1. If nothing is listening, check logs for web server bind errors.
  2. For Windows Service under Local System, add URL reservation (Admin):
netsh http add urlacl url=http://+:55000/ user="NT AUTHORITY\SYSTEM"
  1. Restart the service.

Wrong port — Check Plugins:WebMonitoring:Port in config.

# Files are not uploading

Work the list in order:

  1. Is the service running?
  2. Is the folder Enabled? Configuration → Folders.
  3. Does the path exist and is it readable by the service?
  4. Do include patterns match the file? (report.PDF vs *.pdf — check case/patterns.)
  5. Is the file still being written? Wait for stability (default often ~10 seconds of no size change) plus scan interval.
  6. Is the S3 provider enabled and available? Dashboard → Transfer Providers.
  7. Is the bucket name correct? Folder Destination Bucket must be valid for your credentials.
  8. Check Recent Failures in Database Explorer and Recent Logs on the dashboard.

# Uploads stuck in Uploading / Detected

  • Large files take longer; check transfer progress.
  • Network or API timeouts — see Advanced timeouts / multipart settings.
  • Antivirus locking files — exclude the watch folder if policy allows.
  • Provider disabled mid-flight — re-enable and allow retry.
  • After a crash, give the service a minute to recover multipart state.

# Failed / Failed Permanent

Error theme Likely fix
Auth / 401 / 403 API key or bucket permissions
Bucket not found Typo in Destination Bucket
Network / timeout Connectivity; raise timeouts for large files
File not found File moved/deleted before upload; stop deleting early
Provider unavailable Enable provider; check Base URL

Fix the cause; transient failures often retry. Permanent failures need a corrected environment, then a new upload attempt.

# Settings or folders not saving

  • Service must be running.
  • Data directory must be writable.
  • Browser cache — hard refresh.
  • Check logs for SQLite errors.

# Build / publish fails (developers)

  • Run check-prerequisites.bat.
  • Ensure PresignedUrlClient is cloned as a sibling repo.
  • Use publish.bat rather than a minimal dotnet publish missing native library flags.

# Where to get evidence for support

Collect:

  1. Output of sc query TotumService
  2. Screenshot or export from Database Explorer → Recent Failures
  3. Matching lines from Recent Logs or logs\TotumService-*.log
  4. Application Event Log entries for source TotumService
  5. Folder config (name, path, patterns, bucket) — redact API keys

# Next step

FAQ →