Skip to main content
Solved

Unable to publish from customization project editor

  • 15 October 2020
  • 7 replies
  • 2143 views

KurtBauer
Jr Varsity III
Forum|alt.badge.img

We have a development environment that has many instances of Acumatica installed and in the past week or two publishing from the customization project editor no longer works.  The log window at the bottom opens and nothing is logged.  There is a warning in the windows application log for ASP.NET.4.0.30319.0.  I have included the details at the bottom.  This is happening for all 20+ versions of Acumatica installed in any application pool. 

There is a workaround to update any changes through the editor, but then publish from the customization projects list screen (SM204505).

Thanks,

Kurt Bauer

 

Event Log Details

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 10/15/2020 8:42:56 AM 
Event time (UTC): 10/15/2020 12:42:56 PM 
Event ID: 908185df7ee84a46bd4210f5c030eb43 
Event sequence: 15 
Event occurrence: 1 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/1/ROOT/XXXXXXX-2-132472393165235242 
    Trust level: Full 
    Application Virtual Path: /XXXXXXX 
    Application Path: C:\Program Files\Acumatica ERP\XXXXXXX\ 
    Machine name: XXXXXXX 
 
Process information: 
    Process ID: 21636 
    Process name: w3wp.exe 
    Account name: IIS APPPOOL\DefaultAppPool 
 
Exception information: 
    Exception type: NullReferenceException 
    Exception message: Object reference not set to an instance of an object.
   at PX.Customization.CstValidationProcess.ProcessRequest(HttpContext context)
   at ASP.controls_publish_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
 
Request information: 
    Request URL: http://localhost/XXXXXXX/Controls/Publish.aspx?compile=true&callback_id=0&suffix=77027058-5a94-4d1f-bc2e-cf01f3a4e8a2 
    Request path: /XXXXXXX/Controls/Publish.aspx 
    User host address: ::1 
    User: kurtbauer 
    Is authenticated: True 
    Authentication Type: Forms 
    Thread account name: IIS APPPOOL\DefaultAppPool 
 
Thread information: 
    Thread ID: 35 
    Thread account name: IIS APPPOOL\DefaultAppPool 
    Is impersonating: False 
    Stack trace:    at PX.Customization.CstValidationProcess.ProcessRequest(HttpContext context)
   at ASP.controls_publish_aspx.ProcessRequest(HttpContext context)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Best answer by Irina

Hughes, thank you a lot for providing a workaround!

We issued the knowledge base article related to the issue: Known issue: After an upgrade to .NET Framework version 4.8.4250, users were unable to publish a customization project from the Customization Project Editor

The same root cause is bringing another issue affecting users in the system, for more info refer to the Known issue: After an upgrade to .NET Framework version 4.8.4250, users could face an issue when the default data was not specified in a pop-up window

View original
Did this topic help you find an answer to your question?

7 replies

Hughes Beausejour
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Developer Support Team
  • 91 replies
  • October 16, 2020

It’s a known issue currently under investigation.


Hughes Beausejour
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Developer Support Team
  • 91 replies
  • October 21, 2020

As a workaround for self-hosted Acumatica instance. Modify web server file ‘Web.Config’ at the root of your Acumatica instance folder.

 

Add this key in appSettings section:

<appSettings>

    ...

    <add key="aspnet:DisableAppPathModifier" value="false" />
</appSettings>

 

For instance hosted on Acumatica SaaS service please open a support case with Acumatica.

The issue occurs with .Net version 4.8.4250. It works up to version 4.8.3752 without this workaround.


Irina
Community Manager
Forum|alt.badge.img+8
  • Acumatica Support Analyst
  • 504 replies
  • Answer
  • October 22, 2020

Hughes, thank you a lot for providing a workaround!

We issued the knowledge base article related to the issue: Known issue: After an upgrade to .NET Framework version 4.8.4250, users were unable to publish a customization project from the Customization Project Editor

The same root cause is bringing another issue affecting users in the system, for more info refer to the Known issue: After an upgrade to .NET Framework version 4.8.4250, users could face an issue when the default data was not specified in a pop-up window


Hughes Beausejour
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Developer Support Team
  • 91 replies
  • October 26, 2020

The bug is fixed in those versions which will be released soon:

  • 2019 R1 Update 22
  • 2019 R2 Update 15
  • 2020 R1 Update 13
  • 2020 R2 Update 3
  • 2021 R1 Beta

Hughes Beausejour
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Developer Support Team
  • 91 replies
  • November 5, 2020

For your information, the exact root cause has been determined:

If Microsoft .NET Framework 4.8.4250 was used on Acumatica web server, users are unable to publish a customization project from the Customization Project Editor .


  • Freshman I
  • 1 reply
  • January 25, 2021

Hello, 

I am new with this software.  How do i fix this issue?

<appSettings>

    ...

    <add key="aspnet:DisableAppPathModifier" value="false" />
</appSettings>

i cant find this in the config file. Please help.

Regards


Hughes Beausejour
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Developer Support Team
  • 91 replies
  • January 25, 2021

The appSettings element should be there. You need to insert the DisableAppPathModifier line in the text file.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings