Failed validating license either locally or in the cluster
Thus we want to know if someone has already tried to use the same cluster for SQL Server Entreprise AND Ascent Capture, more details below: Node 1: ----- Ascent Capture Enterprise installed (with server files folder on the SAN) ----- 1 dongle ----- 1 running licensing service ----- 1 running instance of recognition, PDF gen, release ----- SQL Server Enterprise --- Validation service running from time to time and configured to access licensing service on node 2 if node 1 doesn't work Note: The option "store batches in SQL Server" is selected Additional question not related to our case above: 1) I understand why a cluster is needed for SQL but why do we need one for Ascent too?(Ascent's shared files are on a SAN anyway)Our development environment is just like that: MS SQL cluster and Ascent on the same 2 node cluster. I noticed that you put the 2nd dongle within the cluster...They need to have a locally-installed MATLAB client, running on a Linux machine.
For now we will start doing the new instance installation in one of the nodes. On this second part, we passed for all the steps to install the first node of a clustered instance.That's not recommended, since failover upon dongle malfunction will not happen.You should put the second dongle and the backup license server outside the cluster (for example on one of the workstations).I noticed that you put the 2nd dongle within the cluster...When you say "AND Ascent Capture" I assume you mean the Ascent Capture file share?