Failure to install - error -102

[missyschoenbaum]

Failed to load URL http://127.0.0.1:8000/ with error (-102). This is currently in progress.

Error 102 is a message generated by the Chrome Browser that is embedded with the ADSM application. This error happens when the browser cannot connect to the server running in the black terminal window that opens with the ADSM application.

Usually this happens because of a firewall that is blocking local connections, an aggressive virus scanner that is preventing the server from starting, or another program running on your system using the same ports as the ADSM application.

Some good troubleshooting steps are:

1. After installation, restart your computer and try running the application again
2. Try disabling your firewall and running the application
3. Try disabling your virus scanner and running the application
4. Try running the application with administrative privileges (right click on the shortcut or executable and select "Run as administrator")
   After trying these steps, please remember to re-enable your firewall and virus scanner so your system isn't vulnerable.

[BryanHurst]

I've obtained a screenshot from the reporter of this bug:

It appears that the Path in the command line is corrupt.
Our current thinking is that this is due to locale/language settings on the user's computer.

[BryanHurst]

It is confirmed that this issue is due to language/locale settings in Windows.

[BryanHurst]

To fix this, we will need to upgrade Python, Django, and rewrite the deployment mechanism.

[missyschoenbaum]

Can we put wording in the Readme that addresses the language setting. For example, ...can be installed on Windows language set = English.....
I'm not sure on the exact wording.

[missyschoenbaum]

Language looks great. Please add the Docker profile comments.

[BryanHurst]

One possible way to a working temporary solution is to use Docker to deploy international versions.

This would require that users have Docker installed.
It would not come with a Viewer application and require users to launch Chrome and navigate to http://127.0.0.1:8000 manually.

Deploying this shouldn't take more than 16 hours and does not need a separate build per locale.

[missyschoenbaum]

Just to make sure I am clear, this would be a work-around for all international users, regardless of language. There's no limitation on Docker with other languages?

[BryanHurst]

Correct, it is is workaround.

Anybody on an English (or similar, but untested) locale will still use the normal deployment.

If somebody on another locale has issues launching the program (specifically with a 102 error), then they should use the Docker image instead.

The Docker image /should/ have no issues across different locales (though the program will still run in English). However, I've never /actually/ tested for that purpose.