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 2022 — Shared Folders (SMB) Server Configuration

Event ID 2022 — Shared Folders (SMB) Server Configuration

Updated: January 27, 2011

Applies To: Windows Server 2008 R2

The Server Message Block (SMB) protocol is what Windows uses to share files, printers, serial ports, and communicate this information between computers. The service must be configured correctly for the server to properly manage shared resources.

Event Details

Product: Windows Operating System
ID: 2022
Source: Server
Version: 6.1
Symbolic Name: EVENT_SRV_NO_FREE_CONNECTIONS
Message: The server was unable to find a free connection %2 times in the last %3 seconds. This indicates a spike in network traffic. If this is happening frequently, you should consider increasing the minimum number of free connections to add headroom. To do that, modify the MinFreeConnections and MaxFreeConnections for the LanmanServer in the registry.

Resolve
Modify the MinFreeConnections and MaxFreeConnections parameters

If the server is frequently unable to find a free connection, you should consider increasing the minimum and maximum number of free connections to the server.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

To increase MinFreeConnections and MaxFreeConnections for the server:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click to select the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type MinFreeConnections, and then press Enter.
  5. Right-click MinFreeConnections, and then click Modify.
  6. In the Value data box, type the desired value, and then click OK.
  7. On the Edit menu, point to New, and then click DWORD Value.
  8. Type MaxFreeConnections, and then press Enter.
  9. Right-click MaxFreeConnections, and then click Modify.
  10. In the Value data box, type the desired value, and then click OK.

For additional infoirmation about setting MinFreeConnections and MaxFreeConnections, see http://support.microsoft.com/kb/317249.

 

Verify

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify SMB configuration settings:

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click to select the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters
  3. Verify that the correct parameters are present and contain the correct values.

 

Related Management Information

Shared Folders (SMB) Server Configuration

File Services

Related:

SMB Server unable to find a free connection

Details
Product: Windows Operating System
Event ID: 2022
Source: server
Version: 5.2.3790.1830
Message: SMB Server unable to find a free connection
   
Explanation

The server was unable to find a free connection %2 times in the last %3 seconds. This indicates a spike in network traffic. If this is happening frequently, you should consider increasing the minimum number of free connections to add headroom. To do that, modify the MinFreeConnections and MaxFreeConnections for the LanmanServer in the registry.

Cause

There was a spike in network activity.

   
User Action

Retry the connection.

Related:

The Microsoft Exchange Replication Service VSS writer failed with error code %1 when collecting the metadata document in preparation for a backup.

Details
Product: Exchange
Event ID: 2022
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: VSSWriterMetadataError
Message: The Microsoft Exchange Replication Service VSS writer failed with error code %1 when collecting the metadata document in preparation for a backup.
   
Explanation

This Error event indicates that the writer of the Volume Shadow Copy Service (VSS) of the Microsoft® Exchange Replication service could not perform a VSS backup because the VSS writer could not collect metadata information. VSS backups require metadata before the backups can continue. When this information cannot be collected by the VSS writer, this event will be triggered with a specific error. The error code will specify the source of the failure. Possible causes of this error include the following conditions:

  • A function call by the VSS writer into the VSS framework has failed.

  • The VSS writer could not access cached information when it prepared to collect metadata.

   
User Action

To resolve the error, follow one or more of these steps:

  • Run the VSS backup again.

  • Contact Microsoft Product Support Services. For information about how to contact support, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: