Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Comments for event ID 13 currently in the processing queue.

Note: We have not reviewed this information yet so it is unfiltered, exactly how it was submitted by our contributors.

Event ID: 13
Event Source: Directory 5
Event Type: Error
Event Description:
Event Type:          Error


Event Source:       Directory 5

Event Category:   None

Event ID:  13

Date: 5/7/2005

Time:                     12:13:27 PM

User:                     N/A

Description:

The description for Event ID (13) in Source (Directory 5) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: slapd-anything 0.

Comment:
Event ID: 13
Event Source: Diskmon
Event Type: Error
Event Description: The description for Event ID ( 13 ) in Source ( Diskmon ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Error: Error InitializeApp Bad file name or number 52.

Comment:
Event ID: 13
Event Source: CAMLoggingService
Event Type: Error
Event Description: Logging update cycle failed unexpectedly during normal operation.
(Error: Logging cycle failed [OnTimer() exception] ! (Error number 3 at line 496 in file ArionException.cpp).)
Comment:
Event ID: 13
Event Source: RMS
Event Type: Warning
Event Description: An improperly signed or structured message was found in the message queue.  This message will not be added to the database.  If you recently upgraded your Microsoft.NET CLR please ensure that your pipelines and logging service are running against the same CLR version.  For all other problems please refer to your documentation.  The following information was reported: Microsoft.DigitalRightsManagement.Core.PropertyBagInvalidHashException: The property bag hash is invalid.
   at Microsoft.DigitalRightsManagement.Logging.DRMSLogging.ValidatePropertyBag(IDrmsPropertyBag receivedPropertyBag String receivedHashString String receivedSignatureString)

For more information see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Comment:
Event ID: 13
Event Source: DeviceLink
Event Type: Error
Event Description: [09:27:54:078] [TransAgentRapi] [ipaqdevice.dll] [MapDeviceConnect] Device DLL error occurred [1460] [This operation returned because the timeout period expired.]
Comment:
Event ID: 13
Event Source: SescLU
Event Type: Error
Event Description: LiveUpdate returned a non-critical error. Available content updates may have failed to install.
Comment: This is pop up dozens of error popups titles: Microsoft Visual C++ Runtime Library.
Runtime error!
Program:  C:\Windows\system32\cscript.exe
R6034
An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.
Event ID: 13
Event Source: nps
Event Type: Error
Event Description: This condition can occur under the following circumstances:

In the NPS Microsoft Management Console (MMC) a RADIUS client is configured by fully qualified domain name (FQDN) or NetBIOS name rather than by IP address and NPS has not received a DNS server response to the name resolution query. Without the IP address provided by the name resolution query NPS cannot contact the RADIUS client.
NPS is receiving communication from a RADIUS client that is not configured in the NPS MMC.
In the NPS MMC a RADIUS client is configured by either IPv4 or IPv6 address but the format of the IP address is incorrect.
To perform this procedure you must be a member of Domain Admins.

Comment: To fix DNS name resolution issues:

Use DNS client and server troubleshooting information to diagnose and repair the DNS name resolution issue. For more information see DNS Server at http://go.microsoft.com/fwlink/LinkId=110949.
In the NPS MMC configure the RADIUS client with the IP address of the RADIUS client rather than the DNS name.
To configure a new RADIUS client:

Click Start Administrative Tools Network Policy Server. The NPS MMC opens.
Double-click RADIUS Clients and Servers.
Right-click RADIUS Clients and then click New RADIUS client.
Follow the steps in the New RADIUS Client Wizard.
To configure the IP address of a RADIUS client:

Click Start Administrative Tools Network Policy Server. The NPS MMC opens.
Double-click RADIUS Server and Clients.
Click RADIUS Clients and in the details pane right-click the RADIUS client that you want to configure. Click Properties and then type an IP address in Address (IP or DNS).
Verify
You can use the following procedure to verify that DNS name resolution errors are resolved. In addition you can use ping results to verify the RADIUS client configuration in the NPS MMC.

To verify the RADIUS client configuration:

Open Command Prompt.
Using ping.exe ping the RADIUS client using the RADIUS client name. For example if the RADIUS client name is NAS-01 type ping NAS-01 and then press ENTER.
If ping can resolve the name of the RADIUS client to an IP address the DNS name resolution error is resolved and the ping results match the RADIUS client configuration in the NPS MMC.
Related Management Information
RADIUS Client Configuration

Network Policy Server Infrastructure

Event ID: 13
Event Source: UmxCC
Event Type: Error
Event Description: The Windows Security Health Agent failed to complete an offline scan.
Failure Code: 80248011.

Comment: Getting the BSOD (blue screen of death every morning.
Event ID: 13
Event Source: sidebyside
Event Type: Error
Event Description: Activation context generation failed for "E:\program files\Corel PaintShop Photo Pro\X3\PSPClassic\Python Libraries\Lib\distutils\command\wininst-9.0-amd64.exe". Dependent Assembly Microsoft.VC90.CRTprocessorArchitecture="amd64"publicKeyToken="1fc8b3b9a1e18e3b"type="win32"version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.
Comment: I removed Corel File Shell monitor from strat up
Event ID: 13
Event Source: HAL
Event Type: Error
Event Description: level=Critical
Source=HAL
Task Category=none
Comment:
Event ID: 13
Event Source: NPS
Event Type: Error
Event Description: Applies to: Windows Server 2008

Protocolname: System
Source:       NPS
Date:        26.04.2016 05:15:32
EVENTID:   13
Description:
A RADIUS message was received from the invalid RADIUS client IP address xxx.xxx.xxx.xxx.

Comment: Take a look at:
https://technet.microsoft.com/en-us/library/cc735406(v=ws.10).aspx
Event ID: 13
Event Source: HAL
Event Type: Error
Event Description: Le temporisateur de surveillance du système a été déclenché.
Comment:
Event ID: 13
Event Source: nvlddmkm
Event Type: Error
Event Description: The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer the display information had to be saved with the event.

The following information was included with the event:

\Device\Video1
Graphics Exception: Shader Program Header 9 Error

Comment:

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...