Step by Step: | There are situations where you can request a more detailed log. One of these logs is the LogProfiler, using mainly to detect sluggish problems. Below the procedure for a proper generation:
Note:
The procedure must be executed in an Appserver dedicated and in exclusive mode, that is, where no other user is accessing the environment, and no Job is in execution.
- First, stop the Appserver server - Open appserver.ini file of this Server and add, in the environment section, the LogProfiler=1 command. Example:
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4cb0858d-b556-4b79-a152-da759d2f6a19"><ac:plain-text-body><![CDATA[Environment] \]></ac:plain-text-body></ac:structured-macro>
...
LogProfiler=1
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="43d8cafd-c6c0-434d-b5cd-3cae71a08b8f"><ac:plain-text-body><![CDATA[- Check whether there is, in the appserver.ini file, in the [General] section, the Consolelog=1 row. If negative, add this row. - In the Appserver folder, rename console.log file for console.bak - Restart Appserver server - Access only a routine in which sluggish is occurring - Close Smartclient - Stop Appserver service - Rename a new file console.log generated for console_lentidao.log - Restart Appserver service - Send files console_lentidao.log and console.bak so the support can evaluate
| ]]></ac:plain-text-body></ac:structured-macro> |
