@ADC_Vanessa wrote:
I ultimately "fixed" this by adding the FQDN of all script URLs to the hosts file and pointed them all back to 127.0.0.1
This caused Windows to not be able to find the web-hosted scripts and move on. No more errors.
I am not familiar with any of this, computer dummy here so let me ask you how exactly did you accomplish this if you don't mind possibly giving some instruction on how to do this. Thanks in advance.
Bill
