There is a problem accessing the SQL server

Scenario

A network-related or instance-specific error occurred while establishing a connection to the SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.)
An error has occurred while establishing a connection to the server. When connecting to SQL Server 20xx, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
SQL Server service has been paused. No new connections will be allowed. To resume the service, use the SQL Computer Manager or the Services application in Control Panel. Login failed for user 'CreativeSolutionsPracticeCsDatabaseOwner'.
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
Practice CS firms with Remote Entry enabled:
Practice CS was able to connect to your database server, but could not find an available Practice CS database to connect to. You will not be able to access Practice CS until a Practice CS database is available.
Practice CS firms with Remote Entry enabled:
Only the remote database will be available to open.

Cause

Solution 1: The SQL Server browser service isn't running

At the workstation where the SQL Server instance is installed, select
Start > Run
, enter
services.msc
in the
Open
field, and then select
OK
.
In the list of services, double-click
SQL Server Browser
.
Verify that the
Startup type
is
Automatic
and that the
Service Status
is
Started
.
If the SQL Browser is not started, then select the
Start
link to start the service, and then select
OK
.
In the list of services, double-click
SQL Server (<insert server name>)
and repeat steps 3 and 4 for the SQL Server service.

Solution 2: TCP/IP Connections are not enabled for SQL Server

At the workstation where the SQL Server instance is installed, open the
SQL Server Configuration Manager
.
For Windows 10, and Server 2012:
Open the
Search
from the Start menu, the Charms bar, or from the
Run
window, and then enter the following, depending on the version of SQL Server that you have installed.
SQL 2014: SQLServerManager12.msc
SQL 2016: SQLServerManager13.msc
SQL 2017: SQLServerManager14.msc
SQL 2019: SQLServerManager15.msc
Select
SQL Server 20xx Network Configuration / Protocols for <InstanceName>
.
Make sure that TCP/IP is enabled. If the status is disabled, right-click and select
Enable
.

Solution 3: Named Pipes are not enabled for SQL Server

At the workstation where the SQL Server instance is installed, open the
SQL Server Configuration Manager
.
For Windows 10, and Server 2012:
Open the
Search
from the Start menu, the Charms bar, or from the
Run
window, and then enter the following, depending on the version of SQL Server that you have installed.
SQL 2014: SQLServerManager12.msc
SQL 2016: SQLServerManager13.msc
SQL 2017: SQLServerManager14.msc
SQL 2019: SQLServerManager15.msc
Select
SQL Server 20xx Network Configuration / Protocols for <InstanceName>
.
Make sure that Named Pipes is enabled. If the status is disabled, right-click and select
Enable
.
Select
SQL Native Client Configuration / Client Protocols
.
Make sure that Named Pipes is enabled. If the status is disabled, right-click and select
Enable
.
Stop and restart the SQL Instance and the SQL Browser in either in the SQL Server Services section of the Configuration manager or in Services.msc under the name SQL Server <InstanceName>.

Solution 4: The database server machine is running a firewall

Solution 5: Restart the SQL Server instance

Solution 6: Use the IP address instead of the machine name

Select
Start > Run
, enter
cmd
in the
Open
field, and then select
OK
.
In command prompt, enter
ping <MACHINENAME>
(or
ping <MACHINENAME> -4
for the IPV4 address).
The network response should be the following line of text:
Pinging MACHINENAME [xxx.xxx.xxx.xxx] with 32 bytes of data
(where xxx.xxx.xxx.xxx represents the valid IP address for MACHINENAME).

Solution 7: Trend Micro-Worry Free Business Security was installed after the application

Choose 
Start > Control Panel
and select
Programs and Features
to uninstall the <application name> Shared Files, and the actual application, if it was installed on the server in Step 3 of the installation procedure.
Restart the installation process while present at the SQL server, and then select the option to
Install a new instance of Microsoft SQL Server Express Edition
.
When prompted, select a new instance name.
Uninstall and reinstall the desktop setup process on all workstations.
Restore the database to the new SQL instance using a backup previously created in the application, or via another application such as Microsoft SQL Server Management Studio.

Solution 8: A third-party application is interfering with database connectivity

Restart the workstation in
Safe Mode with Networking
and retest to see if this issue recurs in this state.
If the application opens without any issues, disable all non-Microsoft services, and then start items using
MSCONFIG.EXE
.
Enable a small number of items at a time, and then retest until the specific item that is causing the interference is identified.
Disable and/or uninstall the application, service, or startup item that is causing the issue.

Solution 9: The SQL instance is misconfigured

Open Microsoft SQL Server Management Studio on the SQL server and connect to your instance.
Right-click on the instance name and select
Properties
.
Select
Security
and make sure that the
SQL Server and Windows Authentication Mode
checkbox is marked.
Close out of any open windows.
Open the
Security
folder and then the
Logins
folder and make sure that the CreativeSolutionsPracticeCSDatabaseOwner is listed (regardless of which application you're using).
If CreativeSolutionsPracticeCSDatabaseOwner is not listed, reinstall the application on the server. During step 2 of the installation, select your existing instance of SQL to create the login.

Solution 10: Disable Microsoft data compression and encryption for SQL files

the ACS_0_FIRM.mdf and ACS_0_FIRM.ldf (for Accounting CS and Workpapers CS)
the CSP_<FIRMID>_<FIRM>.mdf and CSP_<FIRMID>_<FIRM>_log.ldf (for Practice CS)
the fcs_fcabdatadb.mdf, fcsd_fcabdatadb.mdf, fcs_fcabdatadb_log.LDF, and fcsd_fcabdatadb_log.LDF (for FileCabinet CS)

Right-click the
Program Files
or
Program Files (x86)
folder on the server, and select
Properties
.
On the General tab, select the
Advanced
button and clear the options to
Compress contents to save disk space
and
Encrypt contents to secure data
.

Solution 11: Test SQL connectivity outside of the CS Professional Suite

At the workstation, select 
Start > Control Panel
.
Select
Administrative Tools
, and then
Data Sources (ODBC)
Select
Add
.
Select
SQL Server
, and then select
Finish
.
Enter a
Name
and
Description
(anything will do), and then enter the
Server\Instance
name of the SQL instance used by the application (for example, ServerName\CREATIVESOLUTION).
Select
Next
through the remaining screens in the Setup wizard, and then select
Finish
.
Select
Test Data Source
. If the connection to the SQL server is successful, you are prompted with a message.
Close all the open screens and close Administrative Tools.