This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the configuration database

After restarting the SharePoint servers, I tried to browse the SharePoint Site. I got the below error:

This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the configuration database. To connect this server to the server farm, use the SharePoint Products Configuration Wizard.

This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the configuration database. To connect this server to the server farm, use the SharePoint Products Configuration Wizard.

Cause

This issue usually occurs in case of the SharePoint can’t connect to the SQL Server for the following reasons:

  • The Database Server is down.
  • The SQL Server Services are stopped.
  • The Database server is not reachable from the Application server (Firewall Issue / SQL Server Port is closed).
  • The SQL Server license has expired.
  • The SQL Server Service account credentials were changed.
  • The App Pool account for web application is locked or disabled.
  • The farm account is locked or disabled.
  • The farm account password is expired.
  • The farm account doesn’t have
    • Allow Logon locally.
    • Logon as Service.
  • The farm account doesn’t have sufficient permission on the database server, configuration database, and content databases.
  • The SharePoint Configuration database is in recovery mode and its status is not online.
  • The farm servers are not joined properly.

Solution

The SQL Server is down.

Make sure that the Database Server is up and running.

  • If the ping cmdlet is enabled in your organization, try to ping the database server IP from the application server and front end server.

Check How to Check SQL Server Instance Connectivity from the application server to database server for a specific user.

  • If you don’t have access to the database server, check with the database administrator the health of database server, SQL server instances.

The SQL Server Services are stopped.

Make sure the SQL Server services is started and running.

  • Open SQL Server Configuration Manager.
SQL Server Configuration manager
  • From the left side, below SQL Server Services > check the service status, if stopped try to start it.
SQL Service Stopped

The Database server is not reachable from the Application server.

Try to telnet the DB server IP with the SQL Server port (the default: 1433) from APP/WFE server, and make sure it’s reachable from APP/WFE server.

Check How to Check SQL Server Instance Connectivity from the application server to database server for a specific user.

Check also the firewall configuration for SQL Server Port at Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgment?


SQL Server license has expired.

If you are working on a DVE/Test environment, the license expiration may be not monitored from the infrastructure team! therefore, if the SQL server license is expired it will lead to stopping the SQL services and will not working as expected!

below is a workaround to extend the SQL Server licence in your dev environment:

  • Just, change the machine date to the last date service was working.
  • Open SQL Server Configuration Manager.
SQL Server Configuration manager
  • From the left side, below SQL Server Services > check the service status, if stopped try to start it.
SQL Service Stopped
  • The service is trying to start.
SQL service Starting
  • Repeat all the previous steps with SQL Server Agent.
  • The services are now running.
SQL service Started
  • Again, Reset the machine date to today.
  • Try to browse the SharePoint site that should be now worked properly.

Check also SQL SERVER EVALUATION PERIOD HAS EXPIRED, HOW TO EXTEND IT?


SQL Server Service Account credentials were changed.

If the SQL server services accounts are not treated as service account,

  • The password for those accounts will be expired.
  • The account will be locked.

So if you have changed the password for those accounts from AD, it will not be reflected automatically to the SQL Server services. you must update it manually in SQL server services as mentioned below:

  • Open SQL Server Configuration Manager.
SQL Server Configuration manager
  • Within SQL Server Services, Check the SQL Server Instance and SQL Server Agent state (Running/Stopped).
SQL Service Stopped

If it is running, try to restart it.

  • If it was stopped, try to start it.
  • If it was failed to start >  Right Click on it > Properties > below Log on try to retype the username and password then confirm it > Click Start.
Reset SQL Server Account
  • It should be now started properly.
SQL service Started

The App Pool account for web application is locked or disabled.

  • Open IIS.
  • Check Identity for the web application App Pool.
  • Make sure that this account is not locked or disabled.
the user is disabled in AD

Farm account issue

Ask your system administrator to make sure that

  • The farm account
    • Not Locked or disabled.
    • The password is never expired.
  • The farm account have the below security policy rights:
    • Allow Logon locally.
    • Logon as Service.
Allow log on locally - log on as a service

Farm account Permissions

Make sure that the farm account has the below Server roles permissions on the SQL Server instance:

  • Dbcreator.
  • Security Admin.
  • DbOwner on the content database.
  • No changes on the default permissions on SharePoint config database.

Check SharePoint Config Database Status

Make sure that the SharePoint Configuration database is

  • Not in recovery mode
  • its status is online.

Check SharePoint Servers within the farm

Make sure that all SharePoint servers within the farm are joined properly and working healthy!

If there is a server is not listed in the above list and should be a part of the farm, try to run the configuration wizard to join it.


Conclusion

In this article, I have explained the root cause of this issue “This operation can be performed only on a computer that is joined to a server farm by users who have permissions in SQL Server to read from the configuration database

If the above steps don’t helped you, try to run the configuration wizard again on all SharePoint servers cross the farm, to can identify f there are other configuration issue on your farm.

Applies To
  • SharePoint 2016.
  • SharePoint 2013.
  • SharePoint 2010.
See Also
Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s