Forum Discussion
Usage meter javascript error
A javascript error occured in the main process. Uncaught exception: Error: Error parsing your configuration file: [C:\Users\Vampy\AppData\Roaming\HughesNet Usage Meter\status-meter.config]: Unexpe...
The following fix for the Javascript error won't cripple your computer. Just don't delete anything other than what's described in the instructions. Regarding Windows, you'll probably have to change your folder options to be able to view Hidden Items to see the AppData folder and its contents described in the directions. To do so, click "View", then check the box for "Hidden Items", as you see in the red boxes in the picture below. When you're finished with the procedure, uncheck "Hidden Items" so they are hidden again, as they are hidden by default for a reason. If you have a Mac, I'm not sure if you have to unhide anything.
The instructions for the JavaScript error. Credit goes to MarkJFine.
In the event that this happens:
1. Fully quit the Usage Meter from it's own menu by clicking on the donut in the menubar and clicking "Quit".
2. Look for the following directory
Windows: C:\Users\[your User name]\AppData\Roaming\
Mac: /Users/[your User name]/Library/Application Support/
3. Carefully delete just the "HughesNet Usage Meter" folder under that and empty the trash.
4. Restart the Usage Meter. This will regenerate all the underlying information as if it were run for the first time, thus correcting the error.
This solution did not work for me. I installed the latest update of Java and reinstalled the usage meter. Still getting the unexpected token error. Also when I go online and check my usage, it is not billing correctly. Everything is being put into the anytime data skot which causes me to fall short by about 2 days every month. I spoke with tech support abo0ut this to no satisfaction. This is affecting my business and I rely could use some help.
Yeah... Java has nothing to do with the program at all... The solution isn't what op marked as the solution, the solution is to delete the file that it's complaining about when you get the error.
Hi all!
Thank you for letting us know this has come up again. We've escalated this issue to our development team to figure out why this is happening again. I will post an update here when we've received more information.
Thank you
Amanda
Here's the error message I get:
Is this the same issue as above?
Not the same... I have no idea what that is.
You may want to completely reinastall, since it looks like something is missing.
