Page 1 of 1
Exporttomysql after build 3190
Posted: Mon 20 Jun 2022 1:14 am
by BrunswickWeather
After build 3190 Exportomysql fails as per attachments.
Using latest exe as per wiki.
Re: Exporttomysql after build 3190
Posted: Mon 20 Jun 2022 5:31 am
by HansR
The assembly definition does not match the library present.
Did you copy all files from the distribution during the upgrade?
Or, aha..., Mark must create a new executable against the new libraries!
Re: Exporttomysql after build 3190
Posted: Mon 20 Jun 2022 9:37 am
by mcrossley
Yes, I'll need to relink it against the new libraries, doh! ....
Re: Exporttomysql after build 3190
Posted: Mon 20 Jun 2022 9:45 am
by mcrossley
Done, v1.5.0 is available.
Re: Exporttomysql after build 3190
Posted: Mon 20 Jun 2022 11:34 pm
by BrunswickWeather
The new version does not seem to work on Build 3190.
The previous version works on a previous version of Cumulus MX 3184
Both on the the same PC run about 2 minutes apart
Re: Exporttomysql after build 3190
Posted: Tue 21 Jun 2022 5:59 am
by sfws
BrunswickWeather wrote: ↑Mon 20 Jun 2022 11:34 pm
The new version does not seem to work on Build 3190.
ExportToMySQL.exe release 1.5 does not flag any such error for me, but I accept differences exist between your test and mine :
- I ran it with MONO 6.12.0.182 on Raspberry Pi OS (not .NET on Microsoft Windows)
- I tested it with a monthly file (not dayfile)
- I downloaded directly from Git Hub page (not via Cumulus Wiki Software page)
Re: Exporttomysql after build 3190
Posted: Tue 21 Jun 2022 6:04 am
by HansR
Obviously you now have the wrong system.memory dll installed for the 1.5 run.
So for the 1.5 run against the 3190 CMX, did you have a complete new directory structure or did you just copy the CMX and Exporttomysql exe files?
Copy again and make sure you copy all dll files in the distribution.
(Or Mark made a link error but that seems more unlikely)
Re: Exporttomysql after build 3190
Posted: Tue 21 Jun 2022 8:21 am
by mcrossley
Argh! It was me - I checked the versions against my latest build (3191) rather than 3190.
So, I'll create a v1.4.1 release for 3190, and put that up as well as 1.5.0 as the 3191 release will be soon - I need to fix that Ecowitt station settings page error.
Re: Exporttomysql after build 3190
Posted: Tue 21 Jun 2022 8:48 am
by mcrossley
OK, version 1.4.1 is available from the Wiki - but not on on Github, yet.
Re: Exporttomysql after build 3190
Posted: Wed 17 Aug 2022 3:43 am
by BrunswickWeather
Should version 1.4.1 work with build 3196?
C:\CumulusMX>exporttomysql dayfile
Parameter: dayfile
Error encountered opening MySQL connection
Could not load file or assembly 'System.Memory, Version=4.0.1.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Cumulus MX 3196 loads data to the database.
Re: Exporttomysql after build 3190
Posted: Wed 17 Aug 2022 8:38 am
by mcrossley
Ah, no it will not. I forgot to go back and re-release version 1.5.0.
Version 1.6.0 will soon be released to accompany CMX 3.20.0 - can you wait until then?
Re: Exporttomysql after build 3196
Posted: Wed 17 Aug 2022 11:36 pm
by BrunswickWeather
Thanks Mark
Next release OK
Reinstalled Maria DB as MySQL stopped due to a "unexpected error".
I know there are ways to repair the error but the quickest for me is to delete and start again as I only use the three tables from Cumulus MX. I use the database into Excel for history from the last 12 years of Cumulus recording.