The Routing Information Protocol version 2 (RIPv2) encountered an error in socket operation.
The most common reasons for this warning are:
The connection has been dropped, because of a network failure or because the system on the other end went down without notice.
The network subsystem has failed.
The Windows Sockets implementation was unable to allocate the needed resources for its internal operation.
Sample Event#1: IPRIPv2 was unable to receive an incoming messageon the local interface with IP address %1.The data is the error code.
Sample Event#2: IPRIPv2 was unable to send a packet from the interface with IP address %1to the IP address %2.The data is the error code.
Sample Event#3: IPRIPv2 was unable to enumerate network events on the local interfacewith IP address %1.The data is the error code.
Sample Event#4: IPRIPv2 detected an error on the local interface with IP address %1.The error occurred while the interface was receiving packets.The data is the error code.
Sample Event#5: IPRIPv2 was unable to request notification of eventson the socket for the local interface with IP address %1.The data is the error code.
Sample Event#6: IPRIPv2 was unable to create a socket for the local interfacewith IP address %1.The data is the error code.
Sample Event#7: IPRIPv2 could not enable broadcasting on the socket forthe local interface with IP address %1.The data is the error code.
Sample Event#8: IPRIPv2 could no t bind to port 520 on the socket forthe local interface with IP address %1.The data is the error code.
Sample Event#9: IPRIPv2 could not request multicasting on the local interfacewith IP address %1.The data is the error code.
Sample Event#10: IPRIPv2 could not join the multicast group 224.0.0.9on the local interface with IP address %1.The data is the error code.
If the server is low on memory, take appropriate action to increase the available memory. See Help and Support Center for information on low memory.
Stop and restart the Routing and Remote Access service.
If the problem persists, restart the server.
Microsoft Corporation, all rights reserved
Target | Microsoft.Windows.RemoteAccess.2012.R2.Class.VPNServer |
Category | EventCollection |
Enabled | True |
Alert Generate | False |
Remotable | True |
Event Log | System |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.EventProvider | Default |
WriteToDB | WriteAction | Microsoft.SystemCenter.CollectEvent | Default |
<Rule ID="Socket_operation_failure_1_1_Rule" Enabled="true" Target="Microsoft.Windows.RemoteAccess.2012.R2.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>^(30020|30024|30045|30046|30047|30048|30049|30050|30051|30052)$</Pattern>
</RegExExpression>
</Expression>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>ContainsSubstring</Operator>
<Pattern>IPRIP2</Pattern>
</RegExExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WriteToDB" TypeID="SystemCenter!Microsoft.SystemCenter.CollectEvent"/>
</WriteActions>
</Rule>