Windows Web Services Return Values
The following codes are commonly returned by the Windows Web Services API:
| Symbolic | Code | Description |
|---|---|---|
| CERT_E_CN_NO_MATCH | 0x800B010F | The common name of the certificate does not match the value specified by the application. |
| CERT_E_EXPIRED | 0x800B0101 | The certificate has either expired or is not yet valid. |
| CERT_E_UNTRUSTEDROOT | 0x800B0109 | The certificate chain of the certificate was processed, but it terminated in a root certificate that is not trusted. |
| CERT_E_WRONG_USAGE | 0x800B0110 | The certificate is not valid for the requested usage, such as a server using a client certificate. |
| CRYPT_E_REVOCATION_OFFLINE | 0x80092013 | The certificate could not be checked for revocation because the certificate revocation list could not be reached. |
| E_INVALIDARG | 0x8007000E | One or more arguments are invalid. |
| E_OUTOFMEMORY | 0x80070057 | Insufficient memory. |
| WS_E_ADDRESS_IN_USE | 0x804d000b | The address specified is already in use by the same process or another process on the same machine. This error code is also be returned when there are no more addresses available. |
| WS_E_ADDRESS_NOT_AVAILABLE | 0x804d000c | The specified address cannot be used on the particular machine. |
| WS_E_ENDPOINT_ACCESS_DENIED | 0x804d0005 | The remote endpoint indicates that access was denied. This error will only be returned if the remote endpoint indicated this failure. |
| WS_E_ENDPOINT_ACTION_NOT_SUPPORTED | 0x804d0011 | The remote endpoint indicates that the specified action is not supported. This is usually an indication of a mismatch in contract. This error will only be returned if the remote endpoint indicated this failure. |
| WS_E_ENDPOINT_DISCONNECTED | 0x804d0014 | A connection existed with the remote endpoint, but it was actively terminated by the remote endpoint, or there was a lack of connectivity with remote endpoint. |
| WS_E_ENDPOINT_FAILURE | 0x804d000f | General endpoint failures. This error will only be returned if the endpoint actually responded with an error indicating it could not process the request. |
| WS_E_ENDPOINT_FAULT_RECEIVED | 0x804d0013 | A message containing a fault was received, but a different message was expected. The actual fault information can be obtained from the error object using WS_FAULT_ERROR_PROPERTY_FAULT . |
| WS_E_ENDPOINT_NOT_AVAILABLE | 0x804d000e | The endpoint is no longer in service at this location, or is temporarily out of service. This error will only be returned if software on the remote machine indicated this failure. |
| WS_E_ENDPOINT_NOT_FOUND | 0x804d000d | The endpoint cannot be found, for example, if the host can be found, or there is not an endpoint listening at the particular URI. |
| WS_E_ENDPOINT_TOO_BUSY | 0x804d0012 | The remote endpoint indicates that the endpoint or the server the endpoint is hosted on is too busy to process the request. Although this is typically an indicator of an overloaded server, this error may also be returned when the endpoint or server is temporarily unavailable for other reasons. |
| WS_E_ENDPOINT_UNREACHABLE | 0x804d0010 | There is no route or network connectivity to the endpoint. |
| WS_E_INVALID_ENDPOINT_URL | 0x803D0020 | This error is returned when the endpoint address URL is invalid for the current operation. |
| WS_E_INVALID_FORMAT | 0x804d0000 | The data being interpreted did not meet the expectations of the code that was interpreting it. This error code is used for any sort of mismatch between expectations and what was actually found: invalid XML, invalid wire protocol, incorrect format, XML not matching expected schema, etc. It is unlikely that retrying the operation will succeed. |
| WS_E_INVALID_OPERATION | 0x804d0003 | The operation may be a valid operation for the object, however, the object is currently in a state where the operation is not allowed. |
| WS_E_NO_TRANSLATION_AVAILABLE | 0x804d0009 | The language-sensitive information such a localized error string or fault string is not available in the specified language. |
| WS_E_NOT_SUPPORTED | 0x804d0017 | A feature has been requested that is supported on some platforms but not the current one. |
| WS_E_NUMERIC_OVERFLOW | 0x804d0002 | The numeric operation would result in overflow due to lack precision of the values specified. An example of this is when adding two 32-bit integer values where the value would wrap around. |
| WS_E_OBJECT_FAULTED | 0x804d0001 | A new operation is starting for an object that has faulted due to a previous unrecoverable error. |
| WS_E_OPERATION_ABANDONED | 0x804d0007 | An operation was pending but was subsequently abandoned. An abandoned operation will still continue executing, however, the caller will be signaled that it has ended with this error code. |
| WS_E_OPERATION_ABORTED | 0x804d0004 | An operation was started on an object and has been aborted, or an operation was pending, but the object was aborted. |
| WS_E_OPERATION_TIMED_OUT | 0x804d0006 | An operation did not complete with the specified timeout. The timeouts for operations are specified using properties of the object. |
| WS_E_OTHER | 0x803D0021 | This error is returned when an unrecognized error occurred in one of the platform components that Windows Web Services framework uses. An application can obtain the actual error code from the error object, but must not depend on the particular value since it may change in future versions. |
| WS_E_PROXY_ACCESS_DENIED | 0x803D0016 | This error is returned when the HTTP proxy server reports access denied. |
| WS_E_PROXY_FAILURE | 0x803D0015 | This error is returned when some part of HTTP proxy server processing fails. |
| WS_E_PROXY_REQUIRES_BASIC_AUTH | 0x803D0018 | This error is returned when the HTTP proxy server did not accept the HTTP header authentication scheme chosen by the client and instead requires basic authentication. |
| WS_E_PROXY_REQUIRES_DIGEST_AUTH | 0x803D0019 | This error is returned when the HTTP proxy server did not accept the HTTP header authentication scheme chosen by the client and instead requires digest authentication. |
| WS_E_PROXY_REQUIRES_NEGOTIATE_AUTH | 0x803D001B | This error is returned when the HTTP proxy server did not accept the HTTP header authentication scheme chosen by the client and instead requires negotiate authentication. |
| WS_E_PROXY_REQUIRES_NTLM_AUTH | 0x803D001A | This error is returned when the HTTP proxy server did not accept the HTTP header authentication scheme chosen by the client and instead requires NTLM authentication. |
| WS_E_QUOTA_EXCEEDED | 0x803d0008 | The limits of the object would be exceeded in completing the operation. Many objects have different limits some of which may be configurable. |
| WS_E_SECURITY_SYSTEM_FAILURE | 0x803D0023 | This error is returned when a security operation failed in the one of the security platform components that the Windows Web Services framework uses. |
| WS_E_SECURITY_TOKEN_EXPIRED | 0x803D0022 | This error is returned when the server rejected a security token because the token lifetime has expired. Depending on server's configuration, the token may be renewable or could be requested again. |
| WS_E_SECURITY_VERIFICATION_FAILURE | 0x804d000a | The data was in the correct format but could not be verified or trusted for some reason. This error is returned when interpreting the security information that has been received from a remote endpoint. |
| WS_E_SERVER_REQUIRES_BASIC_AUTH | 0x803D001C | This error is returned when the remote endpoint did not accept the HTTP header authentication scheme chosen by the client and instead requires basic authentication. |
| WS_E_SERVER_REQUIRES_DIGEST_AUTH | 0x803D001D | This error is returned when the remote endpoint did not accept the HTTP header authentication scheme chosen by the client and instead requires digest authentication. |
| WS_E_SERVER_REQUIRES_NEGOTIATE_AUTH | 0x803D001F | This error is returned when the remote endpoint did not accept the HTTP header authentication scheme chosen by the client and instead requires negotiate authentication. |
| WS_E_SERVER_REQUIRES_NTLM_AUTH | 0x803D001E | This error is returned when the remote endpoint did not accept the HTTP header authentication scheme chosen by the client and instead requires NTLM authentication. |
| WS_S_ASYNC | 0x4d0000 | A function is completing asynchronously. |
| WS_S_END | 0x4d0001 | The end of input has been reached. This is returned when there are no more messages available on a channel. No more messages are available if the channel is of type WS_CHANNEL_TYPE_REPLY and has already received a message, if the session was shut down, or if the channel filtered the message. For more information, see Channel Layer Overview . |
| 45 entries | ||
Article text from the Win32 documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.