I am getting this error when I try to delete or to create a tag. Do you have any idea? I have stopped and started the server, and it doesn't work. I have installed the server in my local machine.
Unfortunately. since there is nothing that we could troubleshoot, I cannot give you a final solution. It would only be a hypothesis.
Since the version that you have installed is 3.4.390.16, the known issue 16408OSI8 does not apply.
If the issue occurs again, after the new installation, it would be very interesting to have a look at it.
Check to see if your PI license is expired. I usually see this error when my dev or temp license has expired.
Thank s Lonnie. The license is ok. Pi was working ok until yesterday, and suddenly I started getting this message .
I would just give tech support a call. It looks like some issue with your system that they should be able to pin-point.
Thanks Lonnie. Something was wrong with the Pi server. I was trying creating a huge amount of tags, and the action was not successful. After this action, I started getting the message and I couldn't update, delete tags, access the archive. etc I tried several suggestions that I found online, but no one worked. I decided reinstall pi server and after that, all was ok. Maybe there is a better solution, but in my case it was easier to do that. It is a local installation for testing purposes only. Yes, call the tech support is a good idea. Thanks for comment my question
When PI update manager is not working properly or not responsive to the client you will see this error (Ref: PI system management guide 3.4.380).Normally Interfaces and PI clients make connection with PI updmgr for notifications of changes in data values, point attributes,modules.
If the connection is not established you can see error "Failed to retrieve events from server. [-10727] PINET: RPC is Non-Existent".
The connection statistics can be viewed in PI SMT under Operatrions>>update manager.
Thanks Balamuruga. I checked the connection statistics, but I didn't find anything that help me to know more details about the problem.
As Lonnie Bowling well suggested it would be advisable to contact with Techsupport in order to have the issue looked at. Would you like me to transfer this thread to a Techsupport case?
As also Balamurugan Veldurai commented this error could be related with network issue but there could be other reasons.
In order to troubleshoot this issue it would be advisable to have a look at the PI Message Logs, Event logs and do further troubleshooting.
Thanks Carlos. I checked the logs. I didn't find anything the help me to understand the problem (maybe I didn 't look very well). I didn't know what the error was, but I reinstalled the Pi server, and it started working again without any problems. The installation is a local one. It would be good to ask Techsupport about this problem. It has to be a better solution that reintall Pi server. This error started when I tried to create a huge amount of tags, and the action failed. I lost all the logs when I reinstalled.
There are several facts that can influence in the error that you were having, and that needed troubleshooting. It is very hard to troubleshoot without any logs and having reinstalled the PI Data Archive.
My best guess would be the following:
16408OSI8 - Archive Subsystem may hang and get disconnected from PInetmgr ( 16408OSI8 - Archive Subsystem may hang and get disconnected from PInetmgr ) Description:
Upon very high levels of stress that include lots of archive update signups (e.g. ACE, RtWebParts), intensive point creations, and high rates of archive queries, the Archive Subsystem may hang for several minutes. If the subsystem stays unresponsive, Network Manager may decide to terminate its connection. This would result in [-10727] "PINET: RPC is Non-Existent" errors from client applications that attempt to talk to the Archive Subsystem.
This was fixed in version PI Data Archive 3.4.375.80
Which version of PI Data Archive are you using?
Version 3.4.390.16. 32bit Yes, I guess the error was related with 16408OSI8 - Archive Subsystem may hang and get disconnected from PInetmgr ,
but I am not sure if there another solution to this issue.
That's right! Sure! Thanks.
Retrieving data ...