Question

DCOM was unable to communicate with the computer x.x.x.x

Forms Version 10

Updated April 13, 2020

asked on June 20, 2017

Hello,

I am seeing a problem where when we try and sync users in LF Forms, the over process works, but the synchronization button just keeps on spinning.

In Event Viewer, I am seeing the following error:

DCOM was unable to communicate with the computer x.x.x.x using any of the configured protocols; requested by PID 2574 (C:\Program Files\Laserfiche\Laserfiche Forms\Forms\bin\RoutingEngineServiceHost.exe).

The interesting part is that the IP address that is showing up in the x.x.x.x part of the error is from the old LF server that is no longer used.

Forms Config is pointed to the correct LF server at this point.

Has anyone seen this error before?

0 0

Replies

replied on June 28, 2017

Hi Charles,

I never saw such kind of issue. Routing service reads lf server from database, so if it's connecting to wrong lf server, can you double check the database setting in routing service config file is correct, and double check the [cf_lfdb] table in the database contains correct lf_server?

Also can you try configuring lf server with ip address instead of server name on FormsConfig page?

0 0

replied on July 27, 2017 • Show version history

We are also receiving a similar error. We had an old Laserfiche server which was used for testing. The server is turned offline, but we are getting a constant DistributedCOM error in the System logs. I don't know if it is the same issue as above. See screenshot below.

0 0

replied on July 27, 2017

Hi Zach,

Since the old LF server is offline, your Forms server is now using new LF server right? Have you tried restart routing service after changing LF server?

0 0

replied on August 1, 2017

Hi Rui,

The old Laserfiche test server did not have Forms installed. Forms is currently installed on a different production web server. We can restart the Forms routing service on the production web server if you are confident it may still have an impact on our production Laserfiche server.

Thank You

0 0

replied on August 1, 2017

I meant the Laserfiche server used on Forms server, not where the Forms is installed.

Can you check the Forms config site and see if the repository is still using the old LF server? If so, routing service would try to connect to the old server and that would cause trouble.

0 0

replied on March 22, 2018

I have the exact same error message happening after moving Laserfiche from one server to another. Nothing seems to be broken but that message is showing up in my event viewer and I have checked that DB table and the name is the updated server. I have also tried the IP address in the config page and it does not stop that message from appearing.

0 0

replied on April 13, 2020

Did any of you find a concrete resolution to this?

I have a customer hitting the same errors on a new LF Server with just QF installed and the errors are pointing to the old QF Server that is decommed.

Applications installed include the Laserfiche Quick Fields and Quick Fields Agent Administrator and Quickfields Server (which we are not using at this time)

Appreciate your time,

Jeff Curtis

0 0

You are not allowed to follow up in this post.

Question

Question

DCOM was unable to communicate with the computer x.x.x.x

Replies

Sign in to reply to this post.