Symptoms: Currently there is potentially 3 scenarios in which you may encounter this error:
Scenario 1: When user gets to the desktop, they will automatically see a popup with Error 0x9401 No Boot Logon on Disk.
Scenario 2: When user attempts to encrypt or decrypt a device, they receive Error 0x9401 Invalid Parameter.
Scenario 3: As soon as user attempts to launch SDCC, client will immediately encounter the error 0x9401. (no dialogue to enter user id and password).
Troubleshooting Steps
SDPin.exe relies on SDService.exe, and will show 0x9401 if the service is not running when SDPin attempts to start.
SDPin will stop once the error is dismissed.
- Check if SDPin.exe is running.
- Check if SDService.exe is running.
Scenario 1: If the error shows Boot Logon not on disk, we should check the System Event log for errors relating to SDService.exe not starting, and then the Application event log for a more complete error.
Scenario 2: If the error shows Incorrect Parameters or Parameters are incorrect, we should check the systems Disk Management screen.
We are looking for partitions that show as RAW on any of the encrypted disks.
Scenario 3: You may observed that both Scenario 1 or Scenario 2 were verified to not match, and client is not able to see SDCC running. It's likely you may not see any system event or application logs for SDService.exe to show up as well. You may want to note for your case if there was any Security Software controlled by policy which possibly have prevented SDService from launching.
Proposed Solutions:
The following are the proposed solutions which could fix issue depending on each scenario:
Scenario 1: Verify the error against Jira. Build numbers of the SecureDoc version should be in the Application Event log, and you should be able to
You can search Jira for fixes for older versions. If you do not find a fix for the version you need. We should collect the Debug logs for SecureDoc, Application
and system event logs, and an application dump file. We can utilize DebugDiag to create the dump for the WinMagic SecureDoc Service as an NT service.
Scenario 2: If the user is trying to decrypt or encrypt a disk and receive this. Check Disk Management, and check the disks connected for any partitions that show as Raw. Verify whether the customer needs to recover data from the Raw partition, and then format them as Fat32, or NTFS, before trying to encrypt or decrypt again.
Scenario 3: If both Scenario 1 and 2 did not match client issue, please check to see if you can try manually starting SDService and then attempt to launch SDCC