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 2032 — Firewall Rule Processing

Event ID 2032 — Firewall Rule Processing

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Windows Firewall with Advanced Security receives its rules from local security policy stored in the system registry, and from Group Policy delivered by Active Directory. After receiving a new or modified policy, Windows Firewall must process each rule in the applied policies to interpret what network traffic is to be blocked, allowed, or protected by using Internet Protocol security (IPsec).

When appropriate auditing events are enabled (http://go.microsoft.com/fwlink/?linkid=92666), Windows reports successes and failures, both in retrieving policy and in processing the rules defined in the policy.

Event Details

Product: Windows Operating System
ID: 2032
Source: Microsoft-Windows-Windows Firewall with Advanced Security
Version: 6.1
Symbolic Name: WFRestoreDefaultsEvent
Message: Windows Firewall has been reset to its default configuration.

%tModifyingUser:%t%1
%tModifyingApplication:%t%2

Resolve

This is a normal condition. No further action is required.

Related Management Information

Firewall Rule Processing

Windows Firewall with Advanced Security

Related:

The Microsoft Exchange Replication Service VSS Writer (instance %1) failed when terminating the backup.

Details
Product: Exchange
Event ID: 2032
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: VSSWriterAbortError
Message: The Microsoft Exchange Replication Service VSS Writer (instance %1) failed when terminating the backup.
   
Explanation

This Error event indicates that the writer of the Volume Shadow Copy Service (VSS) of the Microsoft Exchange Replication Service did not exit the ongoing backup process when the VSS writer received a request to stop the backup. The VSS writer might not exit a backup process as requested because it did not recognize the backup set.

   
User Action

To resolve this error, do one or both of the following:

  • Run VSS backup again on the storage group on which backup was stopped. If the successive VSS backups fail with a backup-in-progress error, stop and restart the following services from the Services snap-in. This will clear the backup-in-progress state for the storage groups that are affected by this failure:

    • Microsoft Exchange Information Store service.

    • Microsoft Exchange Replication Service.

  • If you are using cluster continuous replication (CCR), stop the backup process that is running, restart the passive node of the cluster, and then try the backup again.

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:

A fatal internal MTA error occurred. Contact Microsoft Technical Support. Buffer pool misused. Header/element at address value. [valuevaluevaluevalue] (16)

Details
Product: Exchange
Event ID: 2032
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: A fatal internal MTA error occurred. Contact Microsoft Technical Support. Buffer pool misused. Header/element at address value. [valuevaluevaluevalue] (16)
   
Explanation
The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full.
   
User Action
If the Microsoft Exchange Server disk is full, delete any unneeded files. If you suspect a disk error, run Chkdsk.

Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Contact Microsoft Product Support Services.

Related: