EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-01-15 07:45 AM
Hi,
I have an issue with a new custom driver to retrieve data from EEH. It gives the following error :
"""
Logging started at 15-JAN-2025 14:37:58.669 (UTC)
File : C:\ProgramData\Schneider Electric\ClearSCADA\Logs\Drivers\DriverEEH_001.log
System : Microsoft Windows 10 Professional Edition, 64-bit (10.0.19045)
CPU : 1 x AMD Engineering Sample 90 nm, 32KB L1 Instruction Cache, 32KB L1 Data Cache, 512KB L2 Cache
ClearSCADA Core : Build 6.86.8986.1 (Release)
Local time zone : UTC+01:00 (Standard)
Process ID : 5752
Computer : DESKTOP-U4E2CIE
Driver : SEEnergy
Logging options:
APP : Application
ERR : Errors
SRC : Point Source
SVR : Server
-------------------------------------------------------------------------------
15-JAN-2025 14:37:58.670 0DA8 [APP] Maximum background pending device updates: 100.
15-JAN-2025 14:37:58.670 0DA8 [APP] Block server thread if background pending device updates list is full: True.
15-JAN-2025 14:37:58.670 0DA8 [APP] Starting background DB Point Update Thread...
15-JAN-2025 14:37:58.671 0DA8 [APP] ...Background DB Point Update Thread started.
15-JAN-2025 14:37:58.671 0DA8 [APP] SEEnergy driver started
15-JAN-2025 14:37:58.674 0DA8 [APP] Connect to DBServer
15-JAN-2025 14:37:58.699 0DA8 Connect to DBServer returns 0x80072745
0DA8 An established connection was aborted by the software in your host machine.
15-JAN-2025 14:37:58.699 0DA8 [ERR] ConnectToDBServer failed
15-JAN-2025 14:37:58.700 0DA8 [APP] Shutting down background DB Point Update Thread...
15-JAN-2025 14:37:58.700 0DA8 [APP] Background DB Point Update Thread stopped.
15-JAN-2025 14:37:58.700 0DA8 [APP] Main Loop Exiting
-------------------------------------------------------------------------------
Logging stopped at 15-JAN-2025 14:37:58.701 (UTC)
"""
My driver is not able to connect to the database. But the database is currently running according to the service manager.
Also, odd thing is that my driver only produced one log file in 20 attempts...
Could you please support me this topic ?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-01-16 03:53 AM
If the database does not contain any of your driver's object types then it won't start. If you run it in debug it will not log anything beyond initialisation.
Steve
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-01-16 04:41 AM
Hi,
After a fresh and clean GeoScada reinstallation, the driver finally connected to the new created Database. At the end, it appears that the driver was not looking for the right .exe file.
Allan
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-01-19 08:25 PM
If you have access to the old Registry settings, check how they are configured for the driver. That references the exe file to load. Those log lines suggest however that the exe part is running correctly and cleanly stopping.
"An established connection was aborted by the software in your host machine" when connecting to localhost may mean:
1. The server component process failed, in this case Geo SCADA would probably be stopped too
2. Some HIDS type solution is closing the localhost socket
If it were over the network you could use something such as WireShark and look for packets with the reset flag, but with localhost this is much more complex.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-01-16 03:53 AM
If the database does not contain any of your driver's object types then it won't start. If you run it in debug it will not log anything beyond initialisation.
Steve
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-01-16 04:41 AM
Hi,
After a fresh and clean GeoScada reinstallation, the driver finally connected to the new created Database. At the end, it appears that the driver was not looking for the right .exe file.
Allan
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-01-19 08:25 PM
If you have access to the old Registry settings, check how they are configured for the driver. That references the exe file to load. Those log lines suggest however that the exe part is running correctly and cleanly stopping.
"An established connection was aborted by the software in your host machine" when connecting to localhost may mean:
1. The server component process failed, in this case Geo SCADA would probably be stopped too
2. Some HIDS type solution is closing the localhost socket
If it were over the network you could use something such as WireShark and look for packets with the reset flag, but with localhost this is much more complex.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.
With achievable small steps, users progress and continually feel satisfaction in task accomplishment.
Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.
of