Overview:
In some rare cases, the Nodeware Windows Agent will not complete the installation process.
The issue itself, and the inability to install the agent stem from registry keys either missing or not being set correctly.
The issue itself, and the inability to install the agent stem from registry keys either missing or not being set correctly.
Here is an article that discusses the issue.
https://learn.microsoft.com/en-us/dotnet/framework/network-programming/tls#schusestrongcrypto
Solution:
Check the registry @
HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node\]Microsoft\.NETFramework\<VERSION>: SchUseStrongCrypto
This registry key has a value of type DWORD.
In most cases, this key is not present and will need to be imported.
If that key is not present at all, you should import the following registry keys which will cover all .Net versions and have the correct value set by default.
[HKEYLOCALMACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEYLOCALMACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEYLOCALMACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEYLOCALMACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
If for some reason the above doesn't fix the issue, attempt the install from a command prompt with elevated privileges using the following command.
msiexec.exe /lxv* c:\foo\install.log /i NodewareAgentSetup.XXXXXXX.msi
NOTE: you can put any path/filename for the log. And the XXXXXX above is your specific filename
Next, compress the install.log and submit a support ticket that includes the above log file.
HKEY_LOCAL_MACHINE\SOFTWARE\[Wow6432Node\]Microsoft\.NETFramework\<VERSION>: SchUseStrongCrypto
This registry key has a value of type DWORD.
- The above key DWORD value needs to be set to "1"
In most cases, this key is not present and will need to be imported.
If that key is not present at all, you should import the following registry keys which will cover all .Net versions and have the correct value set by default.
[HKEYLOCALMACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEYLOCALMACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEYLOCALMACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
[HKEYLOCALMACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
"SchUseStrongCrypto"=dword:00000001
If for some reason the above doesn't fix the issue, attempt the install from a command prompt with elevated privileges using the following command.
msiexec.exe /lxv* c:\foo\install.log /i NodewareAgentSetup.XXXXXXX.msi
NOTE: you can put any path/filename for the log. And the XXXXXX above is your specific filename
Next, compress the install.log and submit a support ticket that includes the above log file.
Comments
0 comments
Please sign in to leave a comment.