I am having an issue that has me at a stand still. I have new points that were added to the historical data collection.
My legacy historian is on the Application station.
I have added the points to the module in the explorer, downloaded both the Application station and Proplus continuous historians.
In the PHIST.SCR file I can see the new points in the file when I save it as a .TXT file.
I can use OPCWATCHIT to read the parameter and the value is correct (I have a signal generator writting to the parameter for testing).
In process history I am connected to the application station as the Historical data source with a connection status as good, OPC is connected, and my events are pointed to the ProPlus (the default).
Using HDAprobe.exe I cannot connect to the DeltaV.OPCHDAsvr I get a "Failed to obtain the IOPCCommon interface Must select and OPC HDA Server ErrorCode = -214767259 (0x80004005)" When connecting to the DeltaV.OPCHDAsvr.1 the error "failed to optain the IOPCCommon interface CoCreateInstance of OPC HDA Server failed! Error Code = -2146959355 (0x80080005)"
The frsopcdv.exe service is running under the DeltaVAdmin account.
I am logged into both windows and DeltaV with the DeltaVAdmin account.
The issue is that I do not have historical data for the points added I have verified when looking Process History View that the Parameter path is an exact match to how it appears in history collection and in the PHIST.SCR. I have an old Colleague that has vastly more experience and used to work at the site take a look at it and he said "One thing I noticed is that there are two services running under DvHistorianServerHost" does anyone have experience with a similar issue or possible ideas of where else I can look to resolve the issue?
I'm not sure that you can connect to legacy historian using OPCHDA.
www3.emersonprocess.com/.../opchda_overview.htm
"The DeltaV OPC Historical Data Access (OPC HDA) server (known as the DeltaV OPC History Server) provides an OPC Foundation HDA interface to the DeltaV Continuous Historian"
DeltaV Continuous Historian refers to the Emerson continuous historian, not legacy PI historian.
In reply to Youssef.El-Bahtimy:
Thank you I kind of thought that but it was one thing someone mentioned in another post about seeing if the OPC sever was running and accessible. Thanks for responding.
In reply to wpettit@fce.com:
Some more info my PI administrator was able to force the tag intot he PI server on the application station using the PIadmin account and that point is now collecting historical data as it should. has anyone ever see an issue where the point in history collection when the continious historian is downloaded to the applications station where the associated PI server does not create the points listed in the history collection?
Thanks I have downloaded the module with no issues and then downloaded the application station continious historian again with the same results no historical data. I did read another post that you had on here and I checked the PHIST file and the reference
PHLI
{
PATH='B1200_IJB1/TE-TAM1.CV'
ENAB=T
CDEV=0.01
RATE=60
STEP=2
CONT=T
MAX=86400
}
is in the PHLI I also checked the badscanitem.log
CFIGFAIL in 60 second scan group, B1200_IJB1/TE-TAT.CV, Retry count: 494
CFIGFAIL in 60 second scan group, B1200_IJB1/TE-TAM.CV, Retry count: 494
BADREAD in 60 second scan group, B1200_IJB1/TE-TDB.CV RT_NOT_CONFIGURED
CFIGFAIL in 60 second scan group, B1200_IJB1/TE-TAM1.CV, Retry count: 496
my test point TE-TAM1.CV appears in the badscanitem.log file can you please expand upon what would cause the CFIGFAIL and if that would prevent collection of historical data that I am seeing. Thank you.
Can you read the value using Watchit from the Application station? Let's make sure peer-to-peer comms between the App station and the controller are made.
yes I can pull up opcwatchit and read my test tag (TE-TAM1.CV) value and see it moving (I connected it to a signal generator with a sign waveform) on the application station but I did have to log in to deltaV as deltavadmin it would not let me connect to the OPC.deltaV.1 using the administrator login.
Are any of your historical data points assigned working? I assume from your badscanitems file that only a few of the tags are not being historized, but perhaps you only have the tags listed there assigned?
Take a look at the DVPI.log file in dvdata.
Have you tried removing historical collection from the tags, download the historian, add historical collection, download the historian again (i.e. reset)?
I wanted to say thank you for all your help Youssef and now the answer that we finally found. I called in our PI administrator for the corporate PI server again. All she had to do was change the PIadmin and DeltaVAdmin (both the PI user accounts) to the same password that was used when we synchronized all the passwords using ServPwd.exe. It appears that the legacy PI historian passwords are not updated with the Servpwrd.exe and have to seperately be change. With out this the history collection when when downloading did not have the correct credentials to write the tags to the PI server. This resulted in bad writes in the badscanitem.log file and that information lead our PI administrator to check the credentials as well as some items in the DVPI.log. Below is how she did it should someone else ever find this and need it.
PI: administrator: I have been troubleshooting the deltav HMI again. This time I got instruction to change the password for DeltaVAdmin and piadmin userids on the local deltav PI server right on the HMI to force the password to match the password that Bill changed for the DeltaVAdmin windows login. The password has to be consistent so each component on the deltav HMI will work when logging in with one userid. I restarted the local deltav PI server and the new IJB points are on the local deltav PI server now. Also, these points now exist on the corporate PI server
Me: is that all that was done?
PI administrator: Yes. I just changed the passwords. And to change the passwords, you just go to d:\pi\adm and type pisetpass
If the old password is not known, you just put ‘!’. Then you are asked to enter the new password.
Thank you for the informative update. I don't ever recall having to adjust the piadmin settings even after changing DeltaV admin password (we are talking about the PI account, not an OS account, right?)
It sounds like you have a enterprise PI integration in addition to the local legacy PI historian. If OPC-DA, then yes, changing the DeltaVAdmin password would not update the OPC-DA PI interface credentials. If PI-to-PI then I would assume it runs under system account and should be unaffected.
yes it was the PI account that needed the password change.
It is a direct PI to PI interface between the legacy historian and the corporate PI server. Which is why when she forced the tag into the legacy historian with the PIadmin account everything for that tag started collecting correctly and was able to be displayed with historial data in process history view.
The historian verision I found out from more digging is from DeltaV 6.3 (found the old install disks in a cabinet my predessor used) which we upgraded to 8.4 and chose to keep the legacy historian for the PI to PI ease of data collection (not seeming so easy lately :-D).