Matti Siponen said
Hello,

When you copied the certificate chain to Historian, did you copy the entire chain including root CA certificate, possible intermediate CA certificates and the "leaf" application instance certificate to CLIENT_PKI\CA\certs folder? If you did not copy the entire chain or copied the certificates to an incorrect folder, Historian will not be able to validate them correctly when connecting to the Server.  

Yup, that did it. I wasn't thinking and put the root certs in "SERVER_PKI\CA\Certs". Once I moved them into "CLIENT_PKI\CA\Certs" and the .crl into "CLIENT_PKI\crl" it started working.

Thanks for the help!

When you copied the certificate chain to Historian, did you copy the entire chain including root CA certificate, possible intermediate CA certificates and the "leaf" application instance certificate to CLIENT_PKI\CA\certs folder? If you did not copy the entire chain or copied the certificates to an incorrect folder, Historian will not be able to validate them correctly when connecting to the Server.

When I go to connect, I am using SignAndEncrypt, Aes128_Sha256_RsaOsap (same as used on OPC UA Browser), I always receive the same error:

========================
Error:
Invalid server certificate

Status Code:
Bad_CertificateChainIncomplete (0x810D0000) "The certificate chain is incomplete."
========================

I cannot figure out what is wrong with my certificate, especially since I have the signing rootCA also trusted.

Any help would be greatly appreciated!

Unfortunately at the moment: no.

Technically some day in the future it could do the HistoryRead to the source servers, but I cannot say when or if that happens. Please contact sales@prosysopc.com if you would need this. Also I should note it is also a bit ambiguous how the data from the source server should be interpreted in a case like this, because the data is collected via MonitoredItems that do sample, thus the data obtained by Historian might not be 1:1 the data read via HistoryRead from the source (e.g. should it be "sampled" as well?). And then also should Historian query the history from before it was added as a source server? For example, in the case of our SimulationServer, that is infinite, as it just simulates the history values for any timeperiod. In a real case it could still be more than what the database can handle (e.g. disk size limitations).

As to querying the data manually, that is a bit harder. Most likely that cannot be made, not at least with normal OPC UA HistoryRead for nodes the Historian is collecting data, because the call would be ambiguous for local vs. source. Some non-standard way for this could probably be doable e.g. via a Method, but not sure if desirable.

Technically also the application's use-case at least originally was to also enhance them by adding history. If the servers already support HistoryRead, https://www.prosysopc.com/prod.....a-gateway/ would do better as it is pure aggregation and wont suffer the same ambiguity.

My question is, if there is a loss of connection between the Prosys Historian and the application's OPC UA server, can or does the Prosys Historian have a way of querying the application's history to retrieve the data historised during the period when the connection was lost?

Thanks

I still have in Prosys OPC UA Historian Configurator :
State : “Connection failed Connot connect: at index 2”.

Can you help me ?

Thanks

Knowing that the Server you're reading from is Simulation Server and that you're using a recent version of the SDK (the latest version is 4.10.2), there should be no problem with reading the source timestamps. However, now that I can see your ReadRawModifiedDetails, it seems that you're reading history from DateTime.MIN_VALUE to DateTime.currentTime(). Effectively this means that you're reading from 1.1.1601 00:00:00 UTC to now so over 400 hundred years of history. Since Simulation Server is able to generate simulated history for simulated Values such as Random, this means that there actually will be that much history available. Unless you really need to read such old Values, I would recommend testing with shorter and more recent intervals and checking if there are still errors in the source timestamps of Random.

Though, I tried to do some read some data starting from 1.1.1601 00:00:00 UTC and while there were some errors in timestamps (they were all off by fixed duration), they were not null or the minimum value. Thus the question remains, how exactly does your code output the timestamps to console and/or log?

I tried to do several readings at once using uaClient.historyRead() method.

HistoryReadDetails details = new ReadRawModifiedDetails(false, DateTime.MIN_VALUE, DateTime.currentTime(), UnsignedInteger.valueOf(DATA_BATCH_SIZE), true);
HistoryReadResult[] results = uaClient.historyRead(details, TimestampsToReturn.Source, false, ids);
ExtensionObject historyDataObject = results[0].getHistoryData();
HistoryData data = historyDataObject.decode(uaClient.getEncoderContext());
DataValue[] values = data.getDataValues();

Where are you attempting to read the history from? Prosys OPC UA Historian is a product for collecting History from Source Servers. Have you configured it to collect history from MyLevel of SampleConsoleServer or Simulation Server and then attempted to read history with your OPC UA Client via Historian's OPC UA Server? Or did you post this message on a wrong subforum and Historian is not involved in the reading process at all?

The call to read history looks correct, which suggests that there is error in either the timestamps provided by a Server or how they're processed after they've been read. Would it be possible for you to provide the code that outputs the sourceTimestamp to confirm that there are no errors there?

Also, would it be possible to use Wireshark to capture traffic between the applications and sent the logs to us so that we can check the sourceTimestamps returned by the Server? See https://www.prosysopc.com/blog.....wireshark/ for instructions on how to capture OPC UA communication with Wireshark. If you're running the applications on the same host, remember to select "Support loopback traffic" option when installing Wireshark.

You can send the code and Wireshark capture logs to uajava-support@prosysopc.com