When changing to Avast Antivirus there have been some problems connecting to the Orchestrate database. The error says:-
The selected database is invalid for this software
When Avast is running on the server from which the Orchestrate licence is running, Orchestrate opens very slowly and then comes up with an error when trying to log on. If I turn off Avast completely, Orchestrate opens quickly and then logs on fine with the same settings on the local machine.
We tried opening TCP port 6200, putting the Orchestrate file directory and server directory into the exclusions list in Avast, but the only way to use Orchestrate is by disabling Avast completely on the server.
If you are trying to log into Orchestrate from the live system, add file path locations for X formation (where the Orchestrate licence is kept) and Orchestrate to Avast management console via file shields, exclusions, Orchestrate now works on the server but you cannot log into Orchestrate from the client PC.
C:\Program Files (x86)\X-Formation\LM-X End-user Tools 4.7.5
C:\Program Files (x86)\Orchestrate\Orchestrate Planner
Please ask your IT department or third party IT to complete the following steps:-
Disable each element of the Avast protection in turn and tried running Orchestrate after each. We narrowed the problem down to be specifically the firewall only (it ran perfectly with everything else on).
Delete the port and the programme exclusions you previously added, so you can start afresh.
Change the application rules, so that Avast would ask you with a popup if you ran something and it was unsure if it should be allowed, rather than just auto deciding. The only application to be detected by Avast in this way was orcPlanner.exe. Add this to the exclusions list with 'all connections' enabled.
With the port not added but the application in the exclusions list, Orchestrate now opens quicker but won't log in because of licence server error.
The following ports are required in the inbound and outbound firewall rules. These changes cannot be made by Access Support and must be done by your I.T. provider.
PORT | PROTOCOL | DESCRIPTION |
6200 | TCP | Orchestrate application |
86 | UDP | COBOL Service |
1433 | TCP | SQL Service |
1434 | UDP | SQL Browser (Only if multiple SQL instances are used) |
50000 - 65000 | TCP | Random Client Ports |
If the issue continues to occur or you are trying to log into Orchestrate from the play system, please raise a new case online referencing the title of this article and a member of our support team will be able to help you further.