Printer registration error

Copper Contributor

Hi all,


the universal print connector fails to register a printer every time. In found this error in the event log:


Exception when sending registration request for Drucker Zentrale
 System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
   at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
   --- End of inner exception stack trace ---
   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)
   at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context)
   at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar)
   --- End of inner exception stack trace ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at ProxyLibrary.RegisterHelper.<SendRegistrationRequest>d__9.MoveNext()
I've already checked the prerequisites:
  • License is assigned to me
  • Universal print is enabled in my tenant
  • I am global admin
  • Were using Windows Server 2016 for the connector
  • .NET is up to date


Has somebody an idea what I can do to fix this problem? 

3 Replies

@bandelj The error appears to be related to TLS 1.2. The Connector uses that as our Universal Print service requires it. It might be that the TLS 1.2 needs to be configured on this Windows Server. A few things to check, and then instructions on how to enable/verify this:


1. Is the operating system updated (as far as security patches go)?

2. Have you explicitly disabled TLS 1.2 on the server? If no, below might help


To enable TLS 1.2:

  1. Set the following registry keys:
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "DisabledByDefault"=dword:00000000 "Enabled"=dword:00000001
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001
  2. Restart the server.

 Thank you @keeron. The VM we used was very old and had some problems. Just changing the settings you named didn't help. We created a new VM and now everything is up and running :smile: 

@bandelj Thanks for the update! Glad it is working now. Hopefully the previous steps may help in future if others get stuck.