%11The Winsock sender cannot connect to remote site server "%2" for site "%1" over the TCP/IP.%12 Possible cause: Remote site server "%2" might not be connected to the network. Solution: Verify that site server "%2" is connected to the network and functioning properly. Possible cause: The specified server name "%2" is unrecognizable. Solution: Verify that server name "%2" is recognizable by DNS server. Possible cause: The Winsock Sender/Receiver compononents are not started on the remote server. Solution: Verify that the Winsock Sender has been created on the remote server "%2". Possible cause: Network load might be too high. Solution: Verify that the network is not saturated. Verify that you can move large amounts of data across the network.%0
The Windows server %s that is running the SQL Server is down or not on the network, or your current Windows logon ID does ...
The Windows Update Agent on client computers can be configured to create event messages for Windows Server Updates Services ...
The Winsock receiver on site server "%1" cannot create a connection for clients.%12 Possible cause: Winsock Receiver can ...
The Winsock receiver on site server "%1" cannot start.%12 Possible cause: The Winsock DLL or the TCP/IP is mising on server ...
The Winsock sender cannot connect to remote site server "%2" for site "%1" over the TCP/IP.%12 Possible cause: Remote site ...
The wizard creates a default installation folder for the tool. If you want to select a different folder, click Browse to ...
The WMI service may stop responding on Configuration Manager site systems with the .NET 2.0 framework installed. More information ...
The {0} package does not contain source files and does not require a package access account. If the package should contain ...
There are no configurable properties for this site system role. All System Health Validator points in this site share the ...