Skip to main content

I have a customization our developer created for this client.  When we publish to our internal test/dev server it validates and gets to the “Starting the Website” and just sits there and never returns the “Customization project published successfully” message.  I’ve tried multiple times and let this screen below sit there a couple minutes to as long as 30 minutes or more and never get the message.  If I close the window it appears the custom published and all customizations to screens appear to be working.

 

 

However, in the SaaS production server, when I publish it all works as expected.  In my test system everything seems to be working but would feel better if consistent behavior between test and production on this process.  Anyone ever seen this?

 

 

@kyoung14 What’s the Acumatica version? There was a bug some time ago that prevented the final message from appearing (only visual, the publishing still ends successfully)

Sorry - I should have said that.  It is 23.211.0017

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

No.  But I don’t know that I really expected one.  Every environment is a little different and I do know that there have been some bugs related to the publishing process that have been uncovered and are hopefully addressed in newer versions.

For whatever it’s worth, I sometimes encounter the same thing (23R2).  I just make sure to let it simmer for another 5 minutes or so then refresh the page.  I haven’t had it actually cause any noticeable issues.

@kyoung14 Are you possibly using Windows 11. A little while back, I had some wierd issues when I upgraded to Windows 11 but when I downgraded to Windows 10, everything become normal-ish.

Thanks for comment but no - Windows 10.

Hi All,

We encountered this error recently and found a solution for our specific case! For us, this bug showed up due to the number of customizations (and the lengths of their names) causing a 404 error.

At this stage of publishing, the customizations that are to be published are sent as a comma-separated list in the URL. We had approximately 50 active packages, some of which had long names. This took us over the URL limit of the browser, causing this error.

We are in the process of consolidating projects and shortening names to get under the 2048 character limit on the live instance, but this solution solved the problem on my local. We only discovered the issue because some low- and no-code customizations occur after this point in the publication process (e.g. custom navigation actions on “Screens” in the customization project editor).

 TLDR; There is a hidden limit to the number of customizations you can have on Acumatica! Keep your packages consolidated with short names, and use the Description and Notes fields instead.

Hope this is helpful for other people in the future, as I did not find any information about customization limits when I searched for it...

Thank you for sharing your solution with the community ​@aaronjkeeney!

Reply


Terms & ConditionsCookie settings
About Acumatica ERP system
Acumatica Cloud ERP provides the best business management solution for transforming your company to thrive in the new digital economy. Built on a future-proof platform with open architecture for rapid integrations, scalability, and ease of use, Acumatica delivers unparalleled value to small and midmarket organizations. Connected Business. Delivered.
© 2008 — 2024  Acumatica, Inc. All rights reserved