Error upgrading to build 3101

[jgeorges]

I am trying to upgrade from b3093 to b3101. i have tried by applying the changed files incrementally from all releases, and have also tried by just installing all b3101 files into the CumulusMX directory. When I try to start CMX I get the following error:

Code: Select all

Cumulus MX v.3.9.6 build 3101
Working Dir: D:\CumulusMX\
System.InvalidOperationException: Cannot load Counter Name data because an invalid index '' was read from the registry.
   at System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)
   at System.Diagnostics.PerformanceCounterLib.get_NameTable()
   at System.Diagnostics.PerformanceCounterLib.get_CategoryTable()
   at System.Diagnostics.PerformanceCounterLib.CounterExists(String category, String counter, Boolean& categoryExists)
   at System.Diagnostics.PerformanceCounterLib.CounterExists(String machine, String category, String counter)
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName, String instanceName, Boolean readOnly)
   at System.Diagnostics.PerformanceCounter..ctor(String categoryName, String counterName)
   at CumulusMX.Cumulus..ctor(Int32 HTTPport, Boolean DebugEnabled, String startParms)
   at CumulusMX.Program.RunAsAConsole(Int32 port, Boolean debug)
   at CumulusMX.Program.Main(String[] args)
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

I also had a similar problem when I tried to upgrade to 3100 but did not have time to follow it up. Operating system is Windows 10. Device is an Ecowitt GW1000. Diag files attached.

Any advice appreciated.

[HansR]

i have tried by applying the changed files incrementally from all releases

I have noticed many users try to use that type of updating: trying only to copy changed files. I think that is not the best method. Recently @mcrossley removed the changed file list from the Updates.txt file trying to get you as a user to copy the whole distribution to the operational file tree. It is the only correct method of updating which keeps you free of problems.

I would like to point to my Multiplatform CMX Installer which does exactly that: installing an initial CMX installation or an update. You might want to try it, it is not too difficult.

NOTE:your datafiles won't be touched by this method whether you do it with the installer or whether you do it manually.

[PaulMy]

I would like to point to my Multiplatform CMX Installer which does exactly that: installing an initial CMX installation or an update. You might want to try it, it is not too difficult.

I can concur with Hans, do a full files update, and using his Installer is a cinch to update. I just did three CumulusMX updates to v3.9.7-b3107 in minutes.
1. Download the latest CumulusMXDist3107.zip into the InstallCMX folder (and remove the previous Dist.zip)
2. Stop CumulusMX and make a backup copy of the full working \CumulusMX folder.
3. Run InstallCMX.exe
4. After the CMD screen lists all the CumulusMX folders on your computer select that item number
5. Enter Y to confirm the folder where to install or upgrade.
6. Run CumulusMX.

Of course if you have locally modified files then the update will be more difficult. I place any modified or new template files in a separate \web-additions folder, and \webfiles from another template such as MXUIwebsite in a separate \webfiles-additions folder so do not have an issue when updating.

Enjoy,
Paul

[HansR]

@PaulMy: thanks for the addition to stop CMX, it is indeed part of the procedure. I'll add it in the prescription in the download post.

[PaulMy]

Hi Hans,
And one more...
Also to remember that for remote sites the \webfiles need to be FTP as there may be some changes - i.e. the recent selectachart.js and weatherstyle.css
Maybe a message after the update process is completed to do so

Enjoy,
Paul

[HansR]

You mean that changes in standard files will only be visible on the website after the first FTP cycle has passed and the new versions are updated remote?
True, I can give a message and a note on that. Or are you pointing to something else?

Though not really part of whichever update process the user uses, no doubt that can be confusing for some.
Will make a version 1.1 soon.

[PaulMy]

Hi Hans,
Updating the Cumulus program and associated files on the PC is one thing and your InstallCMX does an excellent job on that. But version updates can also include changes to the webfiles that are one-time FTP to the website. In today's update I used InstallCMX and my computer files are up to date. But my website files also need to be updated using FileZilla as there were at least two file changes - weatherstyle.css and selectachart.js (and maybe others as well). My comment was just to make a reminder of doing this one-time FTP as well.

