Rabbit MQ Error

Hello ​@asingh Try with Restarting Service if you using Windows system.

Hi ​@Abhishek Niikam thanks for reaching out. Any ideas on the root cause, or a fix?

Thanks

Amit

common cause:

• Sometime Service is not running properly on windows
• After upgrade or server restart may cause this 
• or too many notification multiple times may cause stop service or crash.

if it showing frequently then you need to check & verify URL in  Email Preferences screen & configuration on the Process Push Notifications screen.

You can try with updating RabbitMQ or Uninstall and reinstall it.

Thanks, I’ll look into it.

Amit

Hi ​@asingh,
Please check This post for the same.
As a fix you need check the status of the RabbitMQ service in the Services application.
If it is not running, please try restarting the service and ensure it starts successfully.
 

Hello ​@asingh 

AC-330733: In some cases, the system unexpectedly restarted due to an inability to connect to RabbitMQ. When a user attempted to log in, the following error message could appear: An exception was thrown while activating PX.RabbitMQClient.PushNotifications.NotificationProducer.

The issue reported is now fixed in our 2025 R1 GA  (25.100.0054) and later.

The build is available for download on Community: https://community.acumatica.com/supported-releases-67/acumatica-2025-r1-ga-build-25-100-0054-29520

and Amazon  https://builds.acumatica.com/?prefix=builds/25.1/25.100.0054/

https://community.acumatica.com/supported-releases-67/acumatica-2025-r1-downloads-and-release-notes-29519

​@DipakNilkanth thanks for reaching out. I’ll look into it.

Thanks

Amit

​@pallikasharma11 thanks for reaching out. I am currently on 25R1 25.101.0153 however this was a direct upgrade from 24R1 24.114.0020, I am not sure if that makes any difference.

Thanks

Amit

Thank you everyone for reaching out. I’ve been monitoring the application today (16th Feb 2026) and the issue has not occured as yet. It usually happened between 11am and 1pm. Currently it is 1:35pm and the application is functioning. I will continue to monitor the rest of the week to see if it reoccurs.

Thanks again to everyone for reaching out.

Amit

Hi All

I was looking at my installation setup today because the issue occured again. I noticed that although I upgraded the Acumatica application from 24R1 to 25R1, the Erlang OTP and RabbitMQ installations stayed on the versions that were installed with the 24R1 version (RabbitMQ 3.9.11 and Erlang 24). In a test environment, I deployed 25R1 and found that the RabbitMQ version was 3.13.5 and Erlang OTP version was 26.2.5.12.

I figure with Server updates from Microsoft, the older versions of RabbitMQ and Erlang may start to behave a bit buggy (I’m actually hoping and praying that this just may be the reason) and would need to be updated to supported versions.

My question is there a way to safely and cleanly uninstall the old versions associated with 24R1 and have the versions associated with 25R1 installed without major impact on my production environment, please?

Thanks

Amit

Hey Amit,
I pulled RabbitMQ’s upgrade notes there seems to be a few different upgrade paths depending on what version your MQ’s are on, hope this helps! I’m curious if there’s Acumatica Documentation that suggests RabbitMQ is standalone upgrades, am sort of surprised it isn’t upgraded when ACU is, but also not entirely unexpected either.
Upgrading RabbitMQ | RabbitMQ

​@MissyMain41 Thanks for this, I’ll take a look. It’s weird that you upgrade the application but the dependencies are not upgraded, surely they have to consider version compatability and lifecycles.

I was actually hoping to use the Acumatica installer to have it done, both Erlang and RabbitMQ installers I figure are built in and can be extracted. I just need a safe, clean path to have it done.

Thanks

Amit

I completely agree, when ACU is upgraded so too is the device hub and report designer (external from the main ACU site), so perhaps this RabbitMQ not performing an upgrade is worth a case to ACU support