Symantec Protection Center 2.1.1.3012 (SPC) A communication error occurred while requesting data feed IncidentEvents from the product Server GLOBAL NEWS PRODUCT SERVER RESOURCE

Article Id: 157061
Status: Published
Updated On: 06-06-2013 15:17
Legacy Id: TECH196865
Products:
Protection Center
Issue/Introduction:

Failed to request data feed IncidentEvents due to network
error on SPC multiple times daily. 

 

File Name: C:\ProgramData\Symantec\SMP\Logs\a.log
Date:
Type: Error
Description: Raising Critical alert  XXX for
server GLOBAL NEWS PRODUCT SERVER RESOURCE with message: An communication error
occurred while requesting data feed IncidentEvents from product server Global
News Product Server Resource. **CEDUrlStart** :XXXXX  Source: Middletier:RaiseAlert
Process: Symantec.SPC.Middletier.Services
PID: 3040
Thread: 77
Tick Count: 6487941
Module: Symantec.SPC.Middletier.Services.exe
Host Name: SPC-3012

 

Error#2

Failed to communicate with the Deepsight Hosted
Server  
File Name: C:\ProgramData\Symantec\SMP\Logs\a.log
Date:
Type: Error
Description: Data Feed encountered a
Communication exception: System.ServiceModel.EndpointNotFoundException: Could
not connect to spc.deepsight.comXXXXXX. TCP error code 10060:
A connection attempt failed because the connected party did not properly
respond after a period of time, or established connection failed because
connected host has failed to respond XXX.XXX.XXX:7891. --->

Cause:

Unknown

Resolution:

There is currently no solution, The issue has been reported to the respective teams.

-------
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers.

This issue is currently being considered by Symantec to be addressed in the next major revision of the product. There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. Please note that Symantec reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please refer to the following Web site:

 

Note:  There is a known issue that is currently being worked on by development.  If the above instructions do not resolve your problem, it is likely you are experiencing this problem.  Please watch for updates to this KB article, or watch Product Notifications feed for updates.

This KB article does not pertain to SPC Enterprise 3.0.  The Deepsight functionality within SPC Enterprise 3.0 functions differently and there for the known issue in SPC 2.0  being worked on is not a problem in SPC Enterprise 3.0.


Applies To

SPC 2.1.0.2075, SPC 2.1.1.3012 MP1