(13-04-2023, 03:53 PM)sysme escribió: vale, elimina todos los archivos con extensión .err de esa carpeta, luego ejecuta manualmente el programa C:\SYSME\sysmeserver\bin\start.bat y mira se se ha generado un nuevo fichero .err con el nombre del equipo actual
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
230413 16:55:34 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
230413 16:55:34 InnoDB: Started; log sequence number 0 113888041
Can't start server: Bind on TCP/IP port: Invalid argument
230413 16:55:34 [ERROR] Do you already have another mysqld server running on port: 4306 ?
230413 16:55:34 [ERROR] Aborting
todo el texto
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
230413 16:55:54 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
230413 16:55:54 InnoDB: Started; log sequence number 0 113888041
Can't start server: Bind on TCP/IP port: Invalid argument
230413 16:55:54 [ERROR] Do you already have another mysqld server running on port: 4306 ?
230413 16:55:54 [ERROR] Aborting
230413 16:55:54 InnoDB: Starting shutdown...
230413 16:55:56 InnoDB: Shutdown completed; log sequence number 0 113888041
230413 16:55:56 [Note] mysqld-nt: Shutdown complete