Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare Documentation > DameWare Remote Support and Mini Remote Control Documentation - Previous Versions > DameWare Remote Support User Guide > Troubleshoot common errors > System Error 1219

System Error 1219

Table of contents
Created by Anthony.Rinaldi_ret, last modified by Anthony.Rinaldi_ret on Jul 12, 2016

Views: 427 Votes: 0 Revisions: 2

System Message: The credentials supplied conflict with an existing set of credentials.

This is not an error directly related to DameWare software and it can be duplicated in other contexts. The most common reason for this error is that you already have a connection to the remote system using a different set of credentials.


To begin troubleshooting, click Disconnect Network Connections in the main Remote Support toolbar to both display all connections, and then disconnect any connection(s) to the system generating the error. After you disconnect the connection(s), try to re-connect to the system with credentials that have adequate rights to do the job.

If that does not work, or there are not open connections with the remote system, reboot the local system.

Finally, if these two steps fail, make sure you do not have a duplicate user ID on the source and destination systems that utilize a different password. In this case, change the passwords so they are identical on both systems, or change the user IDs so they are different.

For additional information about this error, see this Microsoft KB article.

Last modified
15:19, 12 Jul 2016