Tips When Browsing the Website or Web Application URL

• Run the consistency check on web application on Client/FEP SMC and see the log for troubleshooting.
• If you change the website/web application certificate using SMC, then you must re-install the updated website/web application certificates in the appropriate Windows Certificate store on the system where you are launching the Windows App Clients.
• If a SMC-created host certificate is used for signing the web application and the Internet Explorer browser is configured to check the publisher's certificate revocation, the Security Warning message may display, even after installing the certificate.
• Add the website to the Trusted Sites zone from Tools > Internet Options > Security to resolve the issue.
• Ignore the warning and click Install (for Windows App client).
• If self-signed is configured in web application, then it is recommended to configure trusted certificates for more security.
• When browsing for a web application, if you receive an error message, you can always check the log file located at [Installation drive]:\[Installation folder]\Websites\[Website name]\GMSWebSite\Log. This is the same path that you configure in Details expander during website creation or modification.
• If you launch a Windows App Client using a web application URL linked to a stopped project or if no project is linked, the Windows App Client fails to connect. In this case of a stopped project, you must start the project and re-launch the Windows App Client using the web application. In case of where no project is linked, you must edit the web application and link a project.
• If you launch a Windows App client using a web application URL and cannot save an object (for example, a graphic), while working with the Windows App Client, or if you browse a website URL, you may need to repair the .Net. Refer to repair the .NET Framework 4.0.30319 version at a command prompt.
• Transferring files between Windows App clients and the web server (IIS) is a potential security risk. Communication between the Windows App clients and the Server (IIS) is restricted and only allows you to transfer file types that are supported by Desigo CC for each writable directory of the web server.
  File types that are not supported are not transferred, and IIS responds with an HTTP 404 error. Depending on the workflow, this error is reported to the operator at the client or is added to the log file on the Server. (See File transfer between Web Server (IIS) and Windows App Client)
• It is recommended to create a new certificate if the machine name is changed, each machine name must have a unique certificate, you can import and set the certificates as default.