Export (0) Print
Expand All

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.

Events

Event ID Source Message

2002

Microsoft-Windows-SUA-Psxrun

psxrun: unknown flag %1. Enter -h in a command shell for the complete Help message.

2004

Microsoft-Windows-SUA-Psxrun

The psxrun command might have failed due to improper usage or syntax. Verify in the Subsystem for UNIX-based Applications Help that psxrun has been entered using proper syntax and command arguments. Example: psxrun [-h] [-l logfile] [-p program] [-u] [--] arguments

2005

Microsoft-Windows-SUA-Psxrun

Usage: psxrun [-h] [-l logfile] [-p program] [-u] [--] arguments Verify in the Subsystem for UNIX-based Applications Help that psxrun has been entered using proper syntax and command arguments.

2007

Microsoft-Windows-SUA-Psxrun

psxrun: command missing

2008

Microsoft-Windows-SUA-Psxrun

Unable to connect to Subsystem for UNIX-based Applications.

2009

Microsoft-Windows-SUA-Psxrun

Unable to start process %1

2010

Microsoft-Windows-SUA-Psxrun

Not enough memory to create new tty.

2011

Microsoft-Windows-SUA-Psxrun

Cannot connect to the tty session. The error status code was %1.

2012

Microsoft-Windows-SUA-Psxrun

There are too many terminal sessions open. Subsystem for UNIX-based Applications is unable to open additional terminal sessions.

2013

Microsoft-Windows-SUA-Psxrun

There was an error connecting to the subsystem. The error status code was %1 while trying to launch program %2.

2014

Microsoft-Windows-SUA-Psxrun

WclCall: lpc failure: %1

2015

Microsoft-Windows-SUA-Psxrun

WclCall: unexpected MSG_TYPE %1

2016

Microsoft-Windows-SUA-Psxrun

GetUid failed: error %1

2017

Microsoft-Windows-SUA-Psxrun

GetPwUid(%1) failed: error %2

2018

Microsoft-Windows-SUA-Psxrun

Out of Memory

2019

Microsoft-Windows-SUA-Psxrun

Unusable %1 path name "%2"

2020

Microsoft-Windows-SUA-Psxrun

Unable to find current working directory.

2021

Microsoft-Windows-SUA-Psxrun

Unable to find 8-bit current working directory.

2022

Microsoft-Windows-SUA-Psxrun

Unable to find the current working directory for Subsystem for UNIX-based Applications %1

2025

Microsoft-Windows-SUA-Psxrun

GetFullPathName failed for "%1": %2

2026

Microsoft-Windows-SUA-Psxrun

Program name %1 is not an absolute UNIX path name.

2027

Microsoft-Windows-SUA-Psxrun

StartServiceCntlDispatcher failed for a service

2028

Microsoft-Windows-SUA-Psxrun

A fatal error occurred in psxrun: %1

2032

Microsoft-Windows-SUA-Psxrun

(PSXRUN) This functionality in not available in Safe Mode.

Related Management Information

Subsystem for UNIX-based Applications -- Psxrun utility

Subsystem for UNIX-based Applications

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft