Skip to main content
Answer

Acumatica 2025 R2 or R1 install fails and disappears

  • October 15, 2025
  • 5 replies
  • 82 views

I am trying to install Acumatica 2025 R2 (also tried R1) on to a fresh Windows 2022 server in AWS with a MySQL 8.0.43 RDS instance for the DB. When I deploy a new instance the installer starts then the dialog just disappears. I have verified MySQL is accessible to the EC2 instance. I get the following events logged when I try any insight would be helpful:

 

Application: AcumaticaConfig.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: MySqlConnector.MySqlException
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at MySqlConnector.Core.ResultSet+<ReadResultSetHeaderAsync>d__2.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at MySqlConnector.MySqlDataReader.ActivateResultSet(System.Threading.CancellationToken)
   at MySqlConnector.MySqlDataReader+<CreateAsync>d__97.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at MySqlConnector.Core.CommandExecutor+<ExecuteReaderAsync>d__0.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at MySqlConnector.MySqlCommand+<ExecuteNonQueryAsync>d__69.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at MySqlConnector.MySqlCommand.ExecuteNonQuery()
   at PX.DbServices.Points.DbmsBase.DefaultExecutor`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].executeDbCommand(System.Data.IDbCommand, Double ByRef)
   at PX.DbServices.Points.DbmsBase.DefaultExecutor`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Execute(System.Func`1<System.Data.IDbCommand>)

Exception Info: PX.DbServices.Scripting.ScriptExecutionException
   at PX.DbServices.Points.DbmsBase.DefaultExecutor`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Execute(System.Func`1<System.Data.IDbCommand>)
   at PX.DbServices.Points.DbmsBase.PointDbmsBase.executeSingleCommand(PX.DbServices.Commands.CommandBase, PX.DbServices.Points.ExecutionContext, Boolean)
   at PX.BulkInsert.Installer.BaseInstallProvider.EnsureDatabaseHasCorrectSettingsBeforeDBWork()
   at AcumaticaConfig.Installation.DatabaseWork(PX.BulkInsert.Installer.BaseInstallProvider, AcumaticaConfig.UI.ProgressBase)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

 

Description:
Faulting application name: AcumaticaConfig.exe, version: 25.101.153.0, time stamp: 0x879f9181
Faulting module name: KERNELBASE.dll, version: 10.0.20348.3932, time stamp: 0x4c7b412e
Exception code: 0xe0434352
Fault offset: 0x000000000003f46c
Faulting process id: 0x1ee8
Faulting application start time: 0x01dc3c7e11e971b3
Faulting application path: C:\Program Files\Acumatica ERP\Data\AcumaticaConfig.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: c8a458fe-575e-42f5-a59f-0145fdbec37e
Faulting package full name: 
Faulting package-relative application ID: 

Best answer by chrisp74

Hi ​@chrisp74,

I am having much the same problem trying to install MYOB Acumatica (the Australia/New Zealand variant) on my own computer using MySQL 8.0. I got a little more information though, with the installer telling me that a query could not run because the sql_mode setting for the database included “only_full_group_by”. This seemed to stop a query that included a “group by” clause from running, presumably because the select clause included a field that wasn’t aggregated and also wasn’t included in the “group by” clause.

I was reluctant to just change the setting on the server, but I then compared the MySQL 8.0 installation to my existing MySQL 5.7 installation, and this did not have “only_full_group_by” set. The documentation states that this was only set by default starting from 5.7.5.

So I have now removed “only_full_group_by” from sql_mode on MySQL 8.0 and am running the MYOB Acumatica installer again. I’ll update when I know whether it has made a difference.

Cheers,

Ben.

 

I ended up installing MySQL 8.04 on the EC2 instance itself instead of using an RDS instance and it installed fine. I haven’t figured out the exact problem but it definitely was caused by the MySQL setup in RDS. The installer could see the RDS instance and read the DBs installed and the credentials worked so I’m not sure what was the failure point.

5 replies

benb1977
Freshman II
Forum|alt.badge.img
  • Freshman II
  • October 29, 2025

Hi ​@chrisp74,

I am having much the same problem trying to install MYOB Acumatica (the Australia/New Zealand variant) on my own computer using MySQL 8.0. I got a little more information though, with the installer telling me that a query could not run because the sql_mode setting for the database included “only_full_group_by”. This seemed to stop a query that included a “group by” clause from running, presumably because the select clause included a field that wasn’t aggregated and also wasn’t included in the “group by” clause.

I was reluctant to just change the setting on the server, but I then compared the MySQL 8.0 installation to my existing MySQL 5.7 installation, and this did not have “only_full_group_by” set. The documentation states that this was only set by default starting from 5.7.5.

So I have now removed “only_full_group_by” from sql_mode on MySQL 8.0 and am running the MYOB Acumatica installer again. I’ll update when I know whether it has made a difference.

Cheers,

Ben.

 


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • November 6, 2025

Hi ​@chrisp74 were you able to find a solution? Thank you!


  • Author
  • Freshman II
  • Answer
  • November 6, 2025

Hi ​@chrisp74,

I am having much the same problem trying to install MYOB Acumatica (the Australia/New Zealand variant) on my own computer using MySQL 8.0. I got a little more information though, with the installer telling me that a query could not run because the sql_mode setting for the database included “only_full_group_by”. This seemed to stop a query that included a “group by” clause from running, presumably because the select clause included a field that wasn’t aggregated and also wasn’t included in the “group by” clause.

I was reluctant to just change the setting on the server, but I then compared the MySQL 8.0 installation to my existing MySQL 5.7 installation, and this did not have “only_full_group_by” set. The documentation states that this was only set by default starting from 5.7.5.

So I have now removed “only_full_group_by” from sql_mode on MySQL 8.0 and am running the MYOB Acumatica installer again. I’ll update when I know whether it has made a difference.

Cheers,

Ben.

 

I ended up installing MySQL 8.04 on the EC2 instance itself instead of using an RDS instance and it installed fine. I haven’t figured out the exact problem but it definitely was caused by the MySQL setup in RDS. The installer could see the RDS instance and read the DBs installed and the credentials worked so I’m not sure what was the failure point.


benb1977
Freshman II
Forum|alt.badge.img
  • Freshman II
  • November 6, 2025

Hi ​@chrisp74,

I’m not well-versed in AWS but on a re-read of your problem and my comment I realise just how different our problems are. Both my MySQL installation and my MYOB Acumatica installation are on the same computer as opposed to yours spread across several different virtual machines in AWS.

Add to that the fact that I found that the table involved in the SQL error is specific to MYOB Acumatica - not pure Acumatica - and I’m pretty sure I added zero value to your investigation.

But still - I find value in communicating and sharing frustrations. :)

Cheers,

Ben.


  • Author
  • Freshman II
  • November 10, 2025

Hi ​@chrisp74,

I’m not well-versed in AWS but on a re-read of your problem and my comment I realise just how different our problems are. Both my MySQL installation and my MYOB Acumatica installation are on the same computer as opposed to yours spread across several different virtual machines in AWS.

Add to that the fact that I found that the table involved in the SQL error is specific to MYOB Acumatica - not pure Acumatica - and I’m pretty sure I added zero value to your investigation.

But still - I find value in communicating and sharing frustrations. :)

Cheers,

Ben.

Ben, thanks for the information and  I agree, hopefully the communication in this thread can help, or at least guide others with their issues.