- This topic has 8 replies, 2 voices, and was last updated 3 years, 4 months ago by Rui Bras.
October 14, 2016 at 9:21 am #2492RicardoGuest
When I try to run a script I get “Failed to load URL://…” with error (ERR_CONNECTION_CLOSED).October 14, 2016 at 11:09 am #2493EveryStep SupportModerator
There are no any known compatibility issues with Windows 10.
Could you please send us script to firstname.lastname@example.org for a review?
Kind regards.October 14, 2016 at 11:34 am #2494RicardoGuest
Just a basic Script:
October 14, 2016 at 11:35 am #2495RicardoGuestOctober 14, 2016 at 12:10 pm #2496EveryStep SupportModerator
There can be several possible reasons for that:
1). You have some kind of proxy which fails to automatically detect.
To set it manually click at the wrench icon at top-right and select “Internet options” menu.
2) Some security setting prevent user created for “Every step” to connect to the Internet.
For fixing that we’d advise stopping a “Secondary logon” service and deleting an “Everystep” user. Upon relaunch of the recording tool you’ll need to decline creating a user and starting a service.
That might resolve the issue.
Kind regards.December 23, 2016 at 1:06 pm #2517Rui BrasGuest
I have this same problem with EveryStep v4.0.6114.8857
on MS Windows v10 Pro enUS (build 14393-rs1_release-inmarket.161208-2252).
I managed to create a script and tested it inside the Scripting Tool
about one month ago. But never could run it inside the Player,
even after 3 complete re-installations.
The thing is, there’s no proxy or access problems, every check I do
(default using http://cnn.com and other sites) is OK, except for the URL
I’m trying to test (public access to one of our services on AWS):
Making SV request to https://sinergie.misy.eu/
Making UV request to https://sinergie.misy.eu/
The underlying connection was closed: An unexpected error occurred on a send.
What is this UV (?) request and what are the differences for a SV (?) one?
This error is “Type 205 – error code 12500 – An unexpected error occurred on a send”
(https://www.dotcom-monitor.com/wiki/alerts/error-codes). What does this mean exactly?
Our servers never do that on every browser I have in this machine (all the must
recent versions of MS Edge, MS IE v11, Mozilla Firefox (v50.1.0) and Google Chrome (v55.0.2883.87 m)).December 26, 2016 at 4:39 am #2518AlexanderGuest
Upon checking on our end we haven’t encountered any issues with https://sinergie.misy.eu/ URL. We were able to create UserView script and play it without issues in both: EveryStep Scripting Tool and EveryStep Player.
You can check this article for differences between SV and UV platforms:
Try to perform the following actions on your end with logs enabled and under your user:
1) To enable logging in EveryStep Scripting Tool: exit the Scripting Tool,
create “C:\Users\<YOUR USER NAME>\AppData\Roaming\Dotcom-Monitor\Logs\” folder.
2) Stop a “Secondary logon” service or delete an “EveryStepScripting” user. Upon relaunch of the Scripting Tool you should decline creating a user and starting a service. This will allow to run Scripting Tool under your user privileges.
3) Create a script from scratch, play it at least one time inside Scripting Tool and save it on disk locally.
4) Click down arrow to the right of “start playing” button inside Scripting Tool and click “play in loop”. Then press “Start” in window that appeared (enter Alert Email if necessary).
Please let us know about issues at specific step, if any. Zip log files under “C:\Users\<YOUR USER NAME>\AppData\Roaming\Dotcom-Monitor\Logs\” folder and send them to email@example.com address.January 11, 2017 at 3:18 pm #2522Rui BrasGuest
Thanks for your answer. I’ve followed your instructions and the connection continues to fail with strange SSL errors. I’ve sent you the logs in a separate message to your support email. It seems that the tool needs to access certificates in my user’s Certificate Store (?!) in order to do the SSL handshake… Please advise. Thanks.January 11, 2017 at 3:27 pm #2523Rui BrasGuest
Thanks for your answer. I’ve followed your instructions and generate the logs (sent to your support email as advised) as the connection continues to fail due to strange SSL errors in the initial handshake. It seems that the tool needs to access my local Certificate Store (why?). Should I prepare a personal/company certificate to use the SSL connection? Please advise. Thanks.