Transactional logs may not be exchanged between CICS, IMS, DB2, and Windows COM+ in transactional mode when the Host Integration Server 2004 LU62 Resync service is manually stopped and then restarted (884388)
The information in this article applies to:
- Microsoft Host Integration Server 2004
SYMPTOMSThe Microsoft Host Integration Server 2004 HIS LU62 Resync service resynchronizes transactions that span Microsoft Windows and IBM systems such as Customer Information Control System (CICS), IMS, and DB2. The Resync service works with Host Integration Server SNA LU6.2 network connections. If the Resync service is manually stopped and then started, transactional logs may not be exchanged between CICS, IMS, DB2, and Microsoft Windows COM+ in transactional mode and you may receive the following event message:
Event Type: Error
Event Source: SNA LU6.2 Resync TP
Event Category: SNA LU6.2
Event ID: 131
Date: 7/30/2004
Time: 3:09:10 PM
User: ComputerName\ SNAServiceAccount
Computer: ComputerNameDescription:
(131) The Resynchronization Service was unable to initialize
interfaces to the WMI Provider.
EXPLANATION
The Resynchronization Service encountered HRESULT
80041004 when trying to obtain SNA configuration information
from the Host Integration Server WMI namespace. The
service is unable to initialize its environment and prepare
for transactions. This may indicate that the primary SNA
configuration server or other SNA server service has become
inactive or unreachable on the network, or that the Host
Integration Server was not installed properly.
ACTION
Contact system administrator.
Verify that the SNA servers in the subdomain are active.
Then use the service control manager to start the
Resynchronization Service, if it is not active.
If this does not resolve the problem, contact
Microsoft support.
For more information, see Help and Support Center at http://support.microsoft.com. CAUSEThis problem may occur when you manually shut down and restart the HIS LU62 Resync service by using the Service Control Manager.RESOLUTIONTo resolve this problem, do not manually shut down the HIS LU62 Resync service.WORKAROUNDTo work around this problem, perform a normal shutdown of the computer. Then, restart the computer to make the HIS LU62 Resync service exchange logs again.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 9/22/2006 |
---|
Keywords: | kbinfo kbprb KB884388 kbAudDeveloper |
---|
|