Phil Harron

Hi, I gave up trying it with Windows 2022. I've had better success with Windows Server 2019 which had DCOM hardening switched on. With the changes to the j-interop (which I have made a PR for on GitHub https://github.com/skyghis/j-interop-ng) it can connect and activate the DCOM Server. Good luck!

Hi, I gave up trying it with Windows 2022. I've had better success with Windows Server 2019 which in my case has DCOM hardening switched on. With the changes to the j-interop (which I have made a PR for on GitHub https://github.com/skyghis/j-interop-ng) it can connect and activate my DCOM Server. Good luck!

Hi Tirumala, As mentioned, I'm experiencing exactly the same issue. I've asked the creators of the COM object we use to try it out on Windows server 2022 and am awaiting their reply. Maybe they need to provide an software update. Failing that I guess it could be a question that needs to raised with someone at Microsoft?

Hi Tobias, did you ever find a solution - I am facing a similar problem. Many thanks Phil

Hi Alex, thanks for the quick reply. I've set the Auth Level to 6 now and the windows system event is no longer present warning that the auth level needs to be raised. However, I now get the general 0x80080005 message which is proving harder to track down! Kind Regards Phil

Hello, Has anyone had any luck with raising the auth level as suggested in the Windows event log and gaining access to the DOM server. I have tried the suggestions above, however I still get an access denied message. I have also set the required registry setting as outlined in KB5004442 but that doesn't make a difference on Windows Server 2022 (However it does do the trick on an older version of Windows 2012) What am I missing? Any help would be greatly appreciated. Thanks Phil