historical trends not working

This occurred after client PC crashed due to power failure.
log data is not updating on the connectivity servers.

I have attached an error message on the client PC when selecting log data.

Please note that when the trend is set to "TRIM" real time data is updated but historical trends do not.

IMG_0438.JPG

Comments (0) New comment

ken.cottam Rank: 1172

Asked 5 months ago

Answer this question Follow

Voted best answer

Looks like something is corrupted in your installation, does it work on the server itself?
Restore an image or reinstall the client.

Comments (5) New comment

by ken.cottam Rank: 1172 on 10/23/2019 2:00:43 AM | Like (0) | Report

I have restored the client PC from an acronis backup.
Unfortunately the Log templates have been modified during this period and now no logs are being created.
I have a acronis backup of the primary/Secondary Access servers.
Would it help to restore these also?

by ken.cottam Rank: 1172 on 10/23/2019 2:15:24 AM | Like (0) | Report

Th restore of the client 1 PC did not fix the issue of the error when selecting log1 in any of the trends screens.
This above issue may of pre-existed and is may be a red herring.

backdraft

Rank: 22 on 10/23/2019 3:57:40 AM | Like (0) | Report

So, history service is running on client (??), or the logs don't work on the server as well?
Do you get any error on the server?

by ken.cottam Rank: 1172 on 10/23/2019 5:07:08 AM | Like (0) | Report

The history service is running on the connectivity servers. In the C:\OperateITdata\History\RandomGUIDfolder only two files are created updateStorage.dat and SyncFile.dat. On PRICS are 1KB and 210KB and on secondary both are OKB.
No logs are getting created on either conectivity servers.

backdraft

Rank: 22 on 10/23/2019 1:05:05 PM | Like (0) | Report

ok, but the error "Failed to create ASO for History Source", does it happen on Server as well? Is there a History Source Aspect and linked to the Service? Can you open/create/configure Log Configuration Aspects on the Server? If this all works maybe Log Template is corrupt or some other issue on the Server but I fail to see any relation to the Client Computer Power Fail for this case...

Add new comment

backdraft

Rank: 22

Answered 5 months ago

Answers

Problems are resolved. It turns out that the history source had been corrupted.
Deleted source and created and configured a new History source, after this we had to restart the Basic History services on both connectivity servers.
Once we did this the log files were populated and updating and trends working as normal.

With Regard to the client PC issue, this was rectified by restoring from an image as the system was corrupted.
The client PC is now functioning normally, trends etc.

Thanks backdraft for your help.

Comments (0) New comment

ken.cottam Rank: 1172

Answered 5 months ago

Question details

historical trends not working

Voted best answer

Answers

Other questions needing answers

Related topics

AKS experts