Home
  •  

Rasman port open failure

Rasman_port_open_failure_1_Rule (Rule)

Knowledge Base article:

Management Pack
Summary
The Routing and Remote Access service or The Remote Access Connection Manager service encountered an error while opening a port for remote access.
 
Causes
The most common reasons for this error are:
  1. The Remote Access Connection Manager service failed to start the RAS Async Adapter driver (AsyncMac). The most common reasons for this error are:
    1. The RAS Async Adapter driver (AsyncMac) failed to initialize.
    2. The Remote Access Connection Manager service does not have sufficient permissions to open the driver.
  2. The Remote Access Connection Manager service failed to load rasser.dll.
  3. The modem has moved to an unsupported BPS rate.
  4. The serial driver could not allocate adequate I/O queues.
 
Resolutions
  1. Check whether the System account has read/execute permissions for the file %systemroot%\system32\drivers\asyncmac.sys. To check the permissions:
    1. Right-click the file name, and then click Properties.
    2. On the Securities tab, verify that the System account read/execute permissions for the file.
  2. Verify whether the file rasser.dll exists at %systemroot%\system32 folder.
  3. Verify whether the System account has read/execute permissions for rasser.dll. To check whether the System account has these permissions:
    1. Right-click rastapi.dll, and click Properties.
    2. On the Security tab, verify whether the System account has read/execute permissions for rastapi.dll. If it does not, add them.
  4. Move the modem to a supported BPS rate.
  5. Stop and restart the Routing and Remote Access service.
  6. If the problem persists, you might need to repair or reinstall the Windows operating system
 
Sample Event
Sample Event #1: An attempt by RASSER.DLL to get an async media access control handle failed.
Sample Event #2: RASMXS.DLL cannot load RASSER.DLL.
Sample Event #3: The modem on %1 moved to an unsupported BPS rate.
Sample Event #4 The serial driver could not allocate adequate I/O queues.This may result in an unreliable connection.
Sample Event #5:Remote Access Connection Manager could not reopen biplex port %1. This portwill not be available for calling in or calling out.Restart all Remote Access Service components.
 
© 2004 Microsoft Corporation, all rights reserved.

Element properties:

TargetMicrosoft.Windows.RemoteAccess.2012.Class.VPNServer
CategoryEventCollection
EnabledTrue
Alert GenerateFalse
RemotableTrue
Event LogSystem

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
WriteToDB WriteAction Microsoft.SystemCenter.CollectEvent Default

Source Code:

<Rule ID="Rasman_port_open_failure_1_Rule" Enabled="true" Target="Microsoft.Windows.RemoteAccess.2012.Class.VPNServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>System</LogName>

      <Expression>

        <And>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>MatchesRegularExpression</Operator>

              <Pattern>^(20040|20041|20059|20060|20061)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <RegExExpression>

              <ValueExpression>

                <XPathQuery Type="String">PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>MatchesRegularExpression</Operator>

              <Pattern>RemoteAccess|Rasman</Pattern>

            </RegExExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="WriteToDB" TypeID="SystemCenter!Microsoft.SystemCenter.CollectEvent"/>

  </WriteActions>

</Rule>