PICOLLECTIVE or PISERVER table status values

0

Success

-10407

No Access - Secure Object

Primary and secondary certificates are not properly configured. Run the Fix certificate issues utility in Collective Manager. If you can not run Collective Manager, run piartool -registerhacert -u on the primary, then on one the secondary.

-10420

Direct write operations disallowed on secondary server of collective

Cannot change configuration on secondary.

-10773

No certificate is available on the server for TLS authentication

Primary and secondary certificates are not properly configured, or are missing from the OSIsoft LLC Certificates store. Ensure that all servers in the collective are upgraded to version PI Data Archive 2017.

If there is no certificate in the OSIsoft LLC Certificates store, re-generate or import one.

To generate a new certificate, use New-SelfSignedCertificate command in PowerShell 5.0 or later, or the Microsoft MakeCert tool. Afterwards, run the Fix Certificate Issues option in Collective Manager to register the certificate. If you cannot run Collective Manager, run piartool -registerhacert -u on the primary, then on the secondary.

To import a custom certificate, use Import Certificate option in PI Collective Manager.

-10774

No certificate found matching the specified parameters

No matching certificate for this server exists in the "OSIsoft LLC Certificates" store. Generate or import a certificate.

To generate a new certificate, use New-SelfSignedCertificate command in PowerShell 5.0 or later, or the Microsoft MakeCert tool. Afterwards, run the Fix Certificate Issues option in Collective Manager to register the certificate. If you cannot run Collective Manager, run piartool -registerhacert -u on the primary, then on the secondary.

To import a custom certificate, use Import Certificate option in PI Collective Manager.

-16030

Batch database access disabled on secondary server of PI collective

The Batch database on the secondary server does not have batches unless archives are moved.

-18000

Server has not communicated its status

The primary server never connected to this secondary.

-18001

Unable to process further change records; missing update in sequence

Change record sequence error.

-18002

Error processing update

Change record processing error.

-18003

No producer found on the primary server

The primary server cannot register with PI Update Manager to produce change records

-18005

Server misconfigured; no local server defined

The server cannot find its own host name in table.

-18006

Server misconfigured; no primary server defined

The server cannot find the primary server in table.

-18007

Unable to connect to primary server

The primary server is not reachable.

-18008

Unable to sign up for changes on the primary server

The primary server is not responding.

-18009

Unable to unregister for changes on the primary server

The primary server does not acknowledge request.

-18010

Unable to disconnect from the primary server

The primary server does not acknowledge disconnect.

-18011

Server misconfigured; collective not found

The server cannot find the collective name.

-18012

Invalid role defined for this server

The server role is not valid.

-18013

Member server is in error

The collective status shows this when a server is in error.

-18014

Error reading change record from the primary server

Error reading status information from the primary server.

-18015

Unable to send updates to secondary servers

The primary server is unable to send configuration changes to the secondary servers.

-18016

Unable to send status update to the primary server

The secondary server is unable to send a status update to the primary server.

-18017

Unable to get change records from the primary server

The secondary server is unable to get configuration changes from the primary.

-18018

Server has not communicated

The secondary server has not communicated to the primary server within the designated CommFailureGracePeriod and will be marked unavailable.

-18019

Member has been removed from the PI Sys Database

A status indicating that the server has been marked for deletion from the collective.

-18020

Member clock as drifted too far from the primary's clock

The secondary server's system clock has drifted too far from the primary server's clock, as defined by ClockDiffLimit. Replication temporarily halted.

-18021

Failed to enable replication

Unable to enable replication.

-18022

Server has failed to remain synchronized

The secondary server has failed to keep in sync past the designated SyncFailureGracePeriod and will be marked unavailable. By default, this grace period is disabled.

-18023

Unable to save unprocessed configuration changes to disk

The secondary server was unable to save its unprocessed change records to disk.

-18024

Unable to load unprocessed configuration changes from disk

The secondary server could not read unprocessed configuration changes from disk.

-18025

Server is not a member of a collective

The server is a standalone server and is not part of a collective.

-18026

Promotion is not supported on the primary server

Promotion of another server is not supported on the primary server.

-18027

Server is not ready to process change records

The secondary server is not ready to process changes. This usually indicates that one of the core subsystems is not running.

-18028

Unable to sign up all secondary servers to receive configuration changes

The primary server is unable to sign up every secondary server to receive configuration change records, potentially breaking replication with that secondary.

-18029

Unable to sign up all secondary servers to receive configuration changes

Attempted to set an attribute specific to replication for a non-replicating server.

-18030

Name cannot contain spaces or other invalid characters

Server name contains invalid characters.

-18031

Localhost is not a valid name

Server name cannot be "localhost."

-18032

FQDN is invalid

FQDN must contain only letters, numbers, dashes, underscores, and dots.

-18033

Two servers have the same FQDN or they resolve to the same IP address

Two server's FQDNs resolve to the same IP address.

-18034

Unable to produce update for secondary servers

The primary server is unable to send a change to the secondary servers.

-18035

Error reading update

The secondary server cannot read configuration changes sent by the primary server.

-18036

Unable to rename the current server

The current server cannot be renamed while running.

-18037

Unable to rename a server while it's online

Renaming a server is not supported while that server is marked available.

-18038

Unable to remove the current server

The secondary server must be upgraded to be able to continue processing configuration changes coming from the primary server.

-18039

Unable to remove an server while it's online

Removing a server is not supported while that server is marked available.

-18040

Unsupported replication change record version; upgrade may be required

The secondary server must be upgraded to be able to continue processing configuration changes from the primary server.

-18041

Two servers have the same server ID

The collective reports this error if two servers have the same server ID.

-18045

License has expired

A server reports this error and becomes unavailable if its license expires.

-18046

Unable to resolve the FQDN

A server's FQDN cannot be resolved.

-18047

Unable to resolve the IP Address

A server's IP address cannot be resolved.

-18048

Unable to remove collective

The collective cannot be removed from the Data Archive table while the server is running as a member of that collective.

-18049

Unable to get change records from the primary server

The secondary server cannot read configuration changes sent by the primary server.

-18050

Unable to initialize cryptography

A server reports this error if it cannot initialize the cryptographic certificate.