As per Microsoft: "A server connection was lost while the server was attempting to perform a remote procedure call. It is unknown whether the remote procedure call executed, or how much of it executed. The connection may have broken because of a problem with the network hardware or because a process terminated". The error is most likely a result of network problems or bugs in the application responsible for the error.
If you receive the error when connecting to a printer in the Printer Wizard, this problem usually occurs after you have set up and then deleted multiple printers, logging off and on in between removes and setups. If you see this message, click OK in the dialog box with the error message, and then log off and then back on again. When you get back on, you should be able to connect to the printer. See "Managing Printing Services with NT Server" for more details.
The following are examples of causes for this error:
- M158042 - In this case, the Spooler service has not been started or has stopped working. Restart the service to fix the problem.
- M221790 and M232476 - In this case, the server was running out of work contexts for a particular client.
- M297869 - This issue may occur if the value for the MaxTokenSize value for Kerberos is set too high. Typically, this issue occurs when 0xFFFF (hexadecimal) is specified instead of 65535 (decimal).
- M290737 - This behavior may occur if the maximum open file handle limit (2048) is reached for the virtual circuit between the Terminal Server-based server and the print server.
See Error code 1726, Error code 0x800706BF, and the other links below for more information on this error.
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.