Skip to main content
Question

publishing customization from CPE fails, but works from SM204505

  • August 27, 2026
  • 4 replies
  • 30 views
J
Freshman I

i am attempting to publish a customization project on an instance running on localhost (build 26.100.0175.4) on my dev box.  if i publish from the CPE, it fails:

[2026-08-26 23:58:36.965] Validation finished successfully.

[2026-08-26 23:58:45.103] System.ApplicationException: The customization document has been changed after validation.
   at Customization.CstManager.Publish(Int32 hashCode, ICustomizationLogger logger)
   at PX.Web.Customization.Controls.Publish.DoPublish(Int32 hashCode, HttpResponse response)
[2026-08-26 23:58:45.111] An error has occurred. Please report this error to the technical support and attach the information provided above.

instance is running on a W11 box; no other users are connected, no IDE is running, only one instance of Edge is open, with the main browser open to SM204505, and the CPE window open attempting to publish.  no other customization projects are published in the instance.   the project contains no Modern UI items, and modern UI is not enabled on any screens in the instance. i’ve rebooted the workstation to insure no other processes are touching the files or database. 

if i publish from SM204505, it successfully publishes.   

interestingly, i get the same results when attempting to publish the same package on one of our test servers hosted somewhere in the sky….  publishing fails from CPE, but succeeds from SM204505.

thanks in advance for any suggestions.

    jim

 

    4 replies

    F
    Captain II
    Forum|alt.badge.img+4
    • FarhanaM60
    • Captain II
    • August 27, 2026
    • CPE version vs. Acumatica build
      • Make sure the CPE you're using is the version intended for 26.100.0175.4.
      • An older/newer CPE can sometimes validate successfully but fail when the publish request compares the customization document hash.
    • Try exporting the project and publishing the exported package
      • Export the customization project/package from the instance.
      • Create a fresh customization project/package from that export.
      • Then try publishing that through CPE.
      • This helps determine whether the problem is related to the project metadata/document itself rather than the CPE connection.
    • Try a brand-new trivial customization
      • Create a new project containing something extremely simple, e.g. a small DAC extension or screen customization.
      • Publish it through CPE.
      • If even the trivial project fails, that strongly points toward a CPE/instance compatibility issue rather than your customization.
    • Check whether CPE is modifying the package during validation

       

      The strongest diagnostic test

       

      Create a completely new, empty/simple customization project → save it → publish it using CPE.

      If that also fails: almost certainly CPE/version/client-side issue.
      If that succeeds: the issue is specific to the existing customization project's document/package.
      If an exported/reimported copy succeeds: the original project's customization document is likely carrying some metadata/state that CPE doesn't like.

       

    Farhana Mohammad
    kpopova
    Acumatica Employee
    Forum|alt.badge.img+3
    • kpopova
    • Acumatica Employee
    • August 27, 2026

    Try to search for Zero Width No-Break Space characters in your ASPX and ASPX.cs files and remove them.

    D
    Captain II
    Forum|alt.badge.img+8
    • Django
    • Captain II
    • August 27, 2026

    ​@FarhanaM60  - if you’re using AI to generate your answers, please indicate that in your post.

      KrunalDoshi
      Semi-Pro II
      Forum|alt.badge.img+6
      • KrunalDoshi
      • Semi-Pro II
      • August 27, 2026

      Hi ​@FarhanaM60,

      I would recommend first checking the exact Acumatica version/build on which the customization project was created. Make sure it matches the version/build of the instance where you are currently trying to publish the customization. Remove any spaces or special characters (if any) from your customization project name.

      If the versions are the same, I would suggest creating a new customization project, importing everything from the existing project into the new project, and then trying to publish it from the Customization Project Editor (CPE).

      Since I’m not sure what your customization contains, it’s difficult to suggest a specific solution. However, the above scenario should help determine whether the issue is related to the existing customization project itself.

      I would also recommend putting the site into Maintenance Mode and then trying to publish the customization once from CPE. This will help rule out any interference from other users or processes modifying the customization project during the validation/publishing process.

      Hope this helps!

      Krunal D - Acumatica Developer | www.linkedin.com/in/onlyleader | https://krunaldoshi.com/
      Terms & ConditionsAccessibility statement
      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