| Previous | Next |
| WSASYSCALLFAILURE | WSATYPE_NOT_FOUND |
WSASERVICE_NOT_FOUND
WSASERVICE_NOT_FOUND belongs to Winsock's protocol-independent Registration and Name Resolution model. A WSALookupService* query can search one or more namespace providers using restrictions in a WSAQUERYSET; this code means the requested service could not be found in the selected namespace.
It is broader than DNS host lookup
Winsock namespaces can represent service instances and classes, not only host-to-address records. The query can restrict namespace, service class, protocols, instance name, and returned data. A valid service in one provider may be invisible when the query selects another namespace or an incompatible service class.
What to log
dwNameSpace, service class GUID, instance name, and protocol restrictions.- The lookup control flags passed to
WSALookupServiceBeginandNext. - The namespace providers installed and actually queried.
- Whether legacy
gethostbyname-style code translated this result into a host-not-found error.
Changing a TCP port cannot fix a service-discovery miss that occurs before a transport endpoint has been selected.
Microsoft: WSALookupServiceBegin · Microsoft: Winsock name resolution · Microsoft: Winsock error codes
Looking for a different code? Search another status or error code.