Error found in Event Viewer after OS upgrade from 2019 standard to Win OS 2022 Standard.

Hello, Thank you for reaching out. This error message is not typically from a standard Windows service but from a third-party service wrapper.  

The root cause is almost always a permissions issue. The user account that the service is configured to "Log On As" no longer has sufficient rights to manage the service after the OS upgrade to Windows Server 2022. The upgrade likely tightened security policies or reset permissions, causing "Access is denied" error when the wrapper tries to configure itself. 

How to Fix It 

1. Identify the Failing Service 

In the Event Viewer, select the error log. 

In the General tab, look for the "Source" of the event or other details that name the specific service that is failing. 

2. Check the Service's "Log On As" Account 

Open the Services application (services.msc). 

Find the service you identified in step 1. 

Right-click the service and select Properties. 

Go to the Log On tab. Note which account is being used: "Local System", or a specific user account. 

3. Grant the Necessary Permissions 

The account from the "Log On" tab needs permission to manage its own service. This is the most likely fix. 

If the service runs as a specific user account: That account needs rights to start, stop, and configure the service. You may need to re-grant these permissions. You can do this using Group Policy or, for a quick fix on a single server, using the sc.exe command-line tool. 

If the service runs as Local System: This is less common for this error, but it could indicate that a security policy is restricting the Local System account. 

4. Update the Service Wrapper

The version of the service wrapper you were using on Windows Server 2019 might not be fully compatible with Windows Server 2022. 

Re-installing the service with the new, updated wrapper often resolves compatibility issues introduced by an OS upgrade. 

I hope this helps resolve the issue. If the problem persists, please feel free to provide the name of the service that's causing the error, and we can investigate further. 

Best regards. 

Brian Huynh