Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > Dameware Stand-alone Installation Guide > Common Dameware installation error messages

Common Dameware installation error messages

Table of contents
No headers

Updated: September 12, 2017

The following is a list of common errors encountered when installing Dameware and potential solutions to those errors. These errors are generally related to some type of system or network configuration issue within a network environment and can usually be duplicated outside of Dameware software.

Error Codes Error Potential Solutions
System Error: 5 The credentials for the remote computer were rejected The user account must have sufficient rights to log in locally to the remote computer.
System Error: 51 Windows cannot find the network path Verify that the network path is correct and the target computer is turned on.
System Error: 53 Cannot connect to the remote computer
  • Ensure that File & Network sharing is enabled and the ports are open.
  • Check that the operating system is configured for Names Resolution.
  • Enable NetBios.
System Error: 1300 Not all privileges or groups referenced are assigned to the caller This is frequently related to User Access Control or the Windows Firewall. Run the installer as an Administrator or log in to the computer with the Administrator or Domain Administer account.
System Error: 1603 A fatal error occurred during installation If you have uninstalled DameWare and try to reinstall it, you may need to remove the registry keys.
System Error: 1707 The network address is invalid This is related to the Novell Network Client. Try to connect with the host name or deploy the client agent with the MSI builder.
System Error: 1814 The specified resource name cannot be found in the image file Some or all of the operating system's Standard Performance Indexes (counters) are either missing or corrupt. See KB 300092 for more information.
Winsock Connect Error: 10050 Cannot establish a connection to the remote computer Ensure that the network is up, that you can access the remote computer, and that the firewall has not blocked the connection.
Winsock Connect Error: 10054 The connection was forcibly closed by the remote computer This can be caused if the application has stopped, the remote computer rebooted, the remote computer uses a hard close or keep-alive activity.
Winsock Connect Error: 10060 Connection timed out This may be due to a firewall configuration issue, a names resolution issue, or a network routing issue.
Winsock Connect Error: 10061 The remote computer actively refused the connection
  • Reset the TCP port on both local and remote computers.
  • Ensure that the default TCP port is the same on both local and remote computers. 
  • Ensure that no other program is using the TCP port.
Winsock Connect Error: 11001 Host not found The host name could not be found in the database query. Check that you can access the host with the name or use the IP address.
Winsock Connect Error: 11004 Could not resolve the host name Check your DNS table or use the IP address instead.

For more information on common errors, see KB 300005.

Last modified

Tags

Classifications

Public