Utility control point icons turn green and gray

Question

I am running SQL Server 2008 R2 Enterprise and have set up a MDW, Utility MDW and UCP, when enrolling the instances on the UCP, I get a warning about WMI but it allows me to enroll the instance.  After enrollment of the isntance I have seen the icons
turn green and provide data for each instance but after a few minutes the icons will turn gray again and no data will be seen in any of the tabs.  When I go back into the instance and refresh sometimes it will turn green and provide data, but after a
few seconds it turns gray again.  I have looked at the wmi get commands and verified that I can query the wmi data on each instance as discussed in this article:  http://msdn.microsoft.com/en-us/library/ee210592.aspx  I am not sure why it is
providing data sometimes (green icons) and then going back to gray icons (no data).  Can anyone give me some things to check?  It has been collecting data for a few days now...

Answer 1

Thank you for responding, you are the first one of many questions I have asked in other forums, there doesn't seem to be much support for UCP...
All the jobs on the UCP run successfully except the collection_set_5_noncached_collect_and_upload.  It runs successfully all 3 steps every 3rd attempt.  The 2 attempts in between fail on step 3 but since it eventually all runs not sure if that
is an issue or not.
On the managed instances the jobs all run as well but the same collection_set_5 has the same type of successes and failures where it will run successfully throughout the day but fails more than succeeds and
usually it is step 3 that fails.  But then it will succeed every half hour it seems.  
Another managed instance has the same issues with collection_set_5 but also has failures with the job collection_set_4_noncached_collect_and_upload where it will run multiple times and fail but succeeds every 1-2 hours.  so all jobs succeed at one time
or another, just not consistently succeeding.
Network connections are stable
Here is a common error from step 3 of the collection set 5 job:
Executed as user: ZBC\svc-sqlqrmv14. ...or. Component name: DFT - Upload Query Data 1, Code: -1071636471, Subcomponent: OLE DB Destination [62], Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.  
An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "The statement has been terminated.".   An OLE DB record is available.  Source: "Microsoft SQL Server Native Client
10.0"  Hresult: 0x80004005  Description: "Violation of PRIMARY KEY constraint 'PK_sysutility_cpu_memory_related_info_internal_clustered'. Cannot insert duplicate key in object 'snapshots.sysutility_ucp_cpu_memory_configurations_internal'. The duplicate
key value is (UTMSIV301\DEVQRM2008, 2014-07-25 12:54:00.5322361 -06:00, UTMSIV301).".   .SSIS error. Component name: DFT - Upload Query Data 1, Code: -1071607767, Subcomponent: OLE DB Destination [62], Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.
 The "input "OLE DB Destination Input" (75)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (75)" specifies failure on error. An error occurred on the specified object of the specified
component.  There may be error messages posted before this with more information about the failure.   .  SSIS error. Component name: DFT - Upload Query Data 1, Code: -1073450974, Subcomponent: SSIS.Pipeline, Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED.
 The ProcessInput method on component "OLE DB Destination" (62) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (75). The identified component returned an error from the ProcessInput method. The error is specific to
the component, but the error is fatal and will cause the Data Flow task to stop running.  There may be error messages posted before this with more information about the failure.   .SSIS error. Component name: DFT - Upload Query Data 2, Code: -1071636471,
Subcomponent: OLE DB Destination [46], Description: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.   An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005
 Description: "The statement has been terminated.".   An OLE DB record is available.  Source: "Microsoft SQL Server Native Client 10.0"  Hresult: 0x80004005  Description: "Violation of PRIMARY KEY constraint 'PK_sysutility_volumes_info_internal'.
Cannot insert duplicate key in object 'snapshots.sysutility_ucp_volumes_internal'. The duplicate key value is (UTMSIV301\DEVQRM2008, 2014-07-25 12:54:00.5322361 -06:00, \\?\Volume{7ce60f4c-196d-11e3-a041-002264c19516}\).".   .SSIS error. Component name:
DFT - Upload Query Data 2, Code: -1071607767, Subcomponent: OLE DB Destination [46], Description: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR.  The "input "OLE DB Destination Input" (59)" failed because error code 0xC020907B occurred, and the
error row disposition on "input "OLE DB Destination Input" (59)" specifies failure on error. An error occurred on the specified object of the specified component.  There may be error messages posted before this with more information about the failure.
  .SSIS error. Component name: DFT - Upload Query Data 2, Code: -1073450974, Subcomponent: SSIS.Pipeline, Description: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "OLE DB Destination" (46) failed with error code
0xC0209029 while processing input "OLE DB Destination Input" (59). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.  There
may be error messages posted before this with more information about the failure.   .The master package exited with error, previous error messages should explain the cause.  Process Exit Code 5.  The step failed.