| Previous | Next |
| PEER_E_TIMEOUT | PEER_E_FW_EXCEPTION_DISABLED |
PEER_E_INVALID_ADDRESS
Which peer contract was rejected
PEER_E_INVALID_ADDRESS — HRESULT 0x80637007 marks the endpoint address supplied to the collaboration operation is malformed or incompatible with the expected peer endpoint format. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PEER_ENDPOINT structures and Peer Collaboration invite/subscription calls.
Peer Collaboration provides serverless presence, contacts, endpoint subscriptions and invitations. Its operations depend on an interactive user context, explicit sign-in scopes and firewall/privacy consent.
Minimum diagnostic packet
| Item | Evidence for it |
|---|---|
| Raw input | Preserve address family, IPv6 bytes and scope ID, port, endpoint structure version, source enumeration and serialization boundaries. |
| Owning context | Record the Windows user, process integrity, graph or group handle, database path and selected cloud. |
| Previous success | Save the last successful create, open, enumerate, parse, register or sign-in result that produced the object. |
| Result order | Retain the first HRESULT so cleanup failures do not replace the code that rejected the request. |
Focused reproduction
Use an endpoint structure returned directly by Peer Collaboration enumeration and compare with the manually reconstructed address. Use disposable identities or groups when the test publishes names, creates credentials or modifies a replicated database.
Why the comparison code is different
PEER_E_IPV6_NOT_INSTALLED differs because invalid-address rejects one endpoint value; IPv6-not-installed means the platform protocol prerequisite is absent. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Preserve IPv6 scope and address-family data, validate structure sizes and avoid converting endpoint addresses through lossy text fields. Avoid deleting every peer database, certificate store or firewall rule because broad resets erase evidence without proving the caller contract was repaired.
Proof of repair
- The original input now passes the precise check represented by this HRESULT.
- The operation reaches the intended graph, group, record, PNRP or collaboration outcome.
- Unrelated identity material, membership credentials and replicated records remain unchanged.
Technical references
- Microsoft: About the Peer Collaboration API — it uses this source for the documented peer boundary.
- Microsoft: Collaboration API functions
- Microsoft: People Near Me requirements
- Microsoft: Windows Firewall rules
Looking for a different code? Search another status or error code.