FIX: Event 825 error messages are logged to the event log when you specify different user credentials for multiple HIP application service instances in Host Integration Server 2004 (906666)
The information in this article applies to:
- Microsoft Host Integration Server 2004
SYMPTOMSConsider 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.
CAUSEThis 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. RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Host Integration Server 2004 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
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. WORKAROUNDTo 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.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/25/2006 |
---|
Keywords: | kbQFE kbHIS2004 kbfix kbbug kbpubtypekc KB906666 kbAudDeveloper kbAudITPRO |
---|
|