Page 1 of 1
Problem with b3283a
Posted: Thu 28 Mar 2024 1:22 pm
by bumpy
Hello again
I've hit a problem!
I uploaded build 3283a but since doing so I cannot get any data to load. The latest diagnostic report shows the following message:-
2024-03-28 13:14:39.758 InitTCP: Error - Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
2024-03-28 13:14:39.758 InitTCP: Connecting to the station
2024-03-28 13:14:39.758 OpenTcpPort: TCP Logger Connect attempt 1
2024-03-28 13:14:40.775 OpenTcpPort: TCP Logger reconnected
2024-03-28 13:14:40.775 InitTCP: Flushing input stream
2024-03-28 13:14:42.821 InitTCP: Sending TEST (1) command
2024-03-28 13:14:44.839 InitTCP: TEST (1) received - ''
2024-03-28 13:14:44.839 InitTCP: Sending TEST (2) command
2024-03-28 13:14:44.839 InitTCP: Error - Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
2024-03-28 13:14:44.839 InitTCP: Connecting to the station
2024-03-28 13:14:44.839 OpenTcpPort: TCP Logger Connect attempt 1
I have no idea what this means. Initially I thought it was a server problem and contacted its technical staff which confirmed that were no problems and this appeared to be a software issue.
Can anyone suggest a solution please?
Tony
www.farleighmeadows.co.uk
Re: Reworked default websites
Posted: Thu 28 Mar 2024 1:31 pm
by NeilThomas
bumpy wrote: ↑Thu 28 Mar 2024 1:22 pm
Hello again
I've hit a problem!
I uploaded build 3283a but since doing so I cannot get any data to load. The latest diagnostic report shows the following message:-
2024-03-28 13:14:39.758 InitTCP: Error - Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
2024-03-28 13:14:39.758 InitTCP: Connecting to the station
2024-03-28 13:14:39.758 OpenTcpPort: TCP Logger Connect attempt 1
2024-03-28 13:14:40.775 OpenTcpPort: TCP Logger reconnected
2024-03-28 13:14:40.775 InitTCP: Flushing input stream
2024-03-28 13:14:42.821 InitTCP: Sending TEST (1) command
2024-03-28 13:14:44.839 InitTCP: TEST (1) received - ''
2024-03-28 13:14:44.839 InitTCP: Sending TEST (2) command
2024-03-28 13:14:44.839 InitTCP: Error - Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
2024-03-28 13:14:44.839 InitTCP: Connecting to the station
2024-03-28 13:14:44.839 OpenTcpPort: TCP Logger Connect attempt 1
I have no idea what this means. Initially I thought it was a server problem and contacted its technical staff which confirmed that were no problems and this appeared to be a software issue.
Can anyone suggest a solution please?
Tony
www.farleighmeadows.co.uk
Hi Tony
This indicates that CumulusMX cannot FTP to your server. I suggest that you downgrade to the previous version of CumulusMX as it is nothing to do with the default website setup. If you are still having difficulty then check that you have the correct details configured for both the FTP account and the paths for the uploads.
There may well be others on the Forum that are better equipped to help you sort out this issue.
Neil.
Re: Problem with b3283a
Posted: Thu 28 Mar 2024 1:34 pm
by freddie
@bumpy please start a new topic in a relevant forum if you have a new issue. I've split your question off into its own topic.
Re: Problem with b3283a
Posted: Thu 28 Mar 2024 2:09 pm
by SamiS
bumpy wrote: ↑Thu 28 Mar 2024 1:22 pm
Hello again
I've hit a problem!
I uploaded build 3283a but since doing so I cannot get any data to load. The latest diagnostic report shows the following message:-
2024-03-28 13:14:39.758 InitTCP: Error - Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
2024-03-28 13:14:39.758 InitTCP: Connecting to the station
2024-03-28 13:14:39.758 OpenTcpPort: TCP Logger Connect attempt 1
2024-03-28 13:14:40.775 OpenTcpPort: TCP Logger reconnected
2024-03-28 13:14:40.775 InitTCP: Flushing input stream
2024-03-28 13:14:42.821 InitTCP: Sending TEST (1) command
2024-03-28 13:14:44.839 InitTCP: TEST (1) received - ''
2024-03-28 13:14:44.839 InitTCP: Sending TEST (2) command
2024-03-28 13:14:44.839 InitTCP: Error - Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.
2024-03-28 13:14:44.839 InitTCP: Connecting to the station
2024-03-28 13:14:44.839 OpenTcpPort: TCP Logger Connect attempt 1
Hi Tony,
Basically this is saying, that CMX cannot connect to your Davis station/logger or whatever it is called. I wonder if your Windows Firewall blocks the connection.
The logfile also indicates that there is also something wrong with your data files. It says that your dayfile.txt has 11 duplicate lines for 27th Mar. And your Mar24log.txt has also errors, CMX tries to load first 10 lines and then aborts due to too much errors.
As Neil said, I would also recommend returning to older version to see if it still works normally. If the data files are corrupted, hopefully you made a complete backup of CumulusMX folder and subfolders before the upgrade.
—
Sami
Re: Problem with b3283a
Posted: Thu 28 Mar 2024 3:58 pm
by bumpy
Hello again Sami
I have now checked the firewall settings and there are no restrictions on CumulusMx. So I have no idea. I think I'm at the point of giving up entirely having spent hours over recent days trying to resolve this but tomorrow is another day....!
Tony
Re: Problem with b3283a
Posted: Thu 28 Mar 2024 4:03 pm
by mcrossley
What type of logger are you using? MX appears to make the initial connection, then cannot send any data. Nothing else is connected to the logger is it?
Re: Problem with b3283a
Posted: Thu 28 Mar 2024 7:09 pm
by bumpy
Hello
Thank you to those who provided helpful suggestions.
Finally after a lot of exasperation I have almost resolved the issue. I did mention in one post that in desperation I'd relaunched Cumulus1 which worked fine and this morning deleted the programme and thought no more of it. In removing some other 'junk' I got a point where one folder wouldn't delete because the folder or file within it was use elsewhere. Try as I might I couldn't locate the file but a sudden thought took me to Tark Manager where Cumulus1 was happily working away. I deleted this folder, restarted CumulusMx and it sprang to life.
I need to make a few minor adjustments to get CumulusMX fully right but at the moment I'm just happy that it's working again!
Thank you all again.
Tony