Hi,
I have an issue with piputval and piputvalx in MS excel VBA.
Fyi, I'm using MS Excel 2016 64 bit.
When I tried to use the sample file piexam64.xls in ...\PIPC\Excel only digital and string points that succesfully written in the PI archive, while all numeric data's were failed.
Is there any additional setup that I need to be done for this issue?
Thanks,
Rochim.
Hello Taufiqur,
One thing to consider is the PI Point security. You need to make sure your account has write access to PI Points.
The first thing to verify is with which credentials you are connected. PI SMT -> Operation -> Network Manager Statistics can be used for verification. The first thing to look out for is the application. If you see multiple connections from PI DataLink, you could look up your clients IP address in the PeerAddress column. Scroll to the right hand side and note the value in the Identity Column. You usually see multiple identities e.g. 'Operators | PI World'. PI World reflects the minimum access level and usually provides read access. So other identities showing may provide you write access.
Now you could use PI SMT -> Points -> Point Builder to verify if one of the identities would allow yo to write.
Another common problem is that even with write access, writes fail due to the PI Point being locked by a PI Buffer Subsystem instance. Interfaces nodes are usually have PI Buffer Subsystem set up and running to avoid any data loss in case connection loss. If a PI System infrastructure consists of redundant PI Data Archive nodes, those are also referred to as PI Collective. In such an environment, PI Buffer Subsystem also fulfills the task of fanning data to all Collective members. The PI Services on each member of a PI Collective run independently - with a few exceptions. PI Snapshot and PI Archive Subsystem on a Collective member do not communicate with their pendants on other member nodes. This theoretically introduces the chance that compression is applied differently. To avoid a PI Point on one Collective member has different data archived compared to another member, PI Buffer Subsystem send compressed events with a corresponding marker and this operation requires an exclusive lock on the PI Point.
The error usually logged when the write fails due to the point being locked y a PI Buffer Subsystem instance is
"[-11414] Buffered point does not accept new events"
This brings us to how you could troubleshoot your issue or with other words, figure out what specific problem you are facing. The first thing to check is the local PI Message Log, the PI Message Log on your PI DataLink host. Pigetmsg.exe can be used to continuously print messages to a commend prompt and you could also redirect the output to a file.
Open a commend prompt
Change to the PIHOME (cd %pihome%)
Change to the adm subfolder (cd adm)
Use pigetmsg -f to continuously query PI Message Log.
Use pigetmsg -f > c:\Temp\pimessagelog.txt to dump messages to a text file.
[Strg] + can be used to interrupt / stop the session.
It may be necessary to also check the PI Message Log on the PI Data Archive (in a PI Collective environment, the Primary). This works similar to what's described above except, the environment variable to refer is %piserver% instead of %pihome%.
