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 102 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: 102
Event Source: discovdll
Event Type: Error
Event Description: Date: *******   Source: discovdll
Time: ****      Category: None
Type: Error     EventID: 102
User: N/A
Computer:

Description:
The Discoverer client DLL detected RPC execption 1702 in function GetLogonStatus.
Comment: I have a PC that seems to drop off the network. It means that users can not logon to the PC evening if their profile is in cache. This seems to be because the PC can not find a Domain Controller when it reboots. However the user logon error still happen if the users lets PC lockdown if itís not in use.
I can logon on to the PC on the local administrative account and when I do so I can ping the DCís and map a drive (If I provide a domain account). If I continue to reboot the PC after about 56 time the user can logon.
This error is shown in conjunction with an EventID error 107 Source discovdll Unable to commit the discovererServerName property to the Active Directory.

Has anyone come across these errors before  
Thank you
Event ID: 102
Event Source: hpeaadsm
Event Type: Information
Event Description: A new path (SCSI address Port X XX XX XX) was added to existing multipath capable disk.
Comment: hpeaadsm is the Storage related DSM driver for MPIO connected Disks the Event descripes explorations of new SAN path.
Event ID: 102
Event Source: NICECTI
Event Type: Warning
Event Description: The description for Event ID ( 102 ) in Source ( NICECTI ) 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: Subject:  Msg: CLucentStream::GetCallMembers - Failed to get confirmation (CSTA_SNAPSHOT_CALL_CONF) on get call members (cstaSnapshotCallReq) request. Event class 5 and event type 53 were received... InvokeID = 186..
Comment: This warning refer to Nice application when it is running on the Win2003Server.
However MS not have information about this.
http://img177.imageshack.us/my.phpimage=eventvwrnictcticd9.png
Event ID: 102
Event Source: HP Smart Array
Event Type: Error
Event Description: Description:
A logical drive status has changed to Error.

User Action
Check for failed or removed physical drives.

WBEM Indication Properties
AlertingElementFormat: 2 0x2 (CIMObjectPath)
AlertingManagedElement: "\\Servername\ROOT\HPQ:HPSA_StorageVolume.CreationClassName="HPSA_StorageVolume"DeviceID="EMBEDDED-LD1"SystemCreationClassName="HPSA_ArraySystem"SystemName="EMBEDDED""
AlertType: 5 0x5 (Device Alert)
Description: "A logical drive status has changed to Error."
DeviceOperationalStatus[0]: 6 0x6 (Error)
DeviceOperationalStatusPrevious[0]: 6 0x6 (Error)
EventCategory: 6 0x6 (Primary Storage Device)
EventID: "102"
EventTime: "20100318234602.138000-000"
HWLogicalLocation[0]: "Logical Drive 2 (RAID 0)"
ImpactedDomain: 4 0x4 (System)
IndicationIdentifier: "{60A1690E-135F-47B0-9044-A715BA06AD2A}"
IndicationTime: "20100318234602.154000-240"
NetworkAddresses[0]: "W.X.Y.Z"
OSType: 70 0x46 (Microsoft Windows Server 2003 64-Bit)
OSVersion: "5.2.3790"
PerceivedSeverity: 5 0x5 (Major)
ProbableCause: 86 0x56 (Disk Failure)
ProbableCauseDescription: "Logical Drive Status Changed to Error"
ProviderName: "HP Smart Array"
ProviderVersion: "2.3.0.0"
RecommendedActions[0]: "Check for failed or removed physical drives."
Summary: "Logical drive status error"
SystemCreationClassName: "HP_WinComputerSystem"
SystemFirmwareVersion[0]: "2004.12.02"
SystemFirmwareVersion[1]: "2004.12.02"
SystemGUID: "35303733-3639-5355-5835-313230305746"
SystemModel: "ProLiant DL380 G4"
SystemName: "XXXXXXXXXXXXXX"
SystemProductID: "370596-001"
SystemSerialNumber: "XXXXXXXX"
TIME_CREATED: 129134439693102166 0x1cac716b62d2c56
VariableNames[0]: "FailureDescription"
VariableTypes[0]: 1 0x1 (string)
VariableValues[0]: "Failed"

For more information please contact HP Support.
Comment:
Event ID: 102
Event Source: AD FS 2.0
Event Type: Error
Event Description: There was an error in enabling endpoints of Federation Service. Fix configuration errors using PowerShell cmdlets and restart the Federation Service.

Additional Data
Exception details:
System.ArgumentNullException: Value cannot be null.
Parameter name: certificate
   at System.IdentityModel.Tokens.X509SecurityToken..ctor(X509Certificate2 certificate String id Boolean clone Boolean disposable)
   at System.IdentityModel.Tokens.X509SecurityToken..ctor(X509Certificate2 certificate)
   at Microsoft.IdentityServer.Service.Configuration.MSISSecurityTokenServiceConfiguration.Create(Boolean forSaml)
   at Microsoft.IdentityServer.Service.Policy.PolicyServer.Service.ProxyPolicyServiceHost.ConfigureWIF()
   at Microsoft.IdentityServer.Service.SecurityTokenService.MSISConfigurableServiceHost.Configure()
   at Microsoft.IdentityServer.Service.Policy.PolicyServer.Service.ProxyPolicyServiceHost.Create()
   at Microsoft.IdentityServer.Service.SecurityTokenService.STSService.StartProxyPolicyStoreService(ServiceHostManager serviceHostManager)
   at Microsoft.IdentityServer.Service.SecurityTokenService.STSService.OnStartInternal(Boolean requestAdditionalTime)
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...