SmartDisk is offline in NVBU Device Manager.
Looking at the Windows Services the Foundation Service is not running.
The 'smartdisk start' or 'smartdisk status' commands indicate: "Failed to connect to percolator slave".
One of the 'foundation' trace files, monitorrecent.0.txt, shows the following error:
------------------
0 140 1389860553.602 Failed to lookup account name: '1332:No mapping between account names and security IDs was done.
0 196 1389860553.602 Failed to get user token for foundation/etc/process/percolatorslave.proc
3 58 1389860553.602 Free Keyword: 'binary' Value: 'foundation/bin/percolatorslave.exe'
0 201 1389860553.602 Failed to launch slave program
0 34 1389860553.602 Failed to launch slave
-------------------
During SmartDisk installation, SmartDisk must be installed by a domain administrator on Windows.
However a non-privileged user must be provided as part of the privilege separation security feature of SmartDisk.
This non-privileged user can be a Domain or local user, specifically ccreated to run SmartDisk on behalf of the administrator.
This non-privileged user will be running almost all of the SmartDisk tasks and needs access permissions to all SmartDisk installation and storage directories.
Looking at the SmartDisk folders permissions showed that the user could not be found.
The non-privileged user had been deleted therefore the SmartDisk application cannot starting.
The machine hosting SmartDisk had been made a Domain Controller, therefore the local user database had been disabled by the Operating System.
In the event the Smartdisk non-privileged user has been deleted, one can work around this issue by creating a new domain or local user,
then change the SmartDisk user name and password as described here:
Smartdisk administrators guide
For example, use the following command:
smartdisk password []
where is the domain whose account database will be used to validate the /combination before the is stored.
If this argument is absent, password will use the local machine account database.
Once a new non-privileged user is created and SmartDisk updated with its credentials, the application should start successfully and backups resume.
