Network Management

"Client's time zone and SWIS time zone has to be the same" in Information Services log

When trying to view the Node Details page, an error occurs. In the logs, you can find error messages that the client's time zone and the SWIS time zone are not the same.

First published date

11/5/2018 8:06 PM

Last published date

7/9/2025 5:57 PM

Overview

When trying to view the Node Details page, an error occurs.

In the logs, you can find error messages that the client's time zone and the SWIS time zone are not the same.

 

OrionWeb.log (C:\ProgramData\SolarWinds\Logs\Orion)

<Timestamp> ERROR ASP.global_asax - (null)  Application_Error: Inner exception
SolarWinds.Orion.Web.InformationService.SwisQueryException: Error: A query to the SolarWinds Information Service failed. ---> System.ServiceModel.FaultException`1[SolarWinds.InformationService.Contract2.InfoServiceFaultContract]: RunQuery failed, check fault information.
Client's time zone and SWIS time zone has to be the same. Client time zone: Eastern Standard Time ; SWIS time zone: Central Standard Time
   at SolarWinds.InformationService.InformationServiceClient.InformationServiceCommand.CreateFaultException(Message message)
   at SolarWinds.InformationService.InformationServiceClient.InformationServiceCommand.HandleQueryResponse(Message message)

 

 

SWISv3.log (C:|ProgramData\SolarWinds\Information Service\v3)

<Timestamp> ERROR SolarWinds.InformationService.Core.InformationService - w3wp| /LM/W3SVC/2/ROOT-1-131595452921720792| SolarWinds.Netflow.Web.Reporting.SWISHelper.Query()| /Orion/NetPerfMon/NodeDetails.aspx?NetObject=N:250 (null)  Exception caught in method SolarWinds.InformationService.Core.InformationService.RunQuery
System.InvalidTimeZoneException: Client's time zone and SWIS time zone has to be the same. Client time zone: Eastern Standard Time ; SWIS time zone: Central Standard Time
   at SolarWinds.Data.Providers.NetFlow.CustomEntities.TimePeriodCalculatorEntity.GetDataInternal(CustomEntityInfo entity)
   at SolarWinds.Data.Providers.NetFlow.CustomEntities.Base.CustomEntityBase.GetData(CustomEntityInfo ent)
   at SolarWinds.Data.Providers.NetFlow.NetFlowCustomEntitiesProvider.CreateRelation(IStorageEntityReference entityRef, IEnumerable`1 properties)
   at SolarWinds.Data.Query.PhysicalQueryPlan.ProviderScanOp.<GetEnumeratorInternal>d__5.MoveNext()
   at SolarWinds.Data.Query.PhysicalQueryPlan.ProjectOp.<GetEnumeratorInternal>d__7.MoveNext()
   at SolarWinds.Data.Query.PhysicalQueryPlan.PhysicalQueryPlan.<GetEnumerator>d__4.MoveNext()
   at SolarWinds.InformationService.Serialization.XmlResponseSerializer..ctor(IQueryResultReader reader, Boolean includeQueryPlan, IQueryStatisticsContext statistics, I18n i18N)

Product section

Network Performance Monitor

Cause

The time zone set on the client is different from the SWIS time zone.

Resolution

Set the date, time and time zone on your server to correspond with the SWIS time zone.

To find out the time zone to set, contact your database administrator.

  1. From the Start screen of the MultiPoint Server computer, open Control Panel.
  2. Under Clock, Language, and Region, click Set the time and date.
  3. On the Date and Time tab, verify the date and time. If they are not correct, click Change date and time, update the date and time, and then click OK.
  4. Under Time zone, verify the time zone.
  5. If it is not correct, click Change time zone, select the correct time zone, and then click OK.
  6. Click OK again to save your settings and close the dialog box.
  7. Restart all services - Shutdown and restart Orion services

The Node Details page now displays the current time zone without issues.