SDPIN start-up issue - SDPin does not start up after SES client installation or upgrade
Symptom
The SecureDoc icon - sdpin.exe - does not start up after installation or upgrade.
Cause
This issue can be caused by environment settings or by a bug in older versions.
Resolution
First check the environment variables value %SystemRoot%(c:\windows) by right clicking My Computer -> Advanced -> Environment Variables ->System variables -> Path. Ensure that the path does not point to a non-existent directory or a network directory that may not be available (e.g check user's rights to the directory). Make sure that there is a registry key for sdpin.exe under HKLM\Software\Microsoft\Windows\CurrentVersion\App. If there is, you should erase whatever data is there and try starting up the SecureDoc background task again. Lastly, you can also check the audit log and find out if you have set "server type" to be "local network". This may be checked on a SecureDoc client machine under "Options" then "Audit Log" then along the top of the tab. In the SES profile you can check this by going to the "General" options, then selecting "Audit log"; ensure you don't have "Local Network" selected. This issue only occurs in some versions and is resolved in SecureDoc 5.2.
|
Custom Fields
|