2 of 2 people found this helpful
This error [-10727] PINET: RPC is Non-Existent can happen under a variety of conditions such as:
- In the PI Message Log when the PI Server was starting up
- Connecting to the PI Data Archive
- Running a query on the PI Data Archive
There are many more possibilities than what are listed above, but those are the most common scenarios.
In almost all cases, this problem is caused by one or more PI Data Archive subsystems not running. Starting those subsystems will solve the issue. You can locate the subsystem(s) that is(are) not running from the Windows Service applet and start them manually. All of the subsystem names start with PI (which makes them easy to find). Pay attention to any errors that occur when you try to start the subsystems. If the subsystems failed to start the first time, then they are likely to fail again for the same reason.
In some cases, the subsystem is started, but it is busy, so it has not yet sent its list of RPCs to pinetmgr. These cases are rare because subsystems should publish their RPCs to pinetmgr's table fairly soon after startup. Two notable exceptions include the PI Snapshot Subsystem (pisnapss) and the PI Archive Subsystem (piarchss) during deep queue recovery.
16915 backup was aborted may be due to disk space.
Kindly thanks for your suggestions. Our secondary server can checked current value after deep queue recovery.
It seems to work.But the backup failed again with the same error code [-16915], the disk used for backup is 10 TB and free about 8.9TB.
I think it is not disk problem.Could you give me other advice for making this issue.
Sorry for the delay. Do you still have this issue? Is the Piarchss busy during the Backup time? Please try and move the Backup Time and Restart PI Backup Subsystem. Which type of Backup do you have, INCREMENTAL or NUMARCH/CUTOFF? Please advise to change to INCREMENTAL if you have NUMARCH/CUTOFF KB01032 - PI Data Archive Backup Best Practices