Product DocsMenu

Troubleshooting and Handling Usage Analytics Module Errors

  • When CES and Microsoft SQL run on different servers, ensure that the firewall of the Microsoft SQL Server allows communication from the Coveo server (typically on port 1433).

  • Verify that the Microsoft SQL Server identified in the Web.config file exists, is running, and that the user that runs the Coveo website in IIS on the Coveo Front-End servers has the read and write permissions to the database (see Deploying the On-Premises Usage Analytics Module).

  • Most Usage Analytics module errors are linked to problems with the connection to the Microsoft SQL Server. In the Web.config file, make appropriate changes to the connectionString parameter (refer to the following website for details: http://www.connectionstrings.com/sql-server-2008).

  • In Sql Server Configuration Manager, ensure that the protocol used by CES to communicate with the SQL database is activated (see the example for Microsoft SQL 2008 in the following figure).

Usage Analytics error messages

By default, the Usage Analytics module displays errors below the search box in the Coveo .NET search interface. These Usage Analytics module errors only appear for a Coveo administrator, not for end-users.

Note: You can configure the Usage Analytics module to log errors (see Logging Usage Analytics Module Errors).

You may encounter the following Usage Analytics module errors:

  • Analytics Error: A network-related or instance-specific error occurred while establishing a connection to 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

People who viewed this topic also viewed