I wasn't thinking of a notice for "waiting for the next update interval" as that is pretty well understood by most users, and the CumulusMX FTP Now is a tool for that if one can't wait the usual 5 minutes.

Enjoy,
Paul

[HansR]

Mmm... Yes, i'll PM you for some elaboration on this.

[jgeorges]

I have noticed many users try to use that type of updating: trying only to copy changed files. I think that is not the best method.

Thanks Hans, however you'll notice that my message also says that I: have also tried by just installing all b3101 files into the CumulusMX directory.

In other words I copied the entire contents of the zip file into the CumulusMX directory (after restoring to the 3093 version). So this doesn't seem to be related to the method I am using to upgrade.

Is there anything in the Disgs or error message that may give a hint ?

[PaulMy]

Hi jgeorges,
Sorry to have taken this off topic.

I presume the first MXdiags file is the previous CumulusMX version 3093, and the second file after update to b3101?
From the first file it seems that CumulusMX is working fine but that your Internet settings are not yet entered causing the many errors.
You mention that you have also tried with a fresh install, and is the error then the same and nothing else in MXdiags?

Both b3101 and current version b3107 run ok for me. Others may have better suggestions but things I would try:
1. Stop and restart computer
2. Download b3107 and unzip in a new folder (may as well go to the latest version if you are updating). Copy in your previous Cumulus.ini and start CumulusMX as administrator and with the -debug parameter
3. Check MXdiags and zip up if needed

Enjoy,
Paul

[HansR]

I have noticed many users try to use that type of updating: trying only to copy changed files. I think that is not the best method.

Thanks Hans, however you'll notice that my message also says that I: have also tried by just installing all b3101 files into the CumulusMX directory.

In other words I copied the entire contents of the zip file into the CumulusMX directory (after restoring to the 3093 version). So this doesn't seem to be related to the method I am using to upgrade.

Is there anything in the Disgs or error message that may give a hint ?

OK.

In addition to Pauls remark and when you're convinced the installation is correct, please also check your Windows update status as well.

[HansR]

I have been searching a bit further both into your logfiles and the CMX code.

1. You first logfile starting on 28/1 is already full of errors wrt FTP. The setup of the FTP is wrong (un/pw demanded)
2. The second start on 31/1 fails on the request in the constructor (so it is just starting up, nothing is done yet) for a PerformanceCounter and that one is

   Code: Select all

   PerformanceCounter("System", "System Up Time");

   So there is nothing special but everything is indicating a mismatch of versions in DLLs of .NET

In my view, there was already an error in the setup which worsened with the recent upgrade.

What I said in my prev. post: try a Windows update to current status, that might sync all versions. CMX uses .NET and keeps up more or less with the Windows updates. So if you do update CMX but are lagging behind with windows (or on linux with mono) in the end it can't find the right versions of DLLs and it fails. My guess is that is what is happening here.

[mcrossley]

If it's any hint, the only performance counter MX opens on Windows is the System/System Up Time counter.

Can you open that counter in your Performance Monitor application? Just add it as an extra series to the graph.
If it works there, then it would indicate a .Net issue along the lines of previous suggestions.

[HansR]

If it's any hint, the only performance counter MX opens on Windows is the System/System Up Time counter.

Can you open that counter in your Performance Monitor application? Just add it as an extra series to the graph.
If it works there, then it would indicate a .Net issue along the lines of previous suggestions.

Now that is interesting but how the hell do you do that?
Any suggestion or article?

[mcrossley]

Start -> type "Performance Monitor" -> Open

Select "Performance Monitor" in left hand pane

PerfMon1.png

Click the green PLUS icon

Expand "System" in the top left pane, select "System Up Time", click "Add >>", click "OK"

Then select the system uptime sires at the bottom of the graph and check the Last Value is incrementing each second.

AH! Do the home versions of Windows 10 even have Perf Mon?