I have a group of machines that all have the same base build - win xp pro sp2 (although they are used by developers so who knows what has been installed on them now). I have been deploying apps to them via sms2 sp5 (most of which are in house apps) however about half of the machines aren't running the programs. They will pick up the advert but never actually install the package.

Does anyone know of any software that may conflict with the sms client install or any other things that i can look at as to why the programs aren't running?


0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


The first thing to check would be the SMS logs under %windir%\MS\SMS\Logs. You should be able to see the steps SMS took to get to the point of failure. In most cases it's a corrupt SMS client (for lack of a better description) or some kind of permissions issue either on the client or from the client to the DP where the packages are housed. I think for advertisements the apm32.log is the one you want to look at. If you find anything, Google it or post it back here.
Answered 12/09/2005 by: yarborg
Blue Belt

Please log in to comment
I have already looked through these logs but couldn't see anything obvious. The programs aren't failing as such because they never start, the logs say that they are successfully scheduled but I can't find a reason as to why they don't start.

If I can provide any more info then let me know i.e snippets or log files.
Answered 12/09/2005 by: grayfrost
Yellow Belt

Please log in to comment
If these computers have already run the advertisement in the past they will not run again. Have you tried to rerun the advertisement? Do you use mandatory assignments?
Answered 12/21/2005 by: mickman
Orange Belt

Please log in to comment
The machines haven't run the advert before. I make sure that the programs are mandatory over slow links as this has caused problems in the past.
Answered 12/22/2005 by: grayfrost
Yellow Belt

Please log in to comment
I'm assuming that you've already checked the advertisement status?

Can you run the program manually from the control panel?
Answered 12/27/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment

I have the same problem. Have you resolved it?
Answered 01/06/2006 by: PEPE
Yellow Belt

Please log in to comment
For more details I add the event that appears in the event viewer
(Only in the stations where SMS programs don't start)

Thanks for your help.

Event Type: Error
Event Source: SMS Client
Event Category: Available Programs Manager (APM)
Event ID: 669
Date: 1/6/2006
Time: 3:39:57 PM
User: N/A
Computer: NAMEXXX
The component raised an exception but failed to handle it and will be stopped immediately.

Component name: Available Programs Manager (APM)
Executable: C:\WINDOWS\MS\SMS\clicomp\apa\Bin\smsapm32.exe
Process ID: 0x604
Thread ID: 0xa84 (Listen Thread)
Instruction address: 0x77c3f5ea
Exception code: 0xc0000005
Additional information:

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Answered 01/06/2006 by: PEPE
Yellow Belt

Please log in to comment