Troubleshooting Events Connected to Schannel, HTTP Errors, and TCP/IP DNS (4035329)

You may experience issues protecting an Agent that are the result of environmental configuration settings.

For instance, several SSL, IIS or HTTP driver settings can cause errors to occur when protecting an agent.

For more information regarding environmental settings that can affect agent protection, click here.

1. Open a browser and type https://127.0.0.1:8006/apprecovery/api/agent/pair/connect.
2. You should receive the following message: <guid xmlns=”http://schemas.microsoft.com/2003/10/Serialization/“>ed2cd4ac-7960-4739-ae11-425fce678960</guid>
   1. If you do not receive this message, it could be the result of SSL, IIS, or HTTP settings issues.
   2. Until  https://127.0.0.1:8006/apprecovery/api/agent/pair/connect  will not work the Agent could not be protected.
3. Should the previous step prove unsuccessful, do the following:
   1. Stop the agent service.
   2. Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\AppRecovery\Agent\serviceHost ;
   3. Change the ServiceBaseAddress key to http://127.0.0.1:8006/apprecovery/api/  and restart the agent service.

Events connected to Schannel – Known Issue

There is a known issue in which the TLS client authentication fails between Unified Communications peers with a logged Schannel warning.

To troubleshoot this issue, you will need to set the spatial registry key. Please complete the following steps.

1. Open registry editor and navigate to the following registry subkey:
   1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL
2. On the Edit menu, point to New, and then click DWORD Value.
3. Type SendTrustedIssuerList, and then press Enter to name the registry entry.
4. Right-click SendTrustedIssuerList, and then click Modify.
5. In the Value data box, type 0 if that value is not already displayed, and then click OK.

For more information please visit – http://support.microsoft.com/kb/2464556/

Events Connected to HHTP Error – Known Issue

You may  receive an error message that states “The page cannot be displayed” error, and “Connections_refused” entries are logged in the Httperr.log file on a machine which is running Windows Server 2003, Exchange 2003, and IIS 6.0

To resolve this issue, complete the following steps.

1. Open Registry Editor and navigate to the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
2. On the Edit menu, point to New, and then click DWORD Value.
3. Type EnableAggressiveMemoryUsage, and then press Enter.
4. On the Edit menu, click Modify.
5. In the Value data box, type 1, and then click OK.
6. Restart the HTTP service:
   1.  Open command prompt
   2.  Type net stop http /y, and then press Enter.
   3.  Type iisreset /restart, and then press Enter.

For more information please visit – http://support.microsoft.com/kb/934878/

Events that are Connected to TCP/IP DNS – Known Issue

The error can occur in the following formats:

• TCP_PROV: An existing connection was forcibly closed by the remote host.
• “ProviderNum: 7, Error: 10054, ErrorMessage: “TCP Provider: An existing connection was forcibly closed by the remote host …”
• Unhandled Exception: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 – An existing connection was forcibly closed by the remote host.)

To resolve this issue please add the following registry key in the registry editor:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\

• Type – DWORD;
• Name – SynAttackProtect;
• Value – 00000000.

For more information visit – http://msdn.microsoft.com/en-us/library/ms187005%28v=sql.105%29.aspx