WAS will not be able to start if there is no machineĭeleting these keys and letting WAS regenerating them could solve the problem with a side effect: These machine keys are used to encrypt sensitive information in nfig or web.config (e.g. Machine keys exist but WAS unfortunately cannot access them for some unclear reason. Upon first start after upgrade, WAS will try to create new machine keys if there isn't any, or access the old machine keys left from the old OS. The failure happened because WAS could not access the machine keys during startup. Investigation. But I will definitely help you resolve the issue and unblock your usage.
So I'm not sure what is the unique condition to trigger it, and this needs further Unfortunately, I cannot reproduce the exact same issue on my computer - I tested the upgrade using both Win10 Enterprise and Windows Server 2016, and neither had this problem. Thank you so much for providing the logs.
0 kommentar(er)
