SOLVED: He had installed Scheduler once into an unusual directory, then he turned off User Account Control, then he uninstalled the Scheduler, leaving the old installation path in the virtualized section of the registry, then he reinstalled normally. The net result is that the Database wrapper object was looking for the SQL database file in the old/wrong location, causing the initialization from ACP to fail. This could never have been solved without an online session.