Article ID: 921207 - Last Review: January 24, 2008 - Revision: 2.2 FIX: The PSXRUN process may not stop when you try to stop a POSIX-based application that is running as a Windows service in Windows
On This PageSYMPTOMSIn Microsoft Windows Services for UNIX 3.5 or in a Subsystem for UNIX-based Applications (SUA) environment, you try to stop a Portable Operating System Interface (POSIX)-based application that is running as a Windows service. When you do this, the PSXRUN process may not stop. Additionally, the PSXRUN process may continue to show the STOPPING status. This problem occurs when the following conditions are true:
CAUSEThis problem occurs because there are two threads in the PSXRUN process that call the SetServiceStatus function, and the two threads are not synchronized. One of the threads should always call the SetServiceStatus function before the second thread calls the SetServiceStatus function. RESOLUTIONHotfix informationA supported hotfix is 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.If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesTo apply this hotfix, you must be running Windows Services for UNIX 3.5 or Subsystem for UNIX-based Applications.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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 item in Control Panel.Collapse this table
Windows Server 2003 R2 Service Pack 1, 32-bit systemCollapse this table
Windows Server 2003 R2 Service Pack 2, 32-bit systemCollapse this table
Windows Server 2003 R2 Service Pack 1, 64-bit systemCollapse this table
Windows Server 2003 R2 Service Pack 2, 64-bit systemCollapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
| Article Translations
|

Back to the top
