SMSMon32.exe error not responding

[markk11]

logged into a remote Win2K server with Net Meeting. SMS installed on both machines.

When logging out I get this message "SMSMon32.exe error not responding"

We had an administrator that was getting this message when working on this server and attempting to log off.
This only happens when we log on with NetMeeting. When logging on through terminal services this does not happen.
When I logged on from MY machine I did not get this error. I logged on from his machine and got the message he got.
NOW I GET THE SAME MESSAGE when I log on from my system. This error does not occur when logging on at the console.
any help would be appreciated

 

[snyderj]

I don't know if this is the same condition or not, but...

We experienced the "smsmon32 not responding" issue heavily at a few sites, but not all stragely enough, and it was triggered by the Q327344 hotfix. We found that clicore.exe and smsapm32.exe on the devices were not of compatible versions (both should have been 4127 with SP4 HRP + Q327344).

In task manager we noticed the smsmon32 process without a smsapm32 process. The smsmon32 process loops and causes 16 bit applications (including installation programs with 16 bit compatibility) to hang until the smsmon32 process is killed.

The affected devices picked up a new version of clicore from the DCs but were unable to update smsapm32.exe through apasetup off the CAP. We don't know why, though there are unproven theories (including timing of hotfix application).

About 80% of the affected clients automatically fixed themselves in a matter of a week or so. Increasing the cliverify cycle from the 30 day default to daily seemed to help at one site but not much at another. The remaining clients were cleaned remotely using a VBS/WMI 20clicln variant.

Microsoft indicated that Q811378 should be applied before future hotfixes in order to prevent this type of issue from occurring.

 

[saidalavi]

I am working in an environemt where there is one central server and multiple primary servers. Recently noticed a problme with software distribution that once the package is created on the cntral and distributed to primary it reaches there vey slowly. Hardware upgrade was done and still the Central server is very very sluggish when the SMSEXEC service is running. Thsi is SMS 2.0 on Windows 2000 server. Actually the compressed version of the package reaches the primary but it never shows up in SMSPKGF$ folder.