Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Web Help Desk (WHD) > WHD - Knowledgebase Articles > Unable to access Web Help Desk after installing DameWare

Unable to access Web Help Desk after installing DameWare

Overview

After you integrate DameWare with Web Help Desk, you cannot access Web Help Desk.

Environment

  • All Web Help Desk versions
  • Web Help Desk is using Apache Tomcat as an http engine on port 443.
  • DameWare and Web Help Desk are installed on the same machine.
  • DameWare is using http.sys (IIS engine) on port 443.

Workaround

Perform one of the following procedures:
  • Run Web Help Desk using https on another port (such as port 444). The Web Help Desk and DameWare integration runs correctly when both products are using separate ports. 
  • Run Web Help Desk and DameWare on the same port with separate IP addresses or network interfaces.

    If you cannot start Web Help Desk due to certificate errors, generate a new certificate. See Using SSL Certificates in Web Help Desk for instructions.

  • Install DameWare and Web Help Desk on separate servers. 
Last modified

Tags

Classifications

Public