Article Title: Error: 'The selected database is invalid for this software'
Article Short Description: What to do if Avast Antivirus is preventing you from connecting to the Orchestrate database.
You may see the following error when trying to log into Orchestrate after switching to Avast Antivirus:
⚠️Error: The selected database is invalid for this software.
This error occurs when Avast is running on the server from which the Orchestrate licence is served. Orchestrate may also open very slowly before displaying this error.
Add Avast exclusions for the live system
If you are trying to log into Orchestrate from the live system, add the following file path locations to the Avast management console via file shields exclusions:
C:\Program Files (x86)\X-Formation\LM-X End-user Tools 4.7.5C:\Program Files (x86)\Orchestrate\Orchestrate Planner
📌Note: Adding these exclusions allows Orchestrate to work on the server, but you may still be unable to log in from a client PC. Follow the steps below to resolve this.
Configure Avast firewall settings
Please ask your IT department or third-party IT provider to complete the following steps:
Disable each element of Avast protection in turn and test Orchestrate after each change to identify which component is causing the issue. The problem is specifically caused by the Avast firewall — Orchestrate runs correctly with all other protection elements enabled.
Delete any port and programme exclusions previously added, so you can start afresh.
Change the Avast application rules so that Avast prompts you with a popup when it is unsure whether to allow an application, rather than deciding automatically. The only application detected by Avast in this way will be
orcPlanner.exe. Add this to the exclusions list with All connections enabled.
Required firewall ports
The following ports must be added to both the inbound and outbound firewall rules. These changes must be made by your IT provider and cannot be made by Access Support.
Port | Protocol | Description |
6200 | TCP | Orchestrate application |
86 | UDP | COBOL Service |
1433 | TCP | SQL Service |
1434 | UDP | SQL Browser (only required if multiple SQL instances are used) |
50000–65000 | TCP | Random client ports |
Still having issues?
If the issue continues to occur, or if you are trying to log into Orchestrate from the play system, please raise a new case online and reference the title of this article. A member of our Support team will be happy to help.