Sage Intelligence Reporting: 'Report Execution Error [Microsoft] [ODBC SQL Server Driver] Query timeout expired error

You may observe this error when running a Sage Intelligence Report:

This error is likely caused by a slow network connection and/or a large requested data output on the report.

First, note that you may require the assistance of an IT technician to apply the steps below on the server and workstations.

Consider the following advice to resolve the above error:

A. Report Data Output

Decrease the size of the report data output by narrowing.

For example, if the error was oserved when running the report for 24 months, rerun the report for only 12 months. Keep on narrowing/tweaking the report range until you can run the report.

If the same error is still observed afterwards, apply the advice in the rest of the article.

B. SQL Server Restart required

Restart the SQL Server PC after ensuring all users are logged out of Evolution.

If the same error is still observed afterwards, apply the rest of the advice below.

C. General PC and Network Settings

C1. SQL Services 

1. Ensure the SQL Server Instance and SQL Server Browser services are running on the server machine.

To accomplish this, open the SQL Server PC's Services screen and ensure both services are running. If they’re running, restart both of them after ensuring all users are logged out of all Evolution company

You may find that the SQL Browser Service isn’t running, and it should therefore be started.

If the same error is still observed afterwards, apply the rest of the advice below.

C2. SQL Server Client Network Utility

If the issue is only on the workstations and the SQL server Browser service is running, ensure the below settings are configured on the local workstation: 

• On the Run command/Search field, type Cliconfg and click OK.
• Ensure Named Pipes and TCP/IP are enabled.
• This setting needs to be enabled on the server and all workstations

If the same error is still observed afterwards, apply the rest of the advice below.

C3. SQL Ports on Windows Firewall

The following SQL ports and applications on the Windows Firewall of the SQL Server PC and all workstations should be configured:

• TCP: Port number 1433, for both Inbound and Outbound rules
• UDP: Port number 1434, for both Inbound and Outbound rules
• Add MS SQL Server as an exclusion (or exception) application, by using, for example, the following path C:\Program Files\Microsoft SQL Server\MSSQL18.SQLEXPRESS\MSSQL\Binn\sqlservr.exe

If the same error is still observed afterwards, apply the rest of the advice below.

C4. Location of Company database on workstation 

On the relevant workstation with the error, locate the database using np:

For example, use this string on the Server field where the SQL server instance name is SERVER\SQLEXPRESS:

np:SERVER\SQLEXPRESS