If the Auto Re-index could not run, the users will receive a trigger email indicating the following.
“MM/DD/YYYY Automatic Reindex could not be run.”
Possible Reason #1:
Most of the time re-index is not running because the DBC is in use and the system cannot get exclusive lock on it.
Possible Reason #2:
If you happen to be using a SQL Server or any other outside programs to access the ManEx DBFS files, check the current sessions and see if they are frozen in attempting to access the tables. This will then leave the tables open all night and cause the Datamaintenance not to complete successfully. This could additional cause Corrupt Table issues if not addressed.
Suggested Solution #2:
Create a backup script and make sure to include line of code that will kill all active sessions before starting the backup. This way all users and/or software still connected will be kicked off of the system before Datamaintenance is scheduled to run.
| 
