2040658 - The application error cannot be logged error: SAP startup issue

The aim of this article is to specify steps on how to reset the default log traces back to the default severity values using the Config Tool application when Netweaver Administrator (NWA) is inaccessible on a 7.1 release SAP application server JAVA engine. Usually in such cases, NWA and the other Application server JAVA links fail to load with the below error:
************************************************
Get Session Callers [EXCEPTION] java.lang.Exception: Stack Trace at com.sap.engine.services.security.login.SecurityContext.getSession(SecurityContext.java:256) at com.sap.tc.logging.LogRecord.setRuntimeProperties(LogRecord.java:1336) at com.sap.tc.logging.LogRecord.<init>(LogRecord.java:167) at com.sap.tc.logging.LogRecord.<init>(LogRecord.java:117) Details: "The application error cannot be logged (log ID returned NULL). Possible reasons: logging misconfiguration or logging problem. Check location [com.sap.engine.services.servlets_jsp.client.RequestInfoServer] configuration - minimal required severity is ERROR.
************************************************

• Release Independent
• SAP NetWeaver

Deploying offline components, exit code 67, SAP SRM not starting, SAP JAVA versions, SAPJVM versions, Check if server is started, access point for the protocol is available, 1925352, 723909 jcmon, instance startup, SAP MMC, SMICM ,SAP Production ABAP R/3 ERP SRM CRM ERP PPM SEM APO XI PI PORTAL Test development QA, template Usage_Type_All_in_One log configuration default_trace, Reset to Default Configuration,  2012685 1589548 1880792 , KBA , BC-JAS-ADM-LOG , Logging , BC-JAS-ADM-ADM , Administration , How To