ESM Log size is full - How to clear

ESM log Size is full ---- How to Clear

If your getting the below error in event viewer you can follow the below steps and solve it.

Generally when we open Dell open manage console, suddenly we see that Hardware log status is showing critical and event logs are filling saying ESM log is full...

We need to clear the ESM logs regularly before it reaches 100%. However please follow the below command and procedure before clearing the logs.

Open Dell Manage console, go to logs tab.
Then select ESM logs, you will see an export option.
Export the logs and save it on local drive for future use.
Now open command prompt and Runas administrator.
Type omconfig system esmlog action=clear
Done, your logs are cleared. Come back to Dell open manage console.
Now hardware logs will show green which is normal.

:-) :-)

Comments

System Volume Information is taking more space

On one of the servers (running Windows Server 2012 R2) I faced a problem with the lack of free space on a system drive. I have cleared all resource-consuming locations ( WinSxS , TEMP directories, user profiles, outdated updates , etc.), but it didn’t have any evident effect. At last, I have found that a large part of a system disk has been occupied by System Volume Information folder. Let’s consider why we need System Volume Information folder in Windows systems, what is stored in it and how to clean up it. Note . The instructions given in this article are applicable to other Windows versions as well: Windows 10, Windows 7, Windows 8, Windows 2008 R2, Windows 2012 / 2012 R2. System Volume Information folder is in the root of each disk. System data related to system recovery and Shadow Copy Service are stored in it. By default it is hidden and only the SYSTEM has access to it. Even the administrator cannot open it and look through the contents of the folder. To view the co

The system cannot log you on due to the following error: The RPC server is unavailable

IF your login to windows 2003 and your getting the below error then do the below steps and you can login to the PC. login to any server in the same subnet. open CMD in elevated permission open registry editor go to File---------->connect to network registry type the effected server name and open it go to the below location and create a new DWORD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server Create a new key selecting Dword and name it as IgnoreRegUserConfigErrors now double click it and give a value as 1. after that do the RDP and it will work.

Sysadmin Bloggers

Search This Blog