SMSMon32 Causing GPFs

[uberkaz]

I'm having a bit of a problem... I'm starting to install SMS, and everythings been going fine - Until now. I installed the client (through NDS login installation) on an IBM Thinkpad 380D. after sitting for about two minutes, The machine gives two SMSMon32 GPFs in a row. After that, the machine is alright, and can be used normally. If I skip the Novell login, I do not get the error. If I login, but don't run scripts, I don't get the error (the only other lines in the script are drive mappings).

I haven't been able to find any information on this... I'm lost.

Here's some machine information:

IBM Thinkpad 380D Laptop
80M RAM, adequate drive space
Windows 95B
Novell client (originally 3.0.1, upgraded to 3.3)
Using SMS 2.0, SP3

 

[snyderj]

Do you get a GPF when you run the Advertised Programs Monitor through Control Panel? SMSMON32.EXE is called by CCIM32 and through the control panel Advertised Programs Monitor (APM). When APM detects an advertisement it pops up a dialog asking whether to open the Advertised Programs Wizard (APW).

I'd first try to reinstall APM. The basic way to reinstall APM (sort of) is by running Systems Management through Control Panel, selecting the Components tab, then click Repair Installation.

The full reinstall can be accomplished by running SWDUnIns.exe from %windir%\MS\SMS\clicomp\SWDist32\bin to remove all APM and APW functionality. (It does not remove Control Panel icons until reboot.) If device is still assigned to CAP, and CAP is configured to require APM and APW (which it should be if you didn't change anything), then they will be reinstalled automatically after reboot.

 

[uberkaz]

This error happens on a totally fresh install, as well as a re-install. It also happens across different computers of the same model (I've tried it on four separate IBMs), but only on that model. On approximately 6 other models, everything works fine.

Since the error, I've disabled Advertisements, as we have no plans to use them yet. I'm sure that we will in the future, and I'd really like to get this resolved. Any other ideas?

 

[snyderj]

It sounds like a problem that existed in SP1 (though you're on SP3):

http://support.microsoft.com/support/kb/articles/Q238/8/65.ASP

Check you log files -- anything suspicious in smsmon32.log, swdist.log or smsapm32.log?