troubleshooting:slotting_was_setup
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
troubleshooting:slotting_was_setup [2017/11/07 16:44] – created Gerard Nicol | troubleshooting:slotting_was_setup [2017/11/07 16:49] (current) – removed Gerard Nicol | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | |||
- | |||
- | |||
- | ===== Was slotting setup to run automatically? | ||
- | |||
- | Slotting is usually setup to run automatically via Windows Scheduler or Crond, but sometimes people prefer to run it manually by running a script from the command line or double clicking on a bat file. | ||
- | |||
- | Was your slotting setup to run automatically? | ||
- | |||
- | {{: | ||
- | {{: | ||
- | |||
- | |||
- | ===== Why has your automatic slotting stopped? ===== | ||
- | |||
- | There are several reasons why your automatic slotting may have stopped working: | ||
- | |||
- | - Windows Scheduler has been setup to run the task using credentials that have expired or been revoked. | ||
- | - There is a problem with Windows Scheduler. | ||
- | - The Windows bat file that runs the slotting program has been moved, renamed or deleted. | ||
- | - The TapeTrack User-ID that the slotting program runs under has been revoked, deleted or the password has changed. | ||
troubleshooting/slotting_was_setup.1510073095.txt.gz · Last modified: 2025/01/21 22:07 (external edit)