Adaco: Local Network Prerequisites and Troubleshooting

Overview

This article contains technical information and is intended to be used by customers' internal IT departments. Outlined below are 10 different scenarios with issues that may occur and thier solutions. 

 

Client / Local Network Prerequisites:

Operating System
Microsoft Windows 7, Windows 7 SP1, Windows 8.X or Windows 10

Microsoft .NET Version
Microsoft .NET Framework 4.7.2 (or higher)

Internet Browser
Internet Explorer 11 or above, Microsoft Edge, Google Chrome (ClickOnce required for Edge and Chrome)

Workstation RAM Requirements
Minimum 2GB free memory

Ports
HTTP (80) and HTTPS (443) open on the customer firewall(s)

SMTP (if used)
Working and tested SMTP server and credentials if used.

Bandwidth / Latency
1 MBPS+ / less than 100ms latency from client to server

Web Proxy (if applicable on customer network)
Ability to create exception for Adaco URL to bypass the proxy. The application is not supported through a proxy.

 

Common Issues and Known Resolutions:

Most errors occur during the initial download of the application for a variety of reasons. Typically, a window appears with a “Details” button. Selecting the button will open a text file that includes the error message. It is found at the end of the block with the header “ERROR SUMMARY” (e.g. + Exception from HRESULT: 0xD000000D). Some of the more common errors and solutions are listed below.

1.

Issue

The application fails to launch when the user attempts to login. Device could not be started /Application cannot be started message will appear. One of the errors below may appear in text file created when clicking “Details”.

• The referenced assembly is not installed on your system. (Exception from HRESULT: 0x800736B3)
• Value does not fall within the expected range
• An application for this deployment is already installed with a different application identity
• The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)

Resolution

• ClickOnce store corrupted for this specific user. Delete the 2.0 folder on workstation in path %userprofile%\AppData\Local\Apps

Please note: If there are any applications open that use Microsoft.net framework, you will be unable to delete the 2.0 folder. Typically, the main culprit is the Adaco Quick Launch icons in the workstation’s notification tray. Close the Quick Launch icon(s) by right-clicking on them to Exit. Attempt to delete the 2.0 folder again.

2.

Issue

Application fails to launch when the user attempts to log in using Edge browser. (see Fig.1)

Fig.1 - Failed login attempt

Resolution

• In the Edge browser, type in the following URL: edge://flags/ (see Fig.2)
• You will open Edge configuration(flags)
• Now in the search bar start typing: “ClickOnce”- the option will become visible. Choose Enabled to enable ClickOnce

Fig.2 - Edge browser

3.

Issue

Application fails to launch when the user attempts to log in using Google Chrome browser (same error as shown in Fig.1)

Resolution

• Use this link to go straight to the Google web store page for ClickOnce
• Select Add to Chrome
• Select Add extension

Fig.3 - Adding ClickOnce extension for Google Chrome

The extension will then download.

• Use the down arrow and select Open

Adaco can then be loaded from Google Chrome.

For further detail on this, please see: Adaco: Accessing Adaco using Google Chrome

4.

Issue

When using Internet Explorer 11, the login page fails to open or you receive a browser version error.

Resolution

• In IE, go to Tools > Compatibility View Settings
• Add website
• Re-launch IE browser

5.

Issue

The application fails to launch accompanied by the error ‘'Adaco.Common.Param' cannot be serialized' as shown below.

Fig.4 - 'Adaco.Common.Param' error message

Resolution

Verify Microsoft .NET framework 4.5.2 (or higher) is installed on the workstation. If already installed, the framework may be corrupt and needs to be reinstalled.

 

6.

Issue

Application fails to launch with error ‘Your Web browser settings do not allow you to run signed applications.’

Resolution

• Open Internet Explorer and go to Tools > Internet Options > Security Tab
• Either (1) add URL to the "Trusted sites" zone which should have “Run components signed with Authenticode” enabled by default or (2) click "Custom Level" for the security zone the website is currently in, then check the item "Run components signed with Authenticode".

7.

Issue

Customer receives error message similar to 'No endpoint listening at net.tcp://serveripaddress/CustomerPortal/WCFService/WCFService.svc' – ALL users cannot access application.

Resolution

Restart IIS Application Pool(s) for affected customer portal.

 

8. 

Issue

User receives error message 'Not a Valid Portable Executable Error' during initial download of Adaco application, ClickOnce fails to install after downloading few DLLs. On each subsequent attempt more DLLs are downloaded and finally everything works after 20 to 30 attempts.

Resolution

Network Packet filtering or firewall filter on customer's local network. Too many packets are dropped and ClickOnce issues too many TCP retransmit requests and then fails. When temporarily disabling the network packet analysis, the download is successful.

Customer's local IT needs to create exception in filtering software to allow information from application.

 

9.

Issue

Application download begins, but fails quickly afterwards with error message similar to: 'Exception occurred loading manifest from file DevExpress.RichEdit.v10.1.Core.dll: the manifest may not be valid or the file could not be opened.'

Resolution

Most likely there is a firewall, antivirus or packet sniffer (analyzer) on the property's network (i.e. Cymphonics, Websense). Customer's local IT needs to verify this is the situation and, if necessary add exception to the box for the application's URL and application’s public IP address / breakout IP address. Customer can try connect to Adaco from Guest WiFi network or using GSM(mobile) internet access using USB modem or WiFi HotSpot functionality.

 

10.

Issue

Error when attempting to launch application – A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. May also see below.

Fig.5 - Network-related or instance-specific error message

Resolution

Verify ports 80 and 443 are not being blocked by the firewall on the workstation. Verify antivirus not blocking application.

• Try connect to Adaco from Guest WiFi network
• Try connect over GSM (mobile) internet access using USB modem or WiFi HotSpot functionality
• Try connecting using a different Internet Service Provider (ISP)

11.

Issue

Customer reporting slowness across all aspects of Adaco application (from the initial download and including all modules within the application)

• Test connectivity to Adaco from different PC and internet network
• Try connect to Adaco from Guest WiFi network
• Try connect over GSM(mobile) internet access using USB modem or WiFi HotSpot functionality 
• Try connect using different ISP (Internet Service Provider)
• Latency
• Ping the server by both DNS name and IP address
• Look at the ping statistics. They should report a 0% loss
• Double digit values (such as 80ms, or lower) are good for the time. This varies drastically depending upon where the server is in relation to your computer. The connection should have latency less than a 100 milliseconds

If there is no network connection, you will see the output "Request timed out" repeatedly. If pinging by DNS has higher times, your network may be having issues resolving the name.

• Run Traceroute (tracert via command prompt to the server). Confirm if there’s any drops or hops exceeding 100ms. Any numbers that are more than 100ms to 200ms are considered "high" by most standards
• Bandwidth
• Go to a site such as speedtest.net. Verify your upload/download speeds meet the bandwidth requirement. Be sure to check several times; especially during your site’s busiest times for internet usage
• Confirm server is not having resource issues
• Initial troubleshooting steps below need to be taken by the customer