Tag: Troubleshooting

Hi Everyone, I think everyone have seen this error message at leas once. This error message can appear as on customized Acumatica screens as on standard screens as well. But what is the reason of this error and what to do with it? Explanations This error is related to screen layout. When Acumatica need to perform any of the screen automations (like, scheduling, notifications, import/export data, web-services API calls, automation steps and so on), Acumatica parse screen layout and generates in-memory screen structure based on ASPX markup. This is needed to identify how many controls, forms, grids are located on the screen, what type of controls and how can they… Read more

Hi All, Today want to speak with you about protecting your ERP from accidents. There are 2 possible way to protect you application from disaster, which are different by approach and recovery time: Disaster Recovery (DR) – involves a set of policies, procedures and tools to enable the recovery infrastructure and systems following a natural or human-induced disaster. So basically disaster recovery assumes that disaster can happen and we just need to recover it as soon as possible. Failover Protection – is automatic switching to a redundant computer server, system, hardware component or network upon the failure. Failover basically assume that stability of the system should not be affected by… Read more

Hi Everyone, Acumatica has very powerful feature to catch and logging all exceptions that that has been thrown inside the system and application code. You are able to activate it in the Application Settings section of web.config file. <add key=”EnableFirstChanceExceptionsLogging” value=”false” /> <add key=”FirstChanceExceptionsLogFileName” value=”firstchanceexceptions.log” /> If you do not change the file name, it will be available by this path: “<SiteFolder>App_Datafirstchanceexceptions.log” This log can help a lot if you get any error without stack trace, or when you getting any problem without any information in the UI. Also this log can be very useful for Acumatica support team. You need to understand that using this mechanism you will catch all exception… Read more

Hi All, What you need to check if you have any problem and you want to investigate it? Lets discuss Acumatica traces and log files/tables. The first place that you should check if you faced the issue in application is the standard Acumatica trace. Do you interesting in using PX trace from the code? Them welcome to this article. If you need you can write information to the trace direct from your code. For this task, you should use PXTrace static class. There are a lot of different auxiliary methods to write different types of events: public static void WriteError(string message) public static void WriteError(Exception e) public static void WriteWarning(string… Read more

Hi All Microsoft .Net has a very nice feature like First Chance Exception Log. You can easily use it in your Acumatica to log specific exceptions. Read more about first chance exceptions. Now I want to share with you my logger example: Logger example: View the code on Gist. To to enable this logger, you just need to put an additional file to <SitePath>App_code folder and add this line to your global.asax file: void Application_Start(object sender, EventArgs e) { ….. SessionLogger.Initialise(); ….. } Based on this idea I have created a logger that catchs “Session Expired” messages for monitoring purposes. The source code of SessionLogger is available on GitHub.