%11SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" has %3 KB of free space, which is less than or equal to the Warning Free Space Threshold of %4 KB. Possible cause: The transaction log is too small. Solution: Increase the size of the transaction log using SQL Enterprise Manager. Possible cause: The Warning Free Space Threshold is set too high for the transaction log. Solution: Decrease the Warning Free Space Threshold in the SMS Administrator console by navigating to the Site Hierarchy --> %5 --> Site Settings --> Status Summarizers --> Site System Status Summarizer, right-clicking Properties, selecting the Thresholds tab, and creating or adjusting the specific thresholds for the transaction log. SMS Site System Status Summarizer will now set the status of the transaction log to Warning in the Site System Status summary in the SMS Administrator console.%0
SMS Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
SMS Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
SMS Site System Status Summarizer detected that the storage object "%1" on site system "%2" has %3 KB of free storage space, ...
SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" ...
SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" ...
SMS Site System Status Summarizer detected that the transaction log for the "%1" database on SMS site database server "%2" ...
SMS Site System Status Summarizer has not been able to access the storage object "%1" on Site Object "%2" for %3 hours. SMS ...
SMS Site System Status Summarizer still cannot access storage object "%1" on site system "%2".%12 Possible cause: The site ...
SMS Site System Status Summarizer still cannot access the "%1" database on SMS Site Database Server "%2".%12 Possible cause: ...