Overview
This article provides the detail on attempting multiple connections to a server which triggers the error 1219 and how to solve it.
In these scenarios the debug logs indicate that a server is unable to open a connection to the server with the following Windows Networking error:
'1219 Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. '
The GFI EventsManager Dashboard will show the following error when this occurs collecting text log files:
'Unexpected error when connecting to machine TARGET; remote Text Logs Logs path is: \\TARGET\C$\inetpub\logs\LogFiles\W3SVC1!'
Environment
- Windows File and Printer Sharing
- Remote deployment or scanning
- All Supported Windows Environments
Root Cause
Windows networking only allows one connection to a server from a single user account. If you tried to access the server with two different user accounts from the same source server, you would get the 1219 error.
This error is documented in the following Microsoft KB article 'Error message when you use user credentials to connect to a network share from a Windows-based computer.'
Resolution
- The troubleshooting process is to determine if there other applications that may be making connections to the server using other credentials and configure them to either no longer connect or use the same credentials as used by the GFI product.
- Sometimes it is difficult to determine which process is making the connection.
- You can check by using Process Explorer (Process Explorer v16.22) and using the Find > Find Handle feature. You can then search for the IP address and the host-name of the computer to try and find any other processes with open handles to the target machine.
- Attached is a screenshot showing open handles by explorer.exe and EventsManager (esmproc.exe).
