Yetiforcecrm: Unable to add new records: "Error: There is no active transaction."

Created on 23 Nov 2016  ·  8Comments  ·  Source: YetiForceCompany/YetiForceCRM

When attempting to add new records of any kind, accounts, employees, etc, it fails with message: "Error: There is no active transaction." This is a brand new installation on a CentOS server with everything but LDAP in passing proper configuration checks.

Your Environment

  • YetiForce Version used: 3.4.0
  • Browser name and version: Chrome 54.0.2840.99 m (64-bit)
  • Environment name and version: Application hosted on CentOS Linux webserver with Apache, PHP5.6, MySQL
  • Operating System and version: Accessed from my desktop (Windows 10 64-bit Pro), Application hosted on Linux web server (configuration above.)
🤷‍♂️ MoreInfoRequired

Most helpful comment

Go to Database and use this query

SET GLOBAL sql_mode='';

All 8 comments

CRON Jobs active?

All defaults say 'Active' inside Yeti except Backup.

look like this (last scan started/ended recently or at installation time?)
cron

https://yetiforce.com/en/administrator-documentation/panel/cron/150-enable-cron.html

Thank you. I am lacking in knowledge of creating CRON jobs actually. Do I create 2 CRON jobs total? One for the vtigercron.sh and one for the cron.log file? Should both jobs run at */5**?
Also, I don't see the cron.log file. Do I just create a text file called 'cron.log' and put it in /cache/logs/cron.log?
Also, in the vtigercron.sh am I required to set the VTIGERCRM_ROOTDIR or leave as-is? Thanks.

CRON has nothing to do with adding records. If you are not able to add records then you have to check the logs to see what’s wrong.

@masterGH If your Question is for Schedule task in Crontab, you only need to add this line.

*/5 * * * * sh /var/www/crm/cron/vtigercron.sh

This path /var/www/crm/cache/logs/cron.log is That's where it's stored logs.

If you whant know how to use Crontab see this information

screen shot 2016-11-24 at 5 07 47 pm

Example
min hour day/month month day/week Execution time
30 0 1 1,6,12 * — 00:30 Hrs on 1st of Jan, June & Dec.
0 20 * 10 1-5 –8.00 PM every weekday (Mon-Fri) only in Oct.
0 0 1,10,15 * * — midnight on 1st ,10th & 15th of month
5,10 0 10 * 1 — At 12.05,12.10 every Monday & on 10th of every month

Go to Database and use this query

SET GLOBAL sql_mode='';

@ahmido That works! Thank you sir. However, just fyi, you will lose the global change when you restart the MySQL server, so you should add: sql_mode="" to your my.cnf file under [mysqld] for permanent changes. You can also do it temporarily your way or through PHPMyAdmin in the Variables section.

@skramanzia Thanks for the explanation on CRON jobs. I had done some research right before you posted that and saw the same diagram. I do understand more about them now. Thank you.

@paula-w Which logs should I have checked? Thanks for your help. Checking the log interface inside Yeti showed nothing. The solution was @ahmido 's above with a slight modification noted in this post (see first section of this post.)

Was this page helpful?
0 / 5 - 0 ratings