Upgrade from 4.5 to 4.7 Problem

The problem is true in reports of versions 4.0 and later.
I was hoping with this update to fix it.
When updating, desist it traccar 4.5 delete folder. Restart and proceed to install 4.7 without problem.
I modify the traccar file to connect to my 4.5 database but it does not start giving error.

I'd appreciate your help

2020-01-20 13:42:47  INFO: HikariPool-1 - Starting...
2020-01-20 13:42:48  WARN: Registered driver with driverClassName=com.mysql.jdbc.Driver was not found, trying direct instantiation.
2020-01-20 13:42:50  INFO: HikariPool-1 - Start completed.
2020-01-20 13:42:55  INFO: Clearing database change log checksums
2020-01-20 13:42:56  INFO: SELECT COUNT(*) FROM base1.DATABASECHANGELOGLOCK
2020-01-20 13:42:56  INFO: SELECT COUNT(*) FROM base1.DATABASECHANGELOGLOCK
2020-01-20 13:42:56  INFO: SELECT `LOCKED` FROM base1.DATABASECHANGELOGLOCK WHERE ID=1
2020-01-20 13:42:56  INFO: Waiting for changelog lock....
...
2020-01-20 13:47:26  INFO: Waiting for changelog lock....
2020-01-20 13:47:36  INFO: SELECT `LOCKED` FROM base1.DATABASECHANGELOGLOCK WHERE ID=1
2020-01-20 13:47:36  INFO: Waiting for changelog lock....
2020-01-20 13:47:46  INFO: SELECT `LOCKED` FROM base1.DATABASECHANGELOGLOCK WHERE ID=1
2020-01-20 13:47:46  INFO: Waiting for changelog lock....
2020-01-20 13:47:56  INFO: SELECT ID,`LOCKED`,LOCKGRANTED,LOCKEDBY FROM base1.DATABASECHANGELOGLOCK WHERE ID=1
2020-01-20 13:47:56 ERROR: Main method error - Could not acquire change log lock.  Currently locked by SERVERGPST4 (192.168.0.35) since 1/20/20, 10:28 AM - LockException (... < DataManager:310 < *:90 < Context:292 < Main:110 < ...)
2020-01-20 13:47:56  WARN: JNA: Callback org.traccar.WindowsService$ServiceMain@78452606 threw the following exception - Could not acquire change log lock.  Currently locked by SERVERGPST4 (192.168.0.35) since 1/20/20, 10:28 AM - LockException (... < DataManager:310 < *:90 < Context:292 < Main:110 < ...)

Your database is locked. It means that you restarted server during database migration. Search forum for solution. It has been discussed many times before.

Perfect Anton found the solution to that.
Traccar start correctly.
The fault I am detecting now is with the TK103 Protocol
the same is not working it seems.

2020-01-20 14:18:05  WARN: [e7cc3226] error - Adjusted frame length exceeds 1400: 13889 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-01-20 14:18:05  INFO: [e7cc3226] disconnected
2020-01-20 14:18:05  INFO: [0f1cdfc6: satsol < 201.251.179.183] HEX: 283032373032323531303639374250303533353333323730323235313036393732303031323041333433352e363634365330353833342e30303237573030302e323137313833373030302e303030303030303030304c303030303030303029
2020-01-20 14:18:05  WARN: [0f1cdfc6] error - Adjusted frame length exceeds 1400: 12347 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-01-20 14:18:05  INFO: [0f1cdfc6] disconnected
2020-01-20 14:18:05  INFO: [d2e663a6] connected
2020-01-20 14:18:05  INFO: [346ce3b2: satsol < 201.251.179.220] HEX: 283032373032323733333236354250303533353333323730323237333332363532303031323041333432392e323935365330353833392e37353831573030302e303137313833373331392e363430303030303030304c303030303030303029
2020-01-20 14:18:05  WARN: [346ce3b2] error - Adjusted frame length exceeds 1400: 13117 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-01-20 14:18:05  INFO: [346ce3b2] disconnected
2020-01-20 14:18:05  INFO: [8c8a322d: satsol < 201.251.179.236] HEX: 283032373032313737363937364250303533353333323730323137373639373632303031323041333433332e373731385330353832372e33363235573030302e303137313833383030302e303030303030303030314c303030303030303029
2020-01-20 14:18:05  WARN: [8c8a322d] error - Adjusted frame length exceeds 1400: 13889 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-01-20 14:18:05  INFO: [8c8a322d] disconnected
2020-01-20 14:18:05  INFO: [b821a44d] connected
2020-01-20 14:18:05  INFO: [8978ddd9: satsol < 201.251.179.152] HEX: 283032373032393238363831324250303533353333323730323932383638313232303031323041333433322e333733325330353833342e31393130573030302e303137313833343030302e303030303030303030304c303030303030303029
2020-01-20 14:18:05  WARN: [8978ddd9] error - Adjusted frame length exceeds 1400: 13890 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-01-20 14:18:05  INFO: [8978ddd9] disconnected
2020-01-20 14:18:05  INFO: [7080798b: satsol < 201.251.179.137] HEX: 283032373032393931313031334250303533353333323730323939313130313332303031323041333434382e373536345330353832362e32333639573030302e303137313833353030302e303030313030303030304c303030303030303029
2020-01-20 14:18:05  WARN: [7080798b] error - Adjusted frame length exceeds 1400: 12603 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:43 < ... < NetworkMessageHandler:37 < ...)
2020-01-20 14:18:05  INFO: [7080798b] disconnected

Could it be that they changed the protocol in this version? It seems to be wrong.

now when I point to version 4.5 it works correctly

Solucionado vi que estaba usando el protocolo del satsol porque se duplicaban los puertos.

gracias