Event ID 2032 — Psxrun Availability

Event ID 2032 — Psxrun Availability

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2032
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: PSXRUN_SUA_RUN_IN_SAFE_MODE
Message: (PSXRUN) This functionality in not available in Safe Mode.

Resolve
Restart the computer normally (not in Safe Mode)

Subsystem for UNIX-based Applications (SUA) cannot operate when your Windows operating system is running in Safe Mode. Restart Windows in normal operating mode to run SUA.

To restart the computer:

  • Click Start, click the arrow next to the Lock button, and then click Restart.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2028 — Psxrun Availability

Event ID 2028 — Psxrun Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2028
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: PSXRUN_FATALITY
Message: A fatal error occurred in psxrun: %1

Resolve
Review error details in Event Viewer to help recover from this error

An internal error occurred during psxrun startup. Psxrun attempted to call a Windows API that returned an unexpected failure.

Open the error message in Event Viewer to determine the API call that failed. Failures typically occur during calls to any of the following APIs:

  • CreateEvent ()
  • SetServiceStatus ()
  • WaitForMultipleObjects
  • Calls to an internal WINNT kernel

The error state may be transient. Try restarting the original POSIX application that resulted in this failure. If this fails, restart the computer. If that fails to solve the problem, it is recommended you troubleshoot calls from your POSIX application to the Windows API.

To restart the computer:

  • Click Start, click the arrow next to the Lock button, and then click Restart.

For more information about troubleshooting calls to the Windows API, see “Adjusting Calls to API Functions” on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=95088). Other articles in the Microsoft MSDN database might also be useful.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2027 — Psxrun Availability

Event ID 2027 — Psxrun Availability

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2027
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: CTRL_DISPATCHER_FAILED
Message: StartServiceCntlDispatcher failed for a service

Resolve
Correct SCM error

The POSIX application referenced in the Event Viewer message text was running as a Windows service, but a Service Control Manager (SCM) call to StartServiceCtrlDispatcher failed. For more information about debugging a service in Windows, refer to the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=95087).

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2026 — Psxrun Availability

Event ID 2026 — Psxrun Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2026
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: NOT_ABS_PATH
Message: Program name %1 is not an absolute UNIX path name.

Resolve
Check path name

Verify the path name for the Subsystem for UNIX-based Applications application. Psxrun closed because it could not find the application by using the provided path name.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2025 — Psxrun Availability

Event ID 2025 — Psxrun Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2025
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: GFPN_FAILED
Message: GetFullPathName failed for “%1”: %2

Resolve
Check CurrentDirectory path length

Psxrun attempted to obtain CurrentDirectory information during initialization, but the character length of the path returned for the current directory was greater than the maximum character length allowed in the environment variable PATH_MAX. To solve this problem, run psxrun from another directory that has a path length of fewer characters than the maximum allowed.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2022 — Psxrun Availability

Event ID 2022 — Psxrun Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2022
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: NO_INTERIX_CWD
Message: Unable to find the current working directory for Subsystem for UNIX-based Applications %1

Resolve
Check CurrentDirectory path length

Psxrun attempted to obtain CurrentDirectory information during initialization, but the character length of the path returned for the current directory was greater than the maximum character length allowed in the environment variable PATH_MAX. To solve this problem, run psxrun from another directory that has a path length of fewer characters than the maximum allowed.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2021 — Psxrun Availability

Event ID 2021 — Psxrun Availability

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2021
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: NO_ANSI_CWD
Message: Unable to find 8-bit current working directory.

Resolve
Check documentation and correct failure of GetCurrentDirectoryA API

During initilization of Psxrun, a call to GetCurrentDirectoryA() (ANSI version of GetCurrentDirectory) failed, either by returning NULL, or by returning a current directory that has a path character length greater than that allowed in the environment variable PATH_MAX.

For more information about requirements for calling the GetCurrentDirectoryA() API, see the “GetCurrentDirectory” topic on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=95089). Other articles in the Microsoft MSDN online database might also be useful.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2020 — Psxrun Availability

Event ID 2020 — Psxrun Availability

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2020
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: NO_CWD
Message: Unable to find current working directory.

Resolve
Check documentation and correct failure of GetCurrentDirectoryW API

During initialization of Psxrun, a call to GetCurrentDirectoryW() (the Unicode version of GetCurrentDirectory) failed, either by returning NULL, or by returning a current directory that has a path character length greater than that allowed in the environment variable PATH_MAX.

For more information about requirements for calling the GetCurrentDirectoryW() API, see the “GetCurrentDirectory” topic on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=95089). Other articles in the Microsoft MSDN online database might also be useful.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2019 — Psxrun Availability

Event ID 2019 — Psxrun Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2019
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: BAD_PATHNAME
Message: Unusable %1 path name “%2”

Resolve
Check path name

Verify the path name for the Subsystem for UNIX-based Applications application. Psxrun closed because it could not find the application by using the provided path name.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related:

Event ID 2018 — Psxrun Availability

Event ID 2018 — Psxrun Availability

Updated: November 14, 2007

Applies To: Windows Server 2008

Subsystem for UNIX-based Applications (SUA) Psxrun Availability indicates the ability of the Psxrun utility to start and run SUA processes.

Problems that can occur with Psxrun Availability include API call failures, incorrect path names or command line parameters, and low virtual memory.

Event Details

Product: Windows Subsystem for UNIX-based Applications
ID: 2018
Source: Microsoft-Windows-SUA-Psxrun
Version: 6.0
Symbolic Name: ERR_NO_MEMORY
Message: Out of Memory

Resolve
Free some memory

An error occurred during memory allocation. This can happen if the Windows server is running low on virtual memory. Try closing some applications that are not required and are using virtual memory, and then try running the Subsystem for UNIX-based Applications application again. If this does not correct the problem, try restarting the computer to clear the error.

Verify

Because multiple instances of Psxrun can be running at once, it is best to verify Psxrun in Windows Task Manager not by checking on a particular instance of Psxrun, but by verifying that the specific POSIX process or application launched by using Psxrun is running.

To verify that Psxrun is running:

  1. Open Windows Task Manager by pressing CTRL+ALT+DEL, and then clicking Start Task Manager.
  2. On the Processes tab, select the Show processes from all users check box.
  3. Verify that a specific POSIX process you have started by using Subsystem for UNIX-based Applications is running.

If the POSIX application or process that has been launched by using Psxrun is indicated as running in Task Manager, then Psxrun is fully available. If the process is not running, critical errors are preventing Psxrun from being available.

Related Management Information

Psxrun Availability

Subsystem for UNIX-based Applications

Related: