|
The SMS 2.0 'Backup SMS Site
Database' task that we run nightly seems to be leaving an instance of
'MMC.EXE' open each time it runs. We see it on every SMS server in our hierarchy.
We see the MMC processes in Taskman. There are no visible consoles.
Microsoft is aware of the issue are below are their
comments on this problem:
"I wanted to clear up the multiple MMC tasks on your
site server issue. First, the existence of MMC.EXE process from the time when
Backup runs does not indicate that the backup did not finish. In fact, these two
are not quite that closely related. Although the backup task does start a
MMC.EXE process indirectly, however, it goes on and finishes without this
MMC.EXE process finishing.
We do have a known problem with the multiple MMC.EXE tasks
staying on the Windows 2000 Site Server. Here is what the backup task does when
it runs:
Explanation and Fix: Aside from dumping the database and
saving files and registry the backup tasks executes the 'machinfo.bat'
out of the 'SMS\bin\i386'
directory. In this batch
'WINMSD.EXE'
is started - but
unfortunately the command line syntax of WINMSD changed from NT4 for Windows
2000. Since the Windows 2000 WINMSD.EXE doesn't understand the command line
parameters from Windows NT 4 (which is what is still in the Machinfo.Bat), it
ignores them and in the end only the MSD MMC will be started. That's the MMC
process that builds up the huge task list after a while.
To fix the problem on a Windows 2000 site server one needs
to modify the 'machinfo.bat' -
the right syntax for WINMSD is:
WINMSD.EXE \\%1 /report
%2\%3
Let me know if this helps fix the problem you are seeing.
By the way, you can always open up the task list and End Process on the 'MMC.EXE'
processes as an alternative to rebooting the server every so often.
Thank you."
|
