2012-07-05
03:29 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Windows Eventing Collection Service Error
We recently started migrating to the Windows Eventing Collection Service but e came across the following error in the message viewer (NIC System): Details: HTTP call failed: Action=WinHttpSendRequest, Endpoint=https://hostipaddress:5986, Last Error=12175 Any ideas what it might be? Thanks!
1 Reply
2012-08-21
10:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Milko,
This looks like the same issue described here: http://rsaenvision.lithium.com/t5/Share-Event-Source-Integrations/Cisco-Secure-IDS-IPS-Asynchronous-...
This is caused when the following ms update
(MS10-049: Vulnerabilities in SChannel could allow remote code execution) is applied causing the following registry entry to be modified and losing it's configuration,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL.
By adding the following 2 DWORD values and rebooting the appliance it should hopefully correct the problem.
AllowInsecureRenegoServers value: 1 UseScsvForTls value: 1
Good Luck,
Steve
This looks like the same issue described here: http://rsaenvision.lithium.com/t5/Share-Event-Source-Integrations/Cisco-Secure-IDS-IPS-Asynchronous-...
This is caused when the following ms update
(MS10-049: Vulnerabilities in SChannel could allow remote code execution) is applied causing the following registry entry to be modified and losing it's configuration,
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\SCHANNEL.
By adding the following 2 DWORD values and rebooting the appliance it should hopefully correct the problem.
AllowInsecureRenegoServers value: 1 UseScsvForTls value: 1
Good Luck,
Steve
