This article was previously published under Q273653
This article has been archived. It is offered "as is" and will no longer be updated.
When you are using the System Monitor "Alert" feature to call a batch (.bat) or .cmd file, the available memory may be slowly depleted, total handles may climb steadily, and CPU utilization may become high. This may appear to be a memory or handle leak.
This problem can occur because the Smlogsvc.exe tool consumes memory and object handles each time an alert is triggered and a .bat or .cmd file is called. The memory and handles are not released until that alert is stopped.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name ------------------------------------------------------- 10/06/2000 4:27pm 5.0:2195.2432 88,848 Smlogsvc.exe
To work around this problem, use either of the following methods:
Use the Microsoft Windows NT 4.0 Performance Monitor, Perfmon4.exe.
Stop, and then restart the alert to free the memory and handles that are already taken. Note that doing so does not stop future consumption of resources.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes