How to troubleshoot DCOM in Cloudhouse Compatibility Containers

Save to PDF

Applies to: Compatibility Containers

06/06/2019 Cliff Hobbs   ID: 383006

Purpose

The purpose of this article is to provide troubleshooting-related information for DCOM when implemented in Cloudhouse Compatibility Containers™.

Note

See DCOM support in Cloudhouse Compatibility Containers for background information on DCOM and the scenarios supported by Cloudhouse Containers, and How to Configure DCOM for Cloudhouse Compatibility Containers for details of how to configure and test DCOM in Cloudhouse Containers.

Troubleshooting Tips

By its nature, DCOM is distributed and therefore potentially more prone to problems compared to running applications within the same Container.

If you are encountering issues with DCOM, verify:

  • DCOM is configured as detailed in How to Configure DCOM for Cloudhouse Compatibility Containers.
  • The containerised implementation of the DCOM application matches the implementation it has replaced (if relevant).
  • Network connectivity on both the computer hosting the Container running the DCOM server component and the computer hosting the Container running the DCOM client component.
  • Both computers can communicate with one another. You can use telnet <remote_server_name> 135 (where <remote_server_name> is the name of the remote server), to verify connectivity.
  • Port 135 is open on the firewalls on both computers.
  • Both computers are part of the same domain/workgroup.

Also, use Event Viewer to review the Windows Logs for any potential DCOM-related errors.

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support