Event Calendar

m-Power Demo and Training Schedule

Back to Resources

Calendar Legend
Both Prospects and Customers
m-Power Customers
m-Power Prospects
Would you like to learn more about m-Power, see it in action, or get introduced to new enhancements? Join one of our scheduled events! We hold regular demos, training sessions, and webinars geared to help you understand m-Power and its capabilities. Each event is color-coded to indicate whether it's geared at m-Power users, m-Power prospects, or both. Hover over any event to learn more, and click "Register" if you'd like to participate in that event.

Of course, custom demos are available upon request. Complete this form if you would like to see a demo customized to your needs or company.

StatementCallback; SQL [SELECT T01.`EVENTID`, T01.`EVENTTITLE`, T01.`EVENTDESC`, T01.`EVENTDATE`, (T01.`EVENTDATE`) , T01.`EVENTTIME`, T01.`EVENTTYPE`, T02.`HEXCODE`, T01.`EVENTEND`, T01.`Timezone`, YEAR(T01.`EVENTDATE`)*10000 + MONTH(T01.`EVENTDATE`)*100 + DAY(T01.`EVENTDATE`) AS JIANHUA2 FROM WEBSITE.`EVENTS` T01 left outer join WEBSITE.`EVENTTYPES` T02 ON T01.`EVENTTYPE`=T02.`EVENTTYPES` WHERE (YEAR(T01.`EVENTDATE`)*10000 + MONTH(T01.`EVENTDATE`)*100 + DAY(T01.`EVENTDATE`) BETWEEN 20240225 AND 20240406) ORDER BY T01.`EVENTID` ASC limit 10000]; The last packet successfully received from the server was 145,968,521 milliseconds ago. The last packet sent successfully to the server was 145,968,526 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.; nested exception is com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 145,968,521 milliseconds ago. The last packet sent successfully to the server was 145,968,526 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.