Article ID: 906666
Article Last Modified on 12/4/2007
APPLIES TO
- Microsoft Host Integration Server 2004 Standard Edition
SYMPTOMS
Consider the following scenario. In Microsoft Host Integration Server 2004, you use Transaction Integrator (TI), and you configure multiple host-initiated processing (HIP) applications. You specify different user credentials for each HIP application service (HIPService). In this scenario, events that are similar to the following are logged to the event log:
Event ID: 825
Source: HIP Service
Type: Information
Description: (825) Transaction Integrator failed when attempting to create a timer to monitor for adjusting the runtime characteristics. HIP Application: Application Name
EXPLANATION
Transaction Integrator Service, for the HIP Application listed above, issued a CreateWaitableTimer call and the call failed. The HIP Application will continue processing but dynamic runtime tuning will be disabled.
ACTION
Make sure that the Transaction Integrator service has been properly deployed and administered and that the HIP runtime environment has been installed on the system on which the failure occurred. If the problem persists contact Microsoft support.
CAUSE
This problem occurs because each HIPService instance tries to create a named waitable timer object when the service starts. The waitable timer object is created by using the default security descriptor. This security descriptor is obtained from the user credentials of the HIPService instance. Other HIPService instances that use different user credentials cannot create another instance of the waitable timer object because the same waitable timer object name is specified.
RESOLUTION
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
The English version of this hotfix has the file attributes (or later file attributes) 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 ------------------------------------------------------ 24-Aug-2005 05:49 6.0.1979.0 46,592 Hipservice.exe
Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.
WORKAROUND
To work around this problem, configure each HIPService instance to use the same user credentials when you configure the HIP applications in TI Manager. You can also modify the user credentials for the HIPService instances in the Services MMC snap-in.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbhis2004 KB906666
