Doing a fresh install.
I am able to install and run the client with no issues.
The Kinetic part is not working as expected.
Trying to get to the api help page and am getting an error.
https://kinetic.embedtek.local/Kinetic2021/api/help/v2/
ERR_SSL_KEY_USAGE_INCOMPATIBLE
Can anyone help me out? I am searching log files and am not seeing anything.
What binding are you using? Did you install a certificate with the keys?
i am going to try a different endpoint binding
You need to allow the keys of that certificate to be accessed by the account running Your App Pool
Start → Run → MMC
File → Add / Remove Snapin
Certificates → Computer Account → Local Computer
Find certificate click Manage Private Keys
Give Full Control to your Epicor Account
But yes if you switch to UsernameSSLChannel you may be able to bypass this. (may)
Same error.
I allowed full control the keys of the cert to the EpicorAdmin account.
I even rebooted the server to see if that did the trick.
back to where I started so I know the moving parts from here on out.
client works.
Just not Kinetic form.
Swithc to UsernameSSLChannel does that make a difference?
When using browser, binding does not matter.
Is there more error info in Brower security tab?
Where would that be? I am using EDGE on the server.
Thanks,
Is it new server used? What OS is there? May be TLS is outdated on server or client?
Check if there are any errors in Event Viewer\System or Security on server side.
If no, I could suggest to switch on SChannel detailed logging and look in the event viewer what errors are shown, as described here:
But it requires reboot…
No errors or messages.
This is a new server, though it may be windows server 2022. I’ll see if I can get 2019 installed and retry…
Did you ever find a solution for this? I am thinking it is Windows Server 2022 that now uses TLS1.3. We upgraded to Windows 2022 and got the same error. Classic client runs fine. Rest Services run fine.
Looks like Windows Server 2022 does not like cert generated y EAC. You have to create your own.
It does not look the same issue to me. Here only browser client fails to work. Your link says that none of the clients work. Looks like something different.
