Forum Discussion

Vampy's avatar
Vampy
Freshman
8 years ago

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]: Unexpected Token

 

I tried uninstalling and reininstalling and got the same thing.  Any suggestions ?  Thanks in advance for any help.

  • GabeU's avatar
    GabeU
    7 years ago

    inthewoodsworki

     

    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.

  • C0RR0SIVE's avatar
    C0RR0SIVE
    Associate Professor

    Vampy,

    Try uninstalling the status meter and usage meter from your system, then navigate to C:\Users\Vampy\AppData\Roaming\HughesNet Usage Meter\, and delete anything that desides in that folder.  Also navigate to c:\program files\hughesnet-usage-meter and delete anything that may reside in that folder.  Then download and install the latest version (Should be 6.6) and see what happens.

    • RG's avatar
      RG
      Sophomore

      Meter working now ,Thank you for the fix. Was working fine until a lightning storm rolled through and power kept going on and off, so now when weather gets bad i shut the computer down!

        RG

      • GabeU's avatar
        GabeU
        Distinguished Professor IV

        RG wrote:

        Meter working now ,Thank you for the fix. Was working fine until a lightning storm rolled through and power kept going on and off, so now when weather gets bad i shut the computer down!

          RG


        You'd never think a power issue could, or even would, cause something like this, and why it does, at least for you and I, is definitely a head scratcher.  At least it can be fixed, though, thankfully.   

    • dmag1306's avatar
      dmag1306
      New Member

      That did it for me!    Thank you  -I tried the whole Java Runtime install and same problem so went to the Roaming Folder in App Data and folders from previous and the current install were there even after uninstalling.  So I deleted the old folder and had to go to Task Manager and end the current Hughes Net Usage Meter Background Processes ( two separate instances) to be able to delete the current folder in App Data.  Then I reinstalled the current Usage Meter and it worked fine like before.  :)   Thank you so much again!

    • nicole.miller's avatar
      nicole.miller
      Spectator

      I'm having the same issue on a Mac. I've deleted and reinstalled the program to no avail. What next? Thanks.

      • C0RR0SIVE's avatar
        C0RR0SIVE
        Associate Professor

        What about the file in particular that is mentioned in the error?  I am suspecting that uninstalling isn't removing that file for some reason, and that's why a reinstall isn't working.

  • Fwiw I had the same problem and this was my experience …

     

    1. Uninstalled & reinstalled usage meter.  Problem remained.
    2. Uninstalled usage meter.  Uninstalled & reinstalled JRE. Reinstalled Usage Meter.  Problem remained.
    3. Cleared the contents of C:\Users\YourUserName\AppData\Roaming\HughesNet Usage Meter\ and then: Uninstalled usage meter.  Uninstalled & reinstalled JRE. Reinstalled Usage Meter.  Problem fixed. 

     

    I hope that helps somebody with similar problems.

    • RG's avatar
      RG
      Sophomore

      Your fix worked for me! Thanks for the information , Need to look at community first before calling tech support!

        RG

    • MarkJFine's avatar
      MarkJFine
      Professor

      Curious... would have thought just clearing the js cache might be enough and then restarting. Good info.

    • motobojo's avatar
      motobojo
      Junior

      This problem cropped up again today.  The good news is that the steps identified above still fix the problem.  Is there something Hughesnet can do to avoid the problem cropping up?  Is there something I can do to avoid having this problem crop up over and over?

  • Updating java and deleting the hughes net meter folder from (C:\Users\Usernamehere\AppData\Roaming) your appdata folder worked for me.

    • BirdDog's avatar
      BirdDog
      Assistant Professor

      eric30110 wrote:

      Updating java and deleting the hughes net meter folder from (C:\Users\Usernamehere\AppData\Roaming) your appdata folder worked for me.


      Good info, I had to do this recently myself but didn't post it here. Good that you did.

  • I solved this by uninstalling the program, deleating the folder in the error message, and then reinstalling the program. Installing and uninstalling Java did nothing.

    • GabeU's avatar
      GabeU
      Distinguished Professor IV

      FredB wrote:

      I solved this by uninstalling the program, deleating the folder in the error message, and then reinstalling the program. Installing and uninstalling Java did nothing.


      Unfortunately, the reply that should really be marked as the solution (Corrosive's) isn't the one that is marked as such.  Java itself is unrelated to the issue.

       

      Uninstalling meter, deleting the folder in question, and reinstalling the meter, like you did, is all that is needed.  

       

      It's an odd little error that seems to pop up without rhyme or reason.   

      • GabeU's avatar
        GabeU
        Distinguished Professor IV

        Had this pop up on me again today.  Had to perform a hard shutdown due to my desktop freezing.  When I started it back up, sure enough, it was there, staring at me with its ugly little message.  :(  

         

        Closed the meter down (had to do it through the task manager), uninstalled it, deleted the info in the offending folder, reinstalled the meter and now it's working fine.  :)

         

        Edit:  For those who experience this for the first time on a Windows based computer, you'll most likely have to enable the viewing of hidden items to see the AppData folder and its contents.  

         

            

  • Reinstallation and Java update did not work for me. Here is how I solved it. I first closed the Usage Meter in Task Manager. Then I deleted the file: "C:\Users\Chip\AppData\Roaming\HughesNet Usage Meter\status-meter.conf." That file was recreated in a properly functioning form when I restarted the Usage Meter.

    • GabeU's avatar
      GabeU
      Distinguished Professor IV

      Chipster96

       

      The "Accepted Solution" on the first page contains incorrect information.  Java and Javascript are two different things, and updating or deleting and reinstalling Java has no effect on the JavaScript issue.  

       

      The correct instructions have been posted throughout this thread, but people first see the "Accepted Solution" and assume, and rightfully so, that it is the actual solution, while in reality it isn't.  

       

      Only the person who started the thread can accept, or un-accept, a given solution, which ironically, in this case, was also written by the person who started the thread.  The OP hasn't been on here in over a year, so unless a moderator intervenes and un-accepts the post as the solution, people will continue to see it as the fix, when it actually isn't.  :(  

      • GabeU's avatar
        GabeU
        Distinguished Professor IV

        Liz

        Amanda

         

        Is there any way that one of you could un-accept the accepted solution for this error?  It's not the correct fix, and it gives steps concerning Java, which has nothing to do with this error.  

         

         

         

         

  • This solution worked beautifully for me.   thank you for the assist!

    • GabeU's avatar
      GabeU
      Distinguished Professor IV

      Rafela wrote:

      This solution worked beautifully for me.   thank you for the assist!


      You're very welcome.  I'm glad you found the solution and it worked for you.  :)