You are viewing limited content. For full access, please sign in.

Question

Question

DCC License Validation Erro

asked on December 20, 2018

I have had this at a few clients now quite a few times:

 

The operation could not have been completed because the Laserfiche Distributed Computing Cluster Service is not licensed. License error: "Validation Error code: "ConnectionFailed"".

 

It may be after a reboot but I have seen it a few other times as well.  In both cases they are on the Laserfiche server as well and this is the only product out of everything that deactivates.  We have to generate a new one and swap it out.

Is there something special about the DCC compared to all other products?

0 0

Replies

replied on April 22, 2019

I have the exact same issue with DCC. 

 

Have you been able to fix it?

0 0
replied on April 23, 2019

No, the DCC unlicense at random times.  We do not have a lot of clients making use of the product but the ones that do have need to re-license at least once a month.  All other Laserfiche products are fine, it is only the DCC. 

 

0 0
replied on April 23, 2019

Is this in a Rio setup with a DCC license generated from Directory Server (LFDS)?

0 0
replied on April 23, 2019

Subscription actually, but yes the license is in LFDS.  It actually has not happened in a few weeks now which is better.  It used to happen once a week or so.  Essentially you had to delete the license in LFDS, re-generate, copy/paste, bounce the service.

Everything is on one server in this instance and he only error we get in the logs is the below:

There were in errors in starting the Laserfiche Distributed Computing Cluster Service.

License:
Validation Error code: "ConnectionFailed"

Communication:
Starting main service using latest settings, succeeded.
Port: 8107
Security mode: None
Authentication mode: None

Starting meta data service, succeeded.
Port: 8108

Starting module host process callback service succeeded.

Path:
Data directory: C:\ProgramData\Laserfiche\Distributed Computing Cluster
 

0 0
replied on April 23, 2019

Our issue is on a Rio 10.3.1 system, running multiple DCC's on multiple side branches but it only happens on the main server, the side branches are fine.

 

We are also getting the same errors as mentioned above.

0 0
replied on April 24, 2019

Hm, that looks like DCC couldn't contact LFDS on service start to validate its license. Have you tried just restarting the DCC service?

0 0
replied on April 24, 2019

Yeah, we have tried simply restarting the service and it doesn't seem to work.  Also restarting the whole server doesn't resolve it either.  We have to replace the license completely.  Again, hasn't happened for a couple weeks now so we have not looked further.  It has happened 6 or so times since the 1st.

0 0
replied on October 11, 2019

Were there any updates on this issue? We've run into the same issue for RIO 10.4.1 build 350 deployment. Currently, we set LFDS service on a delayed start because of a known issue when Directory Server is installed on same machine as Microsoft SQL. So Directory Server may possibly start up before SQL. We have set DCC on a delayed start as well since the workaround for the previous LFDS issue was to set it to delayed start to allow SQL to start first but the DCC still unlicensed after reboot. In our case, restarting the DCC service manually works.

0 0
replied on October 14, 2019

No updates that I know of.  We still have to restart the DCC server service a couple times a week...

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.