Hi All Two days back we deployed the windowsXPSP3 to 35 machines, only 14 machines got success, remaining machines are not successful. its showing below error message. The program for advertisement "Adv" ("Adv" - "Install SP3") exceeded the maximum allowed run time of 720 minute(s). Systems Management Server (SMS) has stopped monitoring the program, and is unable to determine the status of the program. SMS will not automatically attempt to run this program again. Possible causes: The program might have taken longer to run than expected, or the program might have experienced problems while running. Possible solution: Make sure the maximum allowed run time specified for the program allows enough time for the program to finish running. If the program requires user input, ensure the program properties allow the user to interact with the program. Program properties is below: Program can run: Whether or not a user is logged on Allow users to interact with this program Machine are online and active. please help regarding above issue.

You should examine the logs on the client to get an idea what happend (execmgr.log and the SP3 log).

hi, thats fine. let me know i have seen so many times above error. why (which situations) above error will display. what troubleshoot steps need to take care for this. thanks in advance.

Hi All, I'm testing winxpsp3 deployment on single machine. i pushed the software, advertisment status is showing received and program aslo started. after that nothing is happening. please clould u tell me the reason..if any thing is required.

Policy is updated for Program: Install - SP3, Package: AUS0002C, Advert: AUS2000F execmgr 12/13/2010 5:24:35 PM 3048 (0x0BE8) Requesting content from CAS for package AUS0002C version 2 execmgr 12/13/2010 6:24:33 PM 1980 (0x07BC) Policy arrived for parent program Test-InstallSP3 execmgr 12/13/2010 6:24:33 PM 2464 (0x09A0) Raising event: [SMS_CodePage(850), SMS_LocaleID(3081)] instance of SoftDistProgramOfferReceivedEvent { AdvertisementId = "AUS20010"; ClientID = "GUID:9D16A549-0835-474D-B46E-C1B40CC28E51"; DateTime = "20101213072433.507000+000"; MachineName = "SYD-DNMRPROD52"; ProcessID = 168; SiteCode = "AUS"; ThreadID = 2464; }; execmgr 12/13/2010 6:24:33 PM 2464 (0x09A0) Successfully submitted event to the Status Agent. execmgr 12/13/2010 6:24:33 PM 2464 (0x09A0) Program Test-InstallSP3 change to state STATE_ADVANCED_DOWNLOAD content in progress execmgr 12/13/2010 6:24:40 PM 1980 (0x07BC) Execution Request for program Test-InstallSP3 state change from NotExist to AdvancedDownload execmgr 12/13/2010 6:24:40 PM 1980 (0x07BC) Mandatory execution requested for program Test-InstallSP3 and advertisement AUS20010 execmgr 12/13/2010 6:24:40 PM 2128 (0x0850) Creating mandatory request for advert AUS20010, program Test-InstallSP3, package AUS0002C execmgr 12/13/2010 6:24:40 PM 2128 (0x0850) Raising event: [SMS_CodePage(850), SMS_LocaleID(3081)] instance of SoftDistWaitingContentEvent { AdvertisementId = "AUS20010"; ClientID = "GUID:9D16A549-0835-474D-B46E-C1B40CC28E51"; DateTime = "20101213072441.116000+000"; MachineName = "SYD-DNMRPROD52"; PackageName = "AUS0002C"; PackageVersion = "2"; ProcessID = 168; ProgramName = "Test-InstallSP3"; SiteCode = "AUS"; ThreadID = 2128; }; execmgr 12/13/2010 6:24:41 PM 2128 (0x0850) Successfully submitted event to the Status Agent. execmgr 12/13/2010 6:24:41 PM 2128 (0x0850) Successfully raised SoftDistWaitingContentEvent event for program Test-InstallSP3 execmgr 12/13/2010 6:24:41 PM 2128 (0x0850) Execution Request for program Test-InstallSP3 state change from WaitingDependency to WaitingContent execmgr 12/13/2010 6:24:41 PM 2128 (0x0850) Content is available for program Test-InstallSP3. execmgr 12/13/2010 6:26:10 PM 2728 (0x0AA8) Notify user mandatory program Test-InstallSP3 is about to run execmgr 12/13/2010 6:26:10 PM 2728 (0x0AA8) Execution Request for program Test-InstallSP3 state change from WaitingContent to NotifyExecution execmgr 12/13/2010 6:26:10 PM 2728 (0x0AA8) Executing program "WinXP SP3 Patch.EXE" in Admin context execmgr 12/13/2010 6:27:10 PM 3256 (0x0CB8) Execution Request for program Test-InstallSP3 state change from Running to Running execmgr 12/13/2010 6:27:10 PM 3256 (0x0CB8) Checking content location C:\WINDOWS\system32\CCM\Cache\AUS0002C.2.System for use execmgr 12/13/2010 6:27:10 PM 3256 (0x0CB8) Successfully selected content location C:\WINDOWS\system32\CCM\Cache\AUS0002C.2.System execmgr 12/13/2010 6:27:10 PM 3256 (0x0CB8) Executing program as a script execmgr 12/13/2010 6:27:10 PM 3256 (0x0CB8) Successfully prepared command line "C:\WINDOWS\system32\CCM\Cache\AUS0002C.2.System\WinXP SP3 Patch.EXE" execmgr 12/13/2010 6:27:10 PM 3256 (0x0CB8) Command line = "C:\WINDOWS\system32\CCM\Cache\AUS0002C.2.System\WinXP SP3 Patch.EXE", Working Directory = C:\WINDOWS\system32\CCM\Cache\AUS0002C.2.System\ execmgr 12/13/2010 6:27:10 PM 3256 (0x0CB8) Created Process for the passed command line execmgr 12/13/2010 6:27:11 PM 3256 (0x0CB8) Raising event: [SMS_CodePage(850), SMS_LocaleID(3081)] instance of SoftDistProgramStartedEvent { AdvertisementId = "AUS20010"; ClientID = "GUID:9D16A549-0835-474D-B46E-C1B40CC28E51"; CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\Cache\\AUS0002C.2.System\\WinXP SP3 Patch.EXE\""; DateTime = "20101213072711.025000+000"; MachineName = "SYD-DNMRPROD52"; PackageName = "AUS0002C"; ProcessID = 168; ProgramName = "Test-InstallSP3"; SiteCode = "AUS"; ThreadID = 3256; UserContext = "NT AUTHORITY\\SYSTEM"; WorkingDirectory = "C:\\WINDOWS\\system32\\CCM\\Cache\\AUS0002C.2.System\\"; }; execmgr 12/13/2010 6:27:11 PM 3256 (0x0CB8) Successfully submitted event to the Status Agent. execmgr 12/13/2010 6:27:11 PM 3256 (0x0CB8) Raised Program Started Event for Ad:AUS20010, Package:AUS0002C, Program: Test-InstallSP3 execmgr 12/13/2010 6:27:11 PM 3256 (0x0CB8) Execution Manager timer has been fired. execmgr 12/13/2010 6:33:21 PM 2800 (0x0AF0) Policy is updated for Program: Test-InstallSP3, Package: AUS0002C, Advert: AUS20010 execmgr 12/13/2010 9:24:34 PM 2524 (0x09DC)

your command line is just winXP SP3 patch.exe? there are no switch for silent installation? Cause maybe a dialog box is launched and wait for user interaction, and you cannot see it cause your are in admin context without allowing user to interact with this program. THis is an option in the program. Julien

your command line is just winXP SP3 patch.exe? there are no switch for silent installation? Cause maybe a dialog box is launched and wait for user interaction, and you cannot see it cause your are in admin context without allowing user to interact with this program. THis is an option in the program. Julien

Have you tried creating a collection for machines with SP2, and SUS SP3 to those machines? Also, can you post you SP3 install command line?