| Previous | Next |
| CO_E_NOIISINTRINSICS | CO_E_DBERROR |
CO_E_NOCOOKIES
The response context cannot accept the component’s cookie update
This HRESULT means an attempt to write a cookie failed. In COM+/IIS integration, diagnosis belongs at the HTTP response and ASP intrinsic boundary rather than at generic COM class activation.
The documented description is “An attempt to write a cookie failed.”.
Relevant contract
The failure concerns writing the cookie through the current request/response context. It does not prove that the client rejected a delivered cookie because the write can fail before any header is sent.
Causes that fit this specific result
- The response headers are already committed when the component attempts to add or modify a cookie.
- No valid IIS intrinsic response object is available on the current execution path.
- The cookie name, value, domain, path, or size violates the hosting layer’s rules.
- Asynchronous work tries to write after the request has completed or moved to another context.
Evidence to preserve before changing the system
- Record cookie name and attributes while redacting the value or security token.
- Capture whether response headers were sent and the lifecycle stage of the IIS request.
- Log request ID, application pool, component context ID, and the exact intrinsic API used.
- Check preceding response or exception events that may have committed output early.
Diagnostic sequence
- Move cookie creation before body output and before the response is finalized.
- Validate cookie syntax, length, SameSite, Secure, domain, and path against the application policy.
- Keep response mutation on the original request thread and lifecycle.
- Return explicit data from business components so the web adapter performs the cookie write.
Retry and recovery
Correct the response order or cookie attributes and issue a new HTTP response. Retrying after headers are already committed cannot amend that response.
What the result does not establish
The HRESULT does not prove browser-side blocking, third-party-cookie policy, or later expiration. It identifies the server-side write attempt.
Difference from nearby HRESULT values
CO_E_NOIISINTRINSICS means the IIS intrinsic environment is unavailable more generally. HTTP status or browser diagnostics are needed for cookies successfully emitted but not stored.
Practical scenario
A component streams part of an ASP response and then attempts to set an authentication cookie. Headers are already committed, so the write fails; the authentication adapter sets the cookie before rendering begins.
Developer and telemetry guidance
Treat cookie mutation as web-boundary work. Telemetry should record header-commit state and safe cookie metadata without logging secrets or complete authentication tokens.
Official Microsoft references
Looking for a different code? Search another status or error code.