Summary

Configuration issues that may prevent data getting into 1E Experience.

On this page:

No data in 1E Experience

ComponentThings to CheckNotes
Tachyon Coordinator
Log file (%programdata%\1E\Tachyon\Tachyon.Coordinator.log)


Check for entries of the following form to ensure that the Coordinator is successfully initiating Cube data processing:

INFO PokeCubeProcessing - Sending cube processing request to https://TACHYON.Acme.local:443/Experience/
INFO PokeCubeProcessing - Sent cube processing request successfully

Ensure no errors are reported in the Coordinator log.

The following value in %programfiles%\1E\Tachyon\Coordinator\Tachyon.Server.Coordinator.exe.config controls the frequency with which the Coordinator initiates cube processing.  

<add key="ExperienceCubeProcessingIntervalMinutes" value="1440" /> (every 24 hours).

It is not recommended that this value be changed.

1E Licensing
License file (%programdata%\1E\Licensing\Tachyon.lic

Ensure the Tachyon Server is licensed for 1E Experience:

<Feature name="TachyonPlatform">
<Consumer name="Platform" enable="on"> </Consumer>
<Consumer name="Experience" enable="on"> </Consumer>

Experience
Log file (%programdata%\1E\Tachyon\Tachyon.Experience.log)


If the log reports connection error messages such as the following, then ensure SQL Server Analysis Services (MSSQLSERVER) is running. If not restart it.

ERROR [INV02\Administrator] Tachyon.Server.Common.Http.WebApiExtensions.ApiControllerBase - Invalid request. Errors: [{"ErrorCode":"Metric.DeviceMetricHistoryCubeInvalidRequest","Message":"Device metric history request resulted in the error 'A connection cannot be made. Ensure that the server is running.'.","Data":["A connection cannot be made. Ensure that the server is running."]}]
Type: Tachyon.Server.Common.Error.Exceptions.InvalidRequestException
Message: Exception of type 'Tachyon.Server.Common.Error.Exceptions.InvalidRequestException' was thrown.
1 error:
Error 1: error code: Metric.DeviceMetricHistoryCubeInvalidRequest, message: Device metric history request resulted in the error 'A connection cannot be made. Ensure that the server is running.'.
StackTrace: at Tachyon.Server.Services.Experience.Providers.DeviceMetricHistoryCubeProvider.GetDeviceMetricAggregatedHistory(DeviceMetricAggregatedHistoryCubeSearch search) in C:\B\395\s\Server\Code\Experience\Tachyon.Server.Services.Experience\Providers\DeviceMetricHistoryCubeProvider.cs:line 67
at Tachyon.Server.Common.Http.WebApiExtensions.ApiControllerBase.TranslateToHttpStatus[TRecord](Func`1 action, Func`2 entityUriTranslator, HttpStatusCode successStatusCode) in C:\B\395\s\Server\Code\Common\Tachyon.Server.Common.Http\WebApiExtensions\ApiControllerBase.cs:line 32

To examine any SQL Server Analysis Services (MSSQLSERVER) error visit your C:\Program Files\Microsoft SQL Server\MSASxx.MSSQLSERVER\OLAP\Log directory and examine msmdsrv.log

If you are using Microsoft SQL Server 2016 SP1 then ensure cumulative update CU15 is installed (KB4495257 - 13.0.4574.0  - Apr 27 2019 17:23:50)

Experience UI
Browse to https://tachyon.acme.local/Tachyon/App/#/experience/overview and ensure you do not see the message "Error occurred"

If an error occurred is displayed please run the browser developer tools to analyze the Tachyon API calls used to populate this page. If for example, you see authorization errors then please check the SQL user permissions of the Cube using SQL Management Studio. If you see connection errors, check the SQL Service Analysis Service is running.

Cube Data
Ensure cube data has been populated

Check that Cube data has been processed by examining the properties of the TachyonExperience cube:


1E Client
Ensure that 1E Client data has been received, ready for processing into the cube data.

Ensure TachyonExperience tables Event, DevicePerformance, SoftwarePerformance etc have been populated. For example under SQL Management Studion run the following query on the Tachyon Experience database:

select t.Name, e.Data, t.Description from [Event] as e inner join [Topic] as t on t.Hash = e.TopicHash order by t.Name

If no Experience data is present or some missing data, then ensure that the data has been sent from the 1E Client to the Switch by examining %programdata%\1E\Client\1E.Client.log and ensuring that updates have been sent daily from the Agent to the Switch, such as:

[51384] INFO - Generating performance summary events for 2020-01-08T00:00:00.000Z
[51384] INFO - Published 1 device performance and 122 software performance summary events for 2020-01-08T00:00:00.000Z
[45296] INFO - 123 events pending for Switch transmission
[45296] INFO - Withholding 118 event(s) for subsequent Switch payloads
[45296] INFO - Sent 5 events(s) to Switch
[45296] INFO - Storing an additional 118 pending event(s) for subsequent payloads to Switch
[45296] INFO - 118 event(s) pending for subsequent payloads to Switch

If the Agent has a lot of Experience events to send to the Switch then it will be batched and trickled through to the Switch over time until none remains for transmission:

[45296] INFO - 19 events pending for Switch transmission
[45296] INFO - Withholding 12 event(s) for subsequent Switch payloads
[45296] INFO - Sent 7 events(s) to Switch
[45296] INFO - 12 event(s) pending for subsequent payloads to Switch
[45296] INFO - 12 events pending for Switch transmission
[45296] INFO - Withholding 5 event(s) for subsequent Switch payloads
[45296] INFO - Sent 7 events(s) to Switch
[45296] INFO - 5 event(s) pending for subsequent payloads to Switch
[45296] INFO - 5 events pending for Switch transmission
[45296] INFO - Sent 5 events(s) to Switch
[45296] INFO - 0 event(s) pending for subsequent payloads to Switch

Similarly, if the Switch connection disconnects whilst Experience events remain unsent to the Switch, then they are persisted until the Switch connection is re-established:

[21836] INFO  - Storing 2 events as Switch connection unavailable

<time passes>

[35436] INFO - Agent will start catch-up from instruction Seq=112
[27656] INFO - Marking current client certificate as successful
[35436] INFO - Catch-up is now complete; ready to accept live instructions
[21836] INFO - 2 events pending for Switch transmission
[21836] INFO - Sent 2 events(s) to Switch
[21836] INFO - 0 event(s) pending for subsequent payloads to Switch

If you don't see these kinds of Agent INFO log messages then ensure a policy has been sent to the Agent from the Switch, remember that you have to deploy the Event Subscriptions to the Agents by using the Deploy button in Guaranteed State even if you have no policies (you want) to deploy:

The Deploy button does not appear to be activated but it is clickable.

This will generate a policy document containing the event subscription data under %ProgramData%\1E\Tachyon\PolicyDocuments for deployment to devices:

{"Rules":[],"EventSubscriptions":[{"Topic":"Device.Performance"},{"Topic":"Software.Performance"},
{"Topic":"Device.PerformanceAnomaly"},{"Topic":"Patch.Install"},{"Topic":"Patch.Uninstall"},
{"Topic":"Software.Crash"},{"Topic":"Software.Hang"},{"Topic":"Software.Install"},
{"Topic":"Software.Uninstall"},{"Topic":"Software.PerformanceAnomaly"},
{"Topic":"Operatingsystem.Boot"},{"Topic":"OperatingSystem.Crash"},
{"Topic":"OperatingSystem.PerformanceAnomaly"},{"Topic":"OperatingSystem.ServiceFailure"},
{"Topic":"OperatingSystem.Upgrade"}]}