FIX: The SNA LU6.2 Resync TP service incorrectly logs event 134 errors for orphaned Remote APPC LUs (838411)


The information in this article applies to:

  • Microsoft Host Integration Server 2000
  • Microsoft Host Integration Server 2000 SP1

SYMPTOMS

The SNA LU6.2 Resync TP service may incorrectly log event 134 errors in the application event log. The service may log these events while the service checks for orphaned Remote APPC LUs in the Microsoft Host Integration Server 2000 configuration.

For a definition of an orphaned Remote APPC LU, see the "More Information" section.

CAUSE

This problem occurs when there are multiple Local LUs in the subdomain that are configured for different Resync clients. This behavior causes the SNA LU6.2 Resync TP service to use an incomplete list of SyncPoint enabled Local APPC LUs. This behavior causes incorrect logging of event 134 errors for Remote APPC LUs that are not orphaned in the Host Integration Server 2000 configuration.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Host Integration Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

328152 How to obtain the latest service pack for Host Integration Server 2000

Hotfix information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version      Size    File name
   -------------------------------------------------------
   13-Mar-2004  00:50  5.0.0.970   127,248  Resyncsvc.exe
Note Because of file dependencies, the most recent fix that contains the previous files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article. This problem was corrected in Microsoft Host Integration Server 2000 Service Pack 2.

MORE INFORMATION

The SNA LU6.2 Resync TP service retrieves a list of all the Local APPC LUs and all the Remote APPC LUs that are configured to support SyncPoint services. The SNA LU6.2 Resync TP service also checks the Host Integration Server 2000 configuration to determine whether any one or more of the SyncPoint enabled Remote APPC LUs are orphaned.

Orphaned Remote APPC LU - An orphaned Remote APPC LU is a Remote APPC LU that has been SyncPoint enabled and that has been created on an SNA Server service (Snaservr.exe) that does not have any Local APPC LUs that are SyncPoint enabled. The SyncPoint enabled Remote APPC LU is orphaned because no SyncPoint enabled Local APPC LU to be partnered with exists on the same SNA Server service.

The SNA LU6.2 Resync TP logs the following event 134 error if an orphaned Remote APPC LU is detected:
Event ID: 134
Source: SNA LU6.2 Resync TP
Description: (134) The Resynchronization Service encountered a Remote LU with no SyncPoint-capable partners.
Explanation: The Resynchronization Service found Remote LU Remote APPC LU Name on SNA Service SNA Service Name. The SyncPoint property was enabled, but no Local LUs with the SyncPoint property and LU 6.2 Resync Service Computer field equal to Client Computer Name were found on the SNA Server service.

Example scenario

The following is an example configuration that results in the SNA LU6.2 Resync TP service logging an incorrect event 134 error.
ServerLocal APPC LU (Resync Client)Remote APPC LU
HISSERVER1LOCAL1 (CLIENT1)REMOTE1
HISSERVER2LOCAL2 (CLIENT2)REMOTE2

In this configuration, all the APPC LUs are configured to support SyncPoint services:
  • Local APPC LU LOCAL1 is configured to work with the SNA LU6.2 Resync TP service running on CLIENT1.
  • Local APPC LU LOCAL2 is configured to work with the SNA LU6.2 Resync TP service running on CLIENT2.
The following sequence of events occurs in this example scenario:
  1. When the SNA LU6.2 Resync TP on CLIENT1 starts, it retrieves a list of the APPC LUs and determines the APPC LUs that are enabled to support SyncPoint services.
  2. The SNA LU6.2 Resync TP service on CLIENT1 keeps an internal list of all the Local APPC LUs that support SyncPoint services and that are configured with a computer name of CLIENT1.
  3. The SNA LU6.2 Resync TP service on CLIENT1 determines that REMOTE1 and REMOTE2 are enabled to support SyncPoint services.
  4. The service checks to determine whether either REMOTE1 or REMOTE2 are orphaned.
  5. Because the Local APPC LU list that the SNA LU6.2 Resync TP service has contains only LOCAL1, the service incorrectly determines that REMOTE2 is an orphaned Remote APPC LU because the Local APPC LU list does not contain LOCAL2.
Modification Type:MinorLast Reviewed:6/5/2006
Keywords:kbHotfixServer kbQFE kbfix kbbug KB838411 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.