- OS: Windows 10 build 1803 only
- Product: ndClick 184.108.40.206
Documents are not handing over to ndClick and just download in the browser locally on Windows 10 machines (specifically build 1803) AND
When Support Logging is enabled from the ndClick windows tray the following error is logged indicating that ndClick did not start (though the executable may be running).
2019-01-18 11:04:42.138 +08:00 [DBG] ndClick was closed
2019-01-18 11:04:49.349 +08:00 [INF] ndClick 220.127.116.11 has started
2019-01-18 11:04:49.579 +08:00 [FTL] ndClickKey.pfx was not found in C:\Program Files (x86)\NetDocuments\ndClick. Nothing will work. Message: Access denied.
StackTrace: at System.Security.Cryptography.CryptographicException.ThrowCryptographicException(Int32 hr)
at System.Security.Cryptography.X509Certificates.X509Utils._LoadCertFromBlob(Byte rawData, IntPtr password, UInt32 dwFlags, Boolean persistKeySet, SafeCertContextHandle& pCertCtx)
at System.Security.Cryptography.X509Certificates.X509Certificate.LoadCertificateFromBlob(Byte rawData, Object password, X509KeyStorageFlags keyStorageFlags)
at System.Security.Cryptography.X509Certificates.X509Certificate2..ctor(Byte rawData, String password)
at ndClickWinTray.ndClickTrayIcon.<>c.<SetDelegates>b__4_4() in C:\corp-build05-ndclick\_work\1\s\ndOneClickWinTray\ndClickTrayIcon.cs:line 160
2019-01-18 11:04:49.701 +08:00 [FTL] The local server didn't start
System.ArgumentException: The server certificate parameter is required.
Parameter name: options
(To see how to enable ndClick Support Logging please see the settings and locations discussed here)
Please note there may be other reasons why ndClick cannot handover like windows firewall settings and this article is specific to the permissions error seen above.
An issue exists in Window 10 1803 Windows build where permissions were set incorrectly when upgrading from earlier builds, the folder is incorrectly set to inherit from the parent folder.
This prevents the loading of the certificate files necessary to run ndClick.
Microsoft resolved the issue in the latest versions, Windows 10 build 1809 onwards has been noted to resolve this specifically.
Update. ndClick 1.1 will also resolve this issue.
Administrator access is required for this. If you are not familiar with setting permissions for folders it is not recommended to proceed.
- Browse to C:\ProgramData\Microsoft\Crypto\RSA
- Right-click the MachineKeys directory and choose Properties
- Select Security tab
- Click Advanced.
- Working installations do not inherit from the C:\ProgramData\Microsoft\ directory and allow Everyone group Read and Write access to the directory.
- Details of "special" permissions granted to Everyone group.
- Correcting your permissions to this should allow ndClick to load correctly.
- Restart ndClick once done and check the error log and test document opening.