Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 10047 Source: ICABrowser
An address incompatible with the requested protocol was used.
or if viewed from a remote computer
The description for Event ID ( 10047 ) in Source ( ICABrowser ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: .
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is a DLL?
What is causing the “The description for Event ID ( … ) in Source ( …. ) cannot be found… “?
This is old info from the WinFrame days but it may still be relevant:
WSAEAFNOSUPPORT (10047) Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated "address family" (i.e., AF_INET for Internet protocols) and a generic protocol type (i.e., SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket() call or if an address of the wrong family is used for a socket; e.g., in sendto().
Document ID: CTX182496
This solution pertains to:
· WinFrame 1.7
· WinFrame 1.8
Shadowing in WinFrame works using internal NetBIOS calls. Without the NetBIOS interface installed under the network icon, the shadowed user will get a popup that there is a request to shadow him/her " if applicable ". " This is not a function of NetBIOS, it is merely the WinFrame message utility." When the user replies to the request (if applicable), the shadowing user receives the message:
WinStation (IDx) shadow failed. (Error 10047 - (no error text available). To resolve this, install the NetBIOS interface under the Network Icon.
WSAEAFNOSUPPORT 10047 Address family not supported by protocol family. The ICA browser is may be having trouble making a UDP connection with a client or server. Check for the following:
- UDP/broadcast blocking between server groups in a subnet
- Invalid ICA Gateway entries
Regarding bad ICA Gateways, run a network trace in the afflicted environment and check for entries that indicate that servers are attempting contact other computers and receiving the response "Unreachable Port Number". Also, check the following registry key on each server with an ICA Browser service:
and look for configured ICA gateways pointing to unreachable addresses.
|Private comment: Subscribers only. See example of private comment|
|Links: How to Set up the ICA Browser Log|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated