Director error: Cannot retrieve the data. for User Connection Failures and Failed Server OS Machines

[Paul Tanner]

I am having an issue with the User Connection Failures and Failed Server OS Machines not displaying properly in Director 7.15 CU2.  We have 2 sites with 3 DDC in each site.   I have Director setup to monitor both sites.  I am only having this issue on one site.   I have checked the Monitor DB and I don't see any issues or lines with all zeroes.  I have restarted all controllers and services.  

 

Controllers running 7.15 CU2

Director version 7.15 CU2

 

Error in Director Log:

10/30/2019 08:55:50.7000 : [t:50, s:dttnxrhzqgxbbvkk2cjtxeyo] Dmc Service error
 Citrix.Dmc.Common.ConnectorException: Monitoring Service ---> Citrix.Dmc.Common.CommunicationException: Monitoring Service ---> System.Data.Services.Client.DataServiceQueryException: An error occurred while processing this request. ---> System.Data.Services.Client.DataServiceClientException: <?xml version="1.0" encoding="utf-8"?><m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"><m:code /><m:message xml:lang="en-US">An error occurred while processing this request.</m:message><m:innererror><m:message>Exception has been thrown by the target of an invocation.</m:message><m:type>System.Reflection.TargetInvocationException</m:type><m:stacktrace>   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)&#xD;
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)&#xD;
   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)&#xD;
   at System.Data.Services.Providers.BaseServiceProvider.InvokeServiceOperation(ServiceOperation serviceOperation, Object[] parameters)&#xD;
   at System.Data.Services.Providers.DataServiceProviderWrapper.InvokeServiceOperation(OperationWrapper serviceOperation, Object[] parameters)&#xD;
   at System.Data.Services.RequestUriProcessor.ComposeExpressionForServiceOperation(SegmentInfo segment, IDataService service, Boolean checkRights, SegmentInfo lastSegment)&#xD;
   at System.Data.Services.RequestUriProcessor.ComposeExpressionForSegments(IList`1 segments, IDataService service, Boolean isCrossReferencingUri)&#xD;
   at System.Data.Services.RequestUriProcessor.ProcessRequestUri(Uri absoluteRequestUri, IDataService service, Boolean internalQuery)&#xD;
   at System.Data.Services.DataService`1.HandleRequest()</m:stacktrace><m:internalexception><m:message>Too many data points requested [1966] for the trend operation. You can request a maximum of 1000 data points.</m:message><m:type>System.InvalidOperationException</m:type><m:stacktrace>   at Citrix.Monitor.Repository.VShared.ValidationHelper.ValidateNumberOfIntervals(DateTime startDate, Nullable`1 endDate, Int32 intervalLength)&#xD;
   at Citrix.Monitor.Repository.SessionRepository.GetConnectionFailureTrendsByType(DateTime startDate, Nullable`1 endDate, Int32 intervalLength, ConnectionFailureType connectionFailureType, IEnumerable`1 propertiesToLoad)&#xD;
   at Citrix.Monitor.DataService.ServiceOperationUtilities.GetConnectionFailureTrendsByType(IUserObjects delegatedAdminUser, DateTime startDate, Nullable`1 endDate, Int32 intervalLength, Int32 connectionFailureType)&#xD;
   at Citrix.Monitor.DataService.DelegatedAdminAuthorizedServiceOperations.GetConnectionFailureTrendsByType(DateTime startDate, Nullable`1 endDate, Int32 intervalLength, Int32 connectionFailureType)</m:stacktrace></m:internalexception></m:innererror></m:error>
   at System.Data.Services.Client.QueryResult.ExecuteQuery()
   at System.Data.Services.Client.DataServiceRequest.Execute[TElement](DataServiceContext context, QueryComponents queryComponents)
   --- End of inner exception stack trace ---
   at System.Data.Services.Client.DataServiceRequest.Execute[TElement](DataServiceContext context, QueryComponents queryComponents)
   at Citrix.Dmc.Connector.MonitoringService.MonitoringServiceClient.<>c__DisplayClass6_0.<GetConnectionFailureTrend>b__0(ServiceOperationClient client)
   at Citrix.Dmc.Connector.MonitoringService.MonitoringServiceClient.CallMonitoringServiceMethod[T](Action`1 msMethod)
   --- End of inner exception stack trace ---
   at Citrix.Dmc.Connector.MonitoringService.MonitoringServiceClient.CallMonitoringServiceMethod[T](Action`1 msMethod)
   at Citrix.Dmc.Connector.MonitoringService.MonitoringServiceClient.GetConnectionFailureTrend(DateTime startDate, Nullable`1 endDate, Int32 intervalLength, Int32 connectionFailureType)
   at Citrix.Dmc.Connector.MonitoringService.MonitoringServiceConnector.GetConnectionFailuresTrend(ConnectionFailureType failureType, DateTime startTime, Nullable`1 endTime, Int32 intervalInMin)
   at Citrix.Dmc.WebService.XDConsoleDao.<>c__DisplayClass12_0.<GetConnectionFailuresDetailsByType>b__0(IMonitoringServiceConnector i)
   at Citrix.Dmc.Common.ConnectorWrapper`1.Invoke[TReturn](Func`2 method)
   --- End of inner exception stack trace ---
   at Citrix.Dmc.Common.ConnectorWrapper`1.Invoke[TReturn](Func`2 method)
   at Citrix.Dmc.WebService.XDConsoleDao.GetConnectionFailuresDetailsByType(String siteId, ConnectionFailureType failureType, Int64 startTime, Int32 intervalInMin)
   at Citrix.Dmc.WebService.ConsoleService.GetConnectionFailuresDetailsByType(String siteId, String failureType, Int64 startTime, Int32 intervalInMin)

 

 

[Sandeep Sandeep]

Hi,

 

Do you still see this issue? CU5 has few fixes for similar issues. You could upgrade to CU5 and test

 

Sandeep.