Calificación:
  • 1 voto(s) - 5 Media
  • 1
  • 2
  • 3
  • 4
  • 5
Sysme Inicio
#1
Hola estimado amigos por favor tengo un problema con el software Sysme con icono de acceso al programa no puedo acceder al programa me da error de conexion dice no se que le paso hace como varias semana que no lo usaba y hoy queria acceder al programa y ahora me da error y entra al programa no se que pueda estar pasando por favor si me pueden ayudar no quiero borrarlo y volver a instalar ya que tenia una configuracion y unos pocos articulos registrado en el programa..... por favor les agradesco la ayuda urgentemente
Responder
#2
Hola wuilfredogs,

Ejecuta de forma manual el fichero C:\SYSME\sysmeserver\bin\start.bat, esto iniciará el motor de datos y mostrará una ventana de comandos que puedes cerrar. Luego inicia el programa.

Hazme saber si te aparece algún error.
Oscar Guirado
Sysme Software

Sysme Software
Veravap
Responder
#3
Hola amigo Oscar, segui los pasos que me indicaste pero me da igual el mismo error me sale error tpv de coneccion luego le doy a ok y me entra a la pantalla de configuarar sysme tengo la captura de las dos pantalla como te las envio
Responder
#4
Pero te aparece la ventana de comandos al ejecutar el start.bat? desaparece sola?
Oscar Guirado
Sysme Software

Sysme Software
Veravap
Responder
#5
Aparece una ventana pero desaparece sola enseguida tengo la captura de pantalla.... sigue con el error
Responder
#6
Ok, entonces el problema está en el motor de base de datos ... vamos a hacer lo siguiente:

1 - Elimina el fichero de errores ( C:\SYSME\sysmeserver\data\NOMBREEQUIPO.err (el fichero tendrá como nombre el nombre de tu equipo + la extensión .err)), hacemos esto para que el motor lo genere de nuevo y podamos comprobar el mensaje exacto

2 - Desactiva cualquier antivirus que tengas en el equipo para descartar que sea este el motivo del problema de arranque

3 - Inicia el programa, si el problema persiste, copia aquí el contenido del fichero de error.

Ya me dices.
Oscar Guirado
Sysme Software

Sysme Software
Veravap
Responder
#7
Nada igual hago exactamente lo que me dices tengo un Anti Virus lo desactive... pero el ante funcionaba normalito con su antivirus... pero igual hago lo que me dices desactive el antivirus.... elimine el fichero que dice mi nombre del equipo pero no tiene la extencion .err voy star y corro el programa y me da el mismo error... el fichero vuelve aparece con el nombre del equipo... pero sigo con el mismo problema dice error de coneccion y me entra a la pantalla de configuracion sin darme ninguna opcion No se que podra ser....sera que como tenia dias sin abrirlo sera por eso o no tiene nada que ver....
Responder
#8
Abre el fichero .err con el bloc de notas de Windows y copia aquí el contenido así puedo ver la descripción del error.

PD: que esté dias, semanas, meses o años sin abrir es indiferente.
Oscar Guirado
Sysme Software

Sysme Software
Veravap
Responder
#9
Me imagino que te refieres al fichero C:\SYSME\sysmeserver\data\NOMBREEQUIPO.err ante mencionado con el nombre del equipo... aqui esta lo que dice...

InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 17:14:51 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...
140126 17:14:51 InnoDB: Started; log sequence number 0 117524616
140126 17:14:51 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 17:14:59 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...
140126 17:14:59 InnoDB: Started; log sequence number 0 117524616
140126 17:14:59 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 17:15:01 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...
140126 17:15:01 InnoDB: Started; log sequence number 0 117524616
140126 17:15:01 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 17:29:59 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...
140126 17:29:59 InnoDB: Started; log sequence number 0 117524616
140126 17:29:59 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 17:30:00 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...
140126 17:30:00 InnoDB: Started; log sequence number 0 117524616
140126 17:30:00 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 18:31:36 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...
140126 18:31:36 InnoDB: Started; log sequence number 0 117524616
140126 18:31:36 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 18:31:38 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...
140126 18:31:38 InnoDB: Started; log sequence number 0 117524616
140126 18:31:38 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 18:33:27 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...
140126 18:33:27 InnoDB: Started; log sequence number 0 117524616
140126 18:33:27 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 18:34:09 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...
140126 18:34:10 InnoDB: Started; log sequence number 0 117524616
140126 18:34:10 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 18:36:59 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...
140126 18:36:59 InnoDB: Started; log sequence number 0 117524616
140126 18:36:59 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140126 18:37:01 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...
140126 18:37:01 InnoDB: Started; log sequence number 0 117524616
140126 18:37:01 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140127 7:08:49 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...
140127 7:08:49 InnoDB: Started; log sequence number 0 117524616
140127 7:08:49 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140127 7:08: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...
140127 7:08:55 InnoDB: Started; log sequence number 0 117524616
140127 7:08:55 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140127 7:08:56 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...
140127 7:08:57 InnoDB: Started; log sequence number 0 117524616
140127 7:08:57 [ERROR] Fatal error: Can't open and lock privilege tables: File '.\mysql\host.MYD' not found (Errcode: 2)
Responder
#10
Aha, ok,

Prueba a eliminar los archivos temporales del sistema, esto ha ocurrido en alguna ocasión y se ha solucionado así.

Ya me dices.
Oscar Guirado
Sysme Software

Sysme Software
Veravap
Responder


Salto de foro:


Usuarios navegando en este tema: 1 invitado(s)

Contáctanos | Sysme Software | Volver arriba | | Archivo (Modo simple) | Sindicación RSS