LoadCurrentVantageData_V Error with New Computer
Posted: Sun 13 Sep 2015 10:26 pm
Hi All:
I've used Cumulus along with my Vue/Data Logger for years on an older Windows 7 desktop without issue. I've recently migrated to a new Dell Optiplex 790 desktop running Windows 7 (and now Windows 10), but I've noticed Cumulus will report errors on the console periodically and data reception will stop. The problem is sporadic - sometimes I'll go a 2-3 days without an issue, and others it happens 2 -3 times a day. The problem occurred while running Windows 7 and has continued since I've upgraded to Windows 10. My computer is not set to standby/sleep, and I've verified that USB selective suspend is disabled in the power options of the computer. The full error is: VP2: LoadCurrentVantageData_V, error = -32701.
Restarting Cumulus fixes the problem (and checking the "Restart if data stops" option effectively mitigates the problem altogether), but I was just wondering if there's anything else I can look so it doesn't happen at all? I've attached a zip of my diag files. The end of the .008 file shows the data stoppage, and .009 was created when the application restarted itself. Thanks!
I've used Cumulus along with my Vue/Data Logger for years on an older Windows 7 desktop without issue. I've recently migrated to a new Dell Optiplex 790 desktop running Windows 7 (and now Windows 10), but I've noticed Cumulus will report errors on the console periodically and data reception will stop. The problem is sporadic - sometimes I'll go a 2-3 days without an issue, and others it happens 2 -3 times a day. The problem occurred while running Windows 7 and has continued since I've upgraded to Windows 10. My computer is not set to standby/sleep, and I've verified that USB selective suspend is disabled in the power options of the computer. The full error is: VP2: LoadCurrentVantageData_V, error = -32701.
Restarting Cumulus fixes the problem (and checking the "Restart if data stops" option effectively mitigates the problem altogether), but I was just wondering if there's anything else I can look so it doesn't happen at all? I've attached a zip of my diag files. The end of the .008 file shows the data stoppage, and .009 was created when the application restarted itself. Thanks!