This article covers common connectivity, performance and crash issues in ConQuest Q Series. For initial database connection errors on first launch, see Error: 'Could not connect to database' when opening ConQuest. For on-premise performance issues, see Performance Issues with ConQuest On-Premise.
ConQuest is pointing to a local database instead of the shared network database
In a multi-user network installation, all users should connect to the same shared SQL database on the network. If a user's ConQuest is connecting to a local database instead, their work will not be visible to other users and they may see different data to their colleagues.
Identify the current database configuration
Open ConQuest and go to Options, then Databases.
Check the database name and server address shown. If the server is listed as localhost, (local) or the user's own machine name, ConQuest is connecting to a local database rather than the shared server.
Compare the database settings with those of a user who is connecting successfully to the shared database.
Copy database settings from a working user profile
On a machine where ConQuest connects correctly to the shared database, go to Options, then Databases and note the server name, instance name, database name and port.
On the affected machine, go to Options, then Databases.
Update the Server, Instance and Database Name fields to match the working configuration.
Click Test Connection to confirm the connection is successful before saving.
Save the settings and restart ConQuest.
⚠️Important: Do not change database settings unless you are sure of the correct configuration. Pointing ConQuest at the wrong database could mean working on a different copy of your data. If in doubt, contact your system administrator or ConQuest support before making changes.
ConQuest performance is slow
Slow performance in ConQuest is most commonly caused by the Number Options setting, a large Project Registry, server resource issues, or network latency — particularly in remote desktop or VPN environments.
Change the Number Options setting
Go to Options, then Number Options.
In the Project Totals section, set the option to Update only on a refresh.
Press OK and allow ConQuest to restart.
Check whether performance has improved.
Check for performance issues under remote desktop or VPN
When ConQuest is accessed via Remote Desktop (RDP), MyDesk or VPN, network latency can significantly affect performance. Check the following:
Confirm the SQL server and file share are on the same network segment as the ConQuest server, not separated by a slow link.
Ask your IT team to check the antivirus configuration on the server. Antivirus software scanning the ConQuest database files or executable in real time is a common cause of slowness. Add the ConQuest installation folder and SQL data folder to the antivirus exclusion list.
If only a specific project is slow, it may be caused by an oversized project or library. Raise a support ticket referencing the Performance Issues with ConQuest On-Premise article and include a zip of the project and library.
If slowness affects all users on all projects, have your IT team check the SQL Server and file share for disk space and CPU/memory usage.
Project is locked after a crash or unexpected close
If ConQuest crashes or closes unexpectedly while a project is open, the project may remain locked. Other users will be unable to open it until the lock is cleared.
Ask the user whose session caused the crash to log back in to ConQuest and attempt to open the locked project — ConQuest may automatically offer to clear the lock on login.
If the lock persists, go to Options, then Project Registry.
Locate the locked project. The lock icon indicates it is currently open or flagged as in use.
Right-click the project and select Clear Lock, or the equivalent option for your version.
If the Clear Lock option is not available, ask your system administrator to clear the lock directly in the ConQuest SQL database. This requires access to the database and should not be attempted without SQL knowledge.
📌Note: If the same user is shown as the lock holder but is no longer in ConQuest, the lock is stale and safe to clear. If another user is shown as the lock holder and is actively working in the project, do not clear the lock — contact that user first.
RabbitMQ service is not running (On-Screen TakeOff)
RabbitMQ is required for communication between ConQuest and On-Screen TakeOff. If the RabbitMQ service has stopped, TakeOff will not function and you may see connection errors when launching it.
Check and restart the RabbitMQ service
On the server where RabbitMQ is installed, open Services (press Windows + R, type services.msc and press Enter).
Locate the RabbitMQ service in the list.
If the service status is Stopped, right-click it and select Start.
Wait for the service to start, then retry opening On-Screen TakeOff.
If the service fails to start, check the Windows Event Log for error details. Common causes include insufficient server memory or a conflict with the Erlang runtime.
Confirm the firewall allows RabbitMQ traffic
Port 5672 must be open through the Windows Firewall for users to connect to the RabbitMQ service. If the service is running but TakeOff still cannot connect, ask your IT team to confirm port 5672 is open. See Which ports need to be open? for the full list of required ports for ConQuest.
📌Note: If RabbitMQ is not yet installed, see Installation of RabbitMQ integration for the full installation steps.
Raise a support ticket
Raise a support ticket if:
ConQuest cannot connect to the database after confirming the correct server and database name.
A project lock cannot be cleared using the steps above.
The RabbitMQ service fails to start after a restart attempt.
Performance issues persist after applying the Number Options change and checking server resources.
For project-specific performance issues, include a zip of the project and library when raising your ticket; reference the title of this article in your ticket subject.