Equisys technical notes

Technical guidance, explanations and fixes for our products

PRB: DCOM fails to save changes on a NT 4.0 backup domain controller

Print

ZTN2047

ID: ZTN2047

This Zetalink technical note applies to:

  • Zetalink version 1.0 and later

Symptom

Within the Events Log there may be reports of DCOM errors on components hosted on NT 4.0 servers, these events may occur on a different machine but be a result of failure to call remote components on an NT 4.0 BDC.
Running the Zetalink Checker program ("C:\Program Files\Zetalink\ZLcheck.exe") may find failures for components installed on the NT 4.0 backup domain controller (BDC).

Cause

DCOM permissions are not correctly set. Registry changes need to be set that must be replicated to a primary domain controller. When manually configuring theses components via the Windows DCOM configuration program "C:\WINNT\system32\DCOMCNFG.EXE" the following popup warning will occour.

Resolution

To set the DCOM permissions manually work through the following steps.

  1. Check the DCOM configuration with the 'C:\WINNT\system32\DCOMCNFG.EXE' program.
  2. Browse the list to the bottom to find the Zetalink Components and edit the properties according to the following criteria.
    • The Launching user should be set to the Zetalink account created for install (remember to specify the correct password).
    • The Security setting should give access permissions for the Zetalink account to be, interactive, and in the local administrators group, the Launch permissions should match this.

Status

This has been identified by Equisys as a problem with the software versions given above.

Last updated: 23 September 2002 (JG/SV)

Equisys Logo, Document Management and Expense Management for Business Central
 

Recent news

This article describes the new features and other improvements in the March 2021 update of the Zetadocs Expenses service. Zetadocs Expenses Release ...

It may seem strange, in an article extolling the vision of an automated digital future, to start with a reference to 1975, but that was the year Business Week magazine published an article looking ...