| Previous | Next |
| PEER_E_CHAIN_TOO_LONG | PEER_E_CIRCULAR_CHAIN_DETECTED |
PEER_E_INVALID_TIME_PERIOD
Diagnostic boundary for PEER_E_INVALID_TIME_PERIOD
HRESULT 0x80630705 marks the validity interval supplied while creating an invitation or issuing credentials is internally inconsistent or outside the accepted range. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGroupCreateInvitation, PeerGroupIssueCredentials and FILETIME conversion, or reconstructed from cached text or another process?
- Preserve start and expiry FILETIME values, time conversion code, local/UTC assumptions, issuer credential lifetime and system clock.
- Did shutdown, deletion, sign-out, expiration or replication occur between object selection and use?
- Does the operation succeed under the controlled comparison described below?
Peer Grouping layers membership credentials, roles, record signing and encrypted connections on top of graphing and PNRP. Local open state, online connection state and authorization state are separate.
Controlled comparison
Create a short future interval using known UTC values and compare with the original interval without altering identity or roles. Keep identity, graph or group ID, cloud and user context fixed unless one of them is the tested variable.
Decision table
| Observed result | Next action for this HRESULT |
|---|---|
| The HRESULT repeats with identical captured state | Inspect the caller contract and GMC trust chain; repeated network retries add no evidence. |
The call advances to PEER_E_INVALID_RECORD_EXPIRATION | PEER_E_INVALID_RECORD_EXPIRATION differs because record expiration controls replicated data lifetime; invalid-time-period concerns invitation or credential validity. |
| The controlled run succeeds but production does not | Compare user token, database path, cloud, endpoint, certificate chain and effective firewall policy. |
Safe remediation and verification
Normalize to UTC, ensure end follows start and keep the issued credential within the issuer authority lifetime. Back up exportable identity and group configuration, and hash database or invitation artifacts before modifying them.
The repair is complete only when the intended operation succeeds and its resulting connection, record, membership, endpoint or collaboration scope can be independently enumerated.
References
- Microsoft: Grouping API functions — it uses this source for the documented peer boundary.
- Microsoft: How to connect to a peer group
- Microsoft: How group security works
- Microsoft Open Specifications: Peer-to-peer grouping overview
Looking for a different code? Search another status or error code.