Skip to main content
Solved

Publish customization project fails on 2025 R2,NPM build runs successfully. The same project can be published successfully on 2026 R1.

  • May 28, 2026
  • 8 replies
  • 155 views
  • Translate All
Captain II
Forum|alt.badge.img+6

We plan to enable Modern UI for users starting from 2026 R1. So I finished migration and testing on my local 2026 R1 instance, and I can publish the project normally here.

I know this is not a standard practice, but I just wanted to see how Modern UI works in a real environment. Therefore, I tried publishing this project to our online test environment(2025R2), which is a clone of our production environment (2025R2).

Strangely, the publication failed, and no additional error details were shown.
 

I tried a common workaround:

removed all Modern UI files and republished the project, and it succeeded. But after putting the Modern UI files back, the publication failed again.---This workaound does not work for me.

Then I ran NPM commands manually. Building a single screen, an entire module, or executing npm run build-dev -- --env customFolder=development all completed successfully. I could also see the updated Modern UI changes on the pages.---This is my workaournd

I have achieved my original goal of checking Modern UI performance in a real environment. However, I am curious about why the customization publish keeps failing. I want to find out the exact cause.

Best answer by ray20

It's a permissions issue, not NPM.

Both my machines use ApplicationPoolIdentity, no difference there. The difference is the install location: my local instance is on E:\Program Files and publishes fine, the server is on C:\Program Files and fails. C:\Program Files is a Windows protected folder, so the app pool account has no write permission there and the build dies silently.

Fix: changed the app pool identity to LocalSystem, recycled, publish works now.
 

Also worth noting: "npm run build-dev" is not what publish runs, so testing that proves nothing. Publish runs "npm run build --env production --env tenant=...".

 

View original

    8 replies

    Captain II
    Forum|alt.badge.img+4

    ​@ray20 Does the instance tenant name contain any special characters? We saw a similar issue earlier due to that.

    Translate
    SaiKrishnaV | https://www.linkedin.com/in/saikrishna-vaddepalli-aa67b8225
      Jr Varsity I
      Forum|alt.badge.img
      • saco86
      • Jr Varsity I
      • May 28, 2026

      Hi ​@ray20,

      It can be because the Nods JS has not installed, when creating the instance make sure it’s installed.
      Or you can run this npm run getmodules.

      Translate
        Captain II
        Forum|alt.badge.img+6
        • ray20
        • Author
        • Captain II
        • May 29, 2026

        ​@saco86 Hello, thank you. I have installed Node.js with the same version as my local computer. I ran npm run getmodules successfully before publishing my project. I also successfully ran npm run build-dev -- --env customFolder=development. After that, I could see the updated Modern UI screens correctly.  Just publishing is failed, strange.

        Translate
        Captain II
        Forum|alt.badge.img+6
        • ray20
        • Author
        • Captain II
        • May 29, 2026

        @SaiKrishnaV Thank you, but our instance and tenant names have no special characters.

        Translate
        Captain II
        Forum|alt.badge.img+4

        ​@ray20 If possible, could you please share the full error message so we can investigate further?

        Translate
        SaiKrishnaV | https://www.linkedin.com/in/saikrishna-vaddepalli-aa67b8225
          Captain II
          Forum|alt.badge.img+6
          • ray20
          • Author
          • Captain II
          • May 29, 2026

          @SaiKrishnaV This is actually the full message. I don’t have any more details. When I run npm run build-dev -- --env customFolder=development, everything is successful with no errors.
           

          This is very weird. I don’t want to waste your time. If nobody else has this same error, I will update my progress in 3 months (at that time, we plan to upgrade the online environment to 2026 R1 and try again).

          I can live with my current workaround: publish the project without MUI files, and manually run the npm commands to build them. It works fine for now.I am just curious about the root cause

          BTW
          Error when publishing any customization: npm run build failed | Community

          The above post describes almost the same issue, but did not mention the root cause.

          Translate
            Chris Hackett
            Community Manager
            Forum|alt.badge.img
            • Chris Hackett
            • Acumatica Community Manager
            • August 27, 2026

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

            Translate
            Chris ~ Let us know how we're doing: https://forms.office.com/r/xmJUdZ1QE5 - A member helped you, please *Like* their post. A member provided an answer to your question, please mark it as *Best Answer*.
            Captain II
            Forum|alt.badge.img+6
            • ray20
            • Author
            • Captain II
            • Answer
            • October 23, 2026

            It's a permissions issue, not NPM.

            Both my machines use ApplicationPoolIdentity, no difference there. The difference is the install location: my local instance is on E:\Program Files and publishes fine, the server is on C:\Program Files and fails. C:\Program Files is a Windows protected folder, so the app pool account has no write permission there and the build dies silently.

            Fix: changed the app pool identity to LocalSystem, recycled, publish works now.
             

            Also worth noting: "npm run build-dev" is not what publish runs, so testing that proves nothing. Publish runs "npm run build --env production --env tenant=...".

             

            Translate
            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