Error Server SID Mismatch 628 (0x274): How to Fix it
Restarting the server process can help with this issue
3 min. read
Published on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
ERROR_SERVER_SID_MISMATCH usually affects system administrators, and if you encounter it, you might experience access issues. This can be fixed, and this guide will show you how to do it.
How can I fix ERROR_SERVER_SID_MISMATCH?
1. Restart the server process and check the server process SID
- Open the command line.
- Next, run the following command to restart the service:
net stop <service_name> && net start <service_name>
- Check the SID with the following command:
whoami /user
- Compare the SID and ensure that it matches the one expected by the client.
2. Update the service logon user
- Press the Windows key + R and enter services.msc.
- Locate the affected service, right-click it, and choose Properties.
- Next, head to the Log on tab and confirm the credentials or enter them again.
- Save changes.
3. Clear cached credentials
- Press the Windows key + R and enter control.
- Next, navigate to Credential Manager.
- Remove all saved credentials for the server.
4. Verify Active Directory Configuration
- Ensure that the user account exists and that it’s active.
- Open the command line.
- Run the following command to check the domain trust status:
nltest /sc_verify:<domain_name>
5. Re-register SPN
- Open the command line and run the following to ensure that SPN is correct:
setspn -L <service_account>
- If the SPN is missing, register it with:
setspn -A <service/hostname> <account>
- After that, check if the issue is resolved.
Keep in mind that this method only applies if you’re using Kerberos authentication.
6. Other tips to try
- Update group policies. You can force the update with the following command:
gpupdate /force
- Check for duplicated SIDs. You can do that with PsGetSid tool and the following command:
psgetsid <machine_name>
- Ensure that the correct users and groups have all the necessary permissions.
- Use Event Viewer on both the client and the server to inspect the log for any issues.
- Restart both the client and the server.
- Verify all configurations.
- If using a cluster, and sure that nodes have synchronized configurations and constant SIDs.
ERROR_SERVER_SID_MISMATCH also comes with the following message: 628 (0x274) The server process is running under a SID different than that required by client. In most cases, this issue is caused by your configuration, and to fix it, you just need to make a few adjustments.
This isn’t the only issue, we wrote about ERROR_CLIENT_SERVER_PARAMETERS_INVALID and Error Synchronization Required which can also affect server administrators, so feel free to check them out.
Our latest article covers, Error_Nointerface, so don’t miss it if you’re dealing with networking problems.
User forum
0 messages