Date
1 - 6 of 6
PropView Sunspot Number error
|
All DXLab apps and Windows Defender are updated. Today starting ProView produced the following error:
"unable to download sunspot number from https://services.swpc.noaa.gov/json/solar-cycle/predicted-solar-cycle.json - resource not found" Navigating to the above URL (also the same in PropView configuration) appears to show some data. PropView launches OK after acknowledging the error. Is this a problem at the data source (i.e. NOAA)? -- 73, Norm/KC1BMD |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
All DXLab apps and Windows Defender are updated. Today starting ProView produced the following error:+ This could be the result of a problem at the data source, a problem with your internet service provider, a hardware or software problem with internet access from your computer, or interference from another application running on your computer. 73, Dave, AA6YQ |
|
|
|
Norm - KC1BMD
Update: I rebooted Windows 10/64 into 'Safe Mode with Networking' and the problem still persisted. Upon restarting the PC normally, the problem no longer existed although the root cause remains unknown.
-- 73, Norm/KC1BMD |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
Update: I rebooted Windows 10/64 into 'Safe Mode with Networking' and the problem still persisted. Upon restarting the PC normally, the problem no longer existed although the root cause remains unknown.+ That eliminates "interference from another application running on your compute" as the root cause. 73, Dave, AA6YQ |
|
|
|
Norm - KC1BMD
Since I could access the data using the URL either directly from a browser and also by clicking the link to go there in the PropView configuration (prediction), without any error - and - since the data source could be accessed in identical ways after the problem disappeared and appeared to look the same as before, I might conclude that it was not a hardware/software or internet service provider issue (especially since there were no other internet access issues). This would lead me to think it could have been a data source issue except that nobody else reported the problem on this site recently as far as I can tell. So I guess it shall remain just one of those mysteries.
-- 73, Norm/KC1BMD |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
Since I could access the data using the URL either directly from a browser and also by clicking the link to go there in the PropView configuration (prediction), without any error - and - since the data source could be accessed in identical ways after the problem disappeared and appeared to look the same as before, I might conclude that it was not a hardware/software or internet service provider issue (especially since there were no other internet access issues). This would lead me to think it could have been a data source issue except that nobody else reported the problem on this site recently as far as I can tell. So I guess it shall remain just one of those mysteries.+ The problem could have been transient, or quickly corrected. 73, Dave, AA6YQ |
|
|