Official SuiteCRM Outlook Plugin v4 has arrived - Compatible with the Outlook Web App or Outlook 2016+ connected to Office365 or Exchange Server 2016. A complete rebuild developed and maintained by SuiteCRM developers, the addon retains previous functionality while massively improves performance, reliability and stability!
#4538 - An unknown error has occurred, please check input and try again. / Database failure. Please refer to suitecrm.log for details.
Hello. I have two problems with the plugin installation/configuration: 1) When adding the user under "SUITECRM OUTLOOK PLUGIN", in the subpanel "Outlook Users". I get an error saying "Database failure. Please refer to suitecrm.log for details.". This is something similar to this issue https://github.com/salesagility/SuiteCRM/issues/9788, but that fix doen't work for this problem. It seems like the query is not properly constructed:
Se encontraron 1 errores durante el análisis.
Símbolo (token) inesperado. (near ")" at position 75)
consulta SQL: Documentación
SELECT users.* FROM users WHERE sa_outlook_is_licensed != 0 AND deleted = 0) ORDER BY users.id asc LIMIT 0,15
2) When configuring the plugin in Outlook, I enter all the information populating all the fields copying and pasting and I get this error: "An unknown error has occurred, please check input and try again."
2 years ago
Both issues may be related to your database errors. What version of SuiteCRM are you using and what database backend?
2 years ago
Hello. Here is the info:
SuiteCRM Version 7.12.7 Sugar Version 6.5.25 (Build 344)
Servidor de base de datos Tipo de servidor: MySQL Versión del servidor: 8.0.31 - MySQL Community Server - GPL Versión del protocolo: 10 Conjunto de caracteres del servidor: UTF-8 Unicode (utf8mb4)
Servidor web cpsrvd 11.106.0.9 Versión del cliente de base de datos: libmysql - mysqlnd 7.4.30 extensión PHP: mysqliDocumentación curlDocumentación mbstringDocumentación Versión de PHP: 7.4.30
2 years ago
This appears to be a core bug in the SuiteCRM application rather than a bug in the plugin itself. There are a number of proposed solutions on github. It may be worth testing these locally or waiting upon the next release.