Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:36
From version 14.1
edited by Erik Bakker
on 2023/09/28 21:00
Change comment: There is no comment for this version
To version 16.2
edited by Erik Bakker
on 2024/02/22 12:36
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Interpreting wrapper.log on-premise
1 +advanced-advanced-monitoring-interpreting-wrapper-log-on-premise
Parent
... ... @@ -1,1 +1,1 @@
1 -WebHome
1 +Main.eMagiz Academy.Microlearnings.Legacy Functionality.WebHome
Content
... ... @@ -44,7 +44,7 @@
44 44  
45 45  One way to do so would be to stop the runtime and delete the data folder without deleting the h2 folder. That would initiate a clean restart of the runtime to alleviate the problems. In case of structural issues, you should dive into the logging and analyze the issues in more detail.
46 46  
47 -== 45. Key takeaways ==
47 +== 4. Key takeaways ==
48 48  
49 49  * The wrapper.log can be found within the folder called log under the folder data
50 50  * You can search the log with the help of tools such as Notepad++