Error Server SID Mismatch 628 (0x274): How to Fix it

Restarting the server process can help with this issue

Reading time icon 3 min. read


Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

ERROR_FLOAT_MULTIPLE_FAULTS
XINSTALL BY CLICKING THE DOWNLOAD FILE
A message from our partner

For fixing Windows errors, we recommend Fortect:

Fortect will identify and deploy the correct fix for your Windows errors. Follow the 3 easy steps to get rid of Windows errors:

  • Download Fortect and install it on your PC
  • Launch the tool and Start scanning your PC for Windows errors
  • Right-click on Start Repair to deploy the right fix for each error encountered during the scan
Download Now Fortect has been downloaded by 0 readers this month, rated 4.6 on TrustPilot

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

  1. Open the command line.
  2. Next, run the following command to restart the service: net stop <service_name> && net start <service_name>
    net stop
  3. Check the SID with the following command: whoami /user
  4. Compare the SID and ensure that it matches the one expected by the client.

2. Update the service logon user

  1. Press the Windows key + R and enter services.msc.
    Services RUn command ERROR_AUDIT_FAILED
  2. Locate the affected service, right-click it, and choose Properties.
  3. Next, head to the Log on tab and confirm the credentials or enter them again.
  4. Save changes.

3. Clear cached credentials

  1. Press the Windows key + R and enter control.
    control panel command in run dialog box
  2. Next, navigate to Credential Manager.
    Microsoft Teams Freezes
  3. Remove all saved credentials for the server.

4. Verify Active Directory Configuration

  1. Ensure that the user account exists and that it’s active.
  2. Open the command line.
  3. Run the following command to check the domain trust status: nltest /sc_verify:<domain_name>

5. Re-register SPN

  1. Open the command line and run the following to ensure that SPN is correct: setspn -L <service_account>
  2. If the SPN is missing, register it with: setspn -A <service/hostname> <account>
  3. 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

  1. Update group policies. You can force the update with the following command: gpupdate /force
  2. Check for duplicated SIDs. You can do that with PsGetSid tool and the following command:  psgetsid <machine_name>
  3. Ensure that the correct users and groups have all the necessary permissions.
  4. Use Event Viewer on both the client and the server to inspect the log for any issues.
  5. Restart both the client and the server.
  6. Verify all configurations.
  7. 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.

More about the topics: error, server

User forum

0 messages