Hi,
also see item Error when attempting to turn automation off - Have to run jobs via automation | Community (safe.com).
We also encounter this issue after fresh install of FME Flow 2023.2.1 on a new Windows 2022 server. Below are all answers on questions asked in the related topic. Can anyone suggest some path to solutions?:
- What version and build of FME Flow are you using?
FME Flow 2023.1.1 Build 23774 Win64
- Is this an express, distributed, or fault-tolerant deployment of FME Flow?
Distributed (database on a separate MS-SQL Server)
- If you restart FME Flow, does it resolve (even if temporary)?
We restarted FME Flow and that resolved it once. Later we ran into the same issue and after another restart it did not resolve.
- what is the FME Flow database? The default Postgres, or another, like SQL Server?
This is a MSSQL 2019 Database
Connect string: DB_JDBC_URL=jdbc:sqlserver://guo10794.k-domstad.org;port=1433;databaseName=fmeserver;TrustServerCertificate=true
The connect string uses jdbc driver. On the Windows 2022 server also OLE DB driver is installed:
- Is there any errors reported in the fmeconnection.log?
After the first issue we found this:
Wed-31-Jan-2024 03:01:08.137 AM ERROR healthnodeclient SQLException: The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.
Wed-31-Jan-2024 03:01:08.138 AM ERROR healthnodeclient com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.
COM.safe.fmeserver.api.FMEServerException: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.
at COM.safe.fmeserver.database.ManagerBase.execute(ManagerBase.java:146)
at COM.safe.fmeserver.database.healthNode.HealthNodeOps.healthNodeKeepAlive(HealthNodeOps.java:42)
at COM.safe.fmeserver.database.healthNode.HealthNodeClient.run(HealthNodeClient.java:92)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is broken and recovery is not possible. The client driver attempted to recover the connection one or more times and all attempts failed. Increase the value of ConnectRetryCount to increase the number of recovery attempts.
at com.microsoft.sqlserver.jdbc.ReconnectThread.run(IdleConnectionResiliency.java:498)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host guo10794.k-domstad.org, port 1433 has failed. Error: "Connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
The second time we encountered the issue there’s this in the fmeconnection.log:
Fri-09-Feb-2024 02:01:10.413 PM INFORM requesthandler 401831 : Accepted new client connection from /172.29.80.164 on port 7071
Fri-09-Feb-2024 02:01:10.454 PM ERROR requesthandler 929028:SQL Query SELECT ncid, connectionname, connectiontype, servicename, username FROM fme_nc_namedconnections WHERE username IS NULL ORDER BY username DESC failed. Error: Could not find prepared statement with handle 1.
Fri-09-Feb-2024 02:01:10.456 PM ERROR pool-6-thread-1 410113 : (Automations) Unable to disassemble automation. 929028:SQL Query SELECT ncid, connectionname, connectiontype, servicename, username FROM fme_nc_namedconnections WHERE username IS NULL ORDER BY username DESC failed. Error: Could not find prepared statement with handle 1.
Fri-09-Feb-2024 02:01:57.928 PM INFORM requesthandler 401937 : Accepted new FME Engine connection.
Fri-09-Feb-2024 02:01:57.929 PM INFORM requesthandler 401950 : Registering FME Engine...
Fri-09-Feb-2024 02:01:57.985 PM ERROR requesthandler 401959 : FME Server license does not allow more than maximum of 1 FME Engine(s).
Fri-09-Feb-2024 02:01:57.989 PM ERROR requesthandler 401939 : Failed to register FME Engine.
Kind regards,
Gerro Zegeling
