Shulou(Shulou.com)06/02 Report--

SharePoint Health Analyzer is an excellent tool for SharePoint administrators responsible for managing SharePoint internal deployment installations. This feature not only helps resolve server failures and service failures, but also provides tips on how to resolve the problem. Overall, I find this feature very helpful. However, in some cases, errors and warnings in the health analyzer may be completely false and must be ignored. Low disk warning seen on the SharePoint server. These are particularly common on SharePoint servers running in virtual environments. What is interesting about this warning is that even if your hard drive uses only 1% of the disk space, the health analyzer may still warn you of the risk of insufficient free space. Therefore, the following warning can be seen even on a newly installed SharePoint server.

# 1 Health Analyzer warning message

The warning message you see in Health Analyzer is:

"Drives are at risk of running out of free space."

SPTimerService (SPTimerV4) failed service warning message

# 2 how does Health Analyzer calculate low disk space?

To understand the low disk warning, we need to see how the health analyzer calculates low disk space. According to the instructions in the above warning message, SharePoint calculates a lower disk space based on physical memory. The explanation of the warning states that "the free drive space is less than five times the physical memory value." This is dangerous because it does not provide enough space to store continuously running memory. It can also cause problems with virtual memory swap files. "

Note: the operating system uses a page file (also known as a swap file) on a Windows computer as if it were RAM. No matter how much RAM is installed on the system, every Windows computer uses a page file. Pagefile.sys is a hidden file that is stored by default in the root directory of drive C.

The same is true of most 99% of customers running SharePoint in a virtual environment. The typical drive size of the Windows Server hosting the SharePoint Server installation is about 100 GB, and the standard installation of all Windows updates uses approximately 25-30GB, depending on the number of RAM (which affects the size of the page file) and the application installed. Therefore, if the available disk space on the 100GB drive is 75GB and you have allocated the RAM of 16GB to the SharePoint server, you will still receive the above warning for the following reasons:

16GB RAM x 5 = 80GB. You will see a low disk space warning when disk space is less than 80GB (for example, 79GB).

# 3 warning!

Insufficient server disk space can have disastrous consequences and may cause the server to crash. Just because health analyzer warnings about insufficient disk space can often be deceptive, you should not always ignore this warning. This is why I do not recommend deleting warning messages. Make sure that you pay close attention to the available disk space on all servers and take appropriate action immediately.

The following is how to handle memory dump settings in Windows clients and servers. This may not apply to everyone, but I turned off the memory dump on the server. These are the memory dump settings I use on all clients and workstations on my network. At least I recommend customers to make these same settings. First, let's look at the default memory dump settings.

This screenshot is from the Windows Server 2016 data Management Center, this version of SharePoint Server 2016 Enterprise. Notice that the default time for displaying the list of operating systems is set to 30 seconds, and the memory dump is set to automatic memory dump.

The following options allow you to configure memory dumps. A small memory dump creates a limited dump of the 256KB memory contents. Kernel memory dumps are limited to operating system kernel memory dumps, and a complete memory dump performs a full memory dump of everything in system memory. Automatic memory dump is the default setting. Setting this option to none turns off memory dumps.

Usually choose to disable memory dump, the main reason is that you do not intend to use it, if you encounter a system crash, or even do not restart, you will not be able to change the settings and create a dump file. So far, I haven't come across a situation where I really need to debug files that are too bad. If my SharePoint server crashes, we can rebuild it from scratch, and if not more, I may recompile it two or three times until I need to debug the memory dump.

If I have to send the debug file to the supplier, it may take several days to get the answer. If they don't have a solution, they may not be able to solve my problem. Because the SharePoint data is stored in SQL Server, it is not too difficult to rebuild SharePoint as long as you have a SQL Server database.

This is what we often say to make sure your SQL Server is clustered, EPS (Uninterruptible Power supply), and SQL databases are backed up frequently. The same parameters apply to domain controllers (DC). I always have two or more DC on my network and back up my Active Directory (AD) database every day.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.