Task Sequence failing
Hello, I have tested individually the Run Command Line and Install Software items outside of the Task Sequence. Both run fine. When I create a task sequence with a Run Command Line (\\SCCM Server Name \Source Files\Packages\test.cmd it fails with an access denied: quote:The task sequence execution engine failed executing the action (Uninstall SOPHOS) in the group () with the error code 2147942405 Action output: =======================[ smsswd.exe ] ======================= PackageID = '' BaseVar = '', ContinueOnError='' SwdAction = '0001' Working dir 'not set' Executing command line: Run command line CreateProcess failed. Code(0x80070005) Command line execution failed (80070005) Failed to execute command line '\\CONFIGMGRDTS\C$\Source Files\Packages\SOPHOS\Sophos_Uninstall.cmd' . Permissions on the requested may be configured incorrectly. Access is denied. (Error: 80070005; Source: Windows) Install Software failed to run command line, hr=0x80070005. The operating system reported error 2147942405: Access is denied. I verified under: System Center Configuration Manager > Site Database > Site Management > Site > Site Settings > Accounts there is an account defined as "Network Access Account, Client Push Installation" This account is in a group which is member of the Local Administrators Group on the machine. Any other steps to verify? Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
March 23rd, 2010 2:38am

Hello, Some logs from execmgr.log: Policy deleted for advertisement DTS20091 package DTS0004C program xxxx - Forefront Installation execmgr 3/22/2010 5:01:04 PM 1244 (0x04DC) Policy deleted for advertisement DTS20091 package DTS00053 program * execmgr 3/22/2010 5:01:04 PM 1244 (0x04DC) Mandatory execution requested for program * and advertisement DTS20092 execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Creating mandatory request for advert DTS20092, program *, package DTS00053 execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Policy arrived for child program xxxx - Forefront Installation execmgr 3/22/2010 5:01:04 PM 1244 (0x04DC) The created request is a Task Sequence request execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Execution Request for package DTS00053 program * state change from NotExist to WaitingDependency execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Requesting content from CAS for package DTS0004C version 7 execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Successfully created a content request handle {7C696FD0-9F31-4115-A89E-65FDBC3A96DE} for the package DTS0004C version 7 execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistWaitingContentEvent { AdvertisementId = "DTS20092"; ClientID = "GUID:A68FC566-77D2-4784-A3BE-6D1667444223"; DateTime = "20100323000104.886000+000"; MachineName = "OPPMCCS6090AA"; PackageName = "DTS0004C"; PackageVersion = "7"; ProcessID = 412; ProgramName = "xxxx - Forefront Installation"; SiteCode = "DTS"; ThreadID = 2760; }; execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Successfully raised SoftDistWaitingContentEvent event for member program xxxx - Forefront Installation execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Execution Request for package DTS00053 program * state change from WaitingDependency to WaitingContent execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Policy arrived for parent package DTS00053 program * execmgr 3/22/2010 5:01:04 PM 1244 (0x04DC) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramOfferReceivedEvent { AdvertisementId = "DTS20092"; ClientID = "GUID:A68FC566-77D2-4784-A3BE-6D1667444223"; DateTime = "20100323000104.964000+000"; MachineName = "OPPMCCS6090AA"; ProcessID = 412; SiteCode = "DTS"; ThreadID = 1244; }; execmgr 3/22/2010 5:01:04 PM 1244 (0x04DC) Content is available for program *. execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Execution Request for package DTS00053 program * state change from WaitingContent to WaitingDependency execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) CExecutionRequest::Overriding Service Windows as per policy. execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Execution Request for package DTS00053 program * state change from WaitingDependency to NotifyExecution execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Notify user mandatory program * is about to run execmgr 3/22/2010 5:01:04 PM 2760 (0x0AC8) Executing program in Admin context execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Execution Request for package DTS00053 program * state change from Running to NotifyExecution execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Execution Manager timer has been fired. execmgr 3/22/2010 5:01:57 PM 1780 (0x06F4) Executing program as a task sequence. execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Successfully prepared command line "C:\WINDOWS\system32\CCM\TSLauncher.exe" execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Command line = "C:\WINDOWS\system32\CCM\TSLauncher.exe", Working Directory = C:\WINDOWS\system32\ execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Created Process for the passed command line execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramStartedEvent { AdvertisementId = "DTS20092"; ClientID = "GUID:A68FC566-77D2-4784-A3BE-6D1667444223"; CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\TSLauncher.exe\""; DateTime = "20100323000157.340000+000"; MachineName = "OPPMCCS6090AA"; PackageName = "DTS00053"; ProcessID = 412; ProgramName = "*"; SiteCode = "DTS"; ThreadID = 2124; UserContext = "NT AUTHORITY\\SYSTEM"; WorkingDirectory = "C:\\WINDOWS\\system32\\"; }; execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Raised Program Started Event for Ad:DTS20092, Package:DTS00053, Program: * execmgr 3/22/2010 5:01:57 PM 2124 (0x084C) Getting member download locations for program xxxx - Forefront Installation package DTS0004C execmgr 3/22/2010 5:01:57 PM 1244 (0x04DC) A request is currently running, software distribution requests will be paused when this program completes execmgr 3/22/2010 5:01:58 PM 1240 (0x04D8) Program exit code 0 execmgr 3/22/2010 5:01:58 PM 1764 (0x06E4) Looking for MIF file to get program status execmgr 3/22/2010 5:01:58 PM 1764 (0x06E4) Script for Package:DTS00053, Program: * succeeded with exit code 0 execmgr 3/22/2010 5:01:58 PM 1764 (0x06E4) Execution is complete for program *. The exit code is 0, the execution status is Success execmgr 3/22/2010 5:01:58 PM 1780 (0x06F4) The task sequence DTS00053 was successfully started. See SMSTS.LOG for more details. execmgr 3/22/2010 5:01:58 PM 1780 (0x06F4) Execution Request for package DTS00053 program * state change from Running to Completed execmgr 3/22/2010 5:01:58 PM 1780 (0x06F4) Policy is updated for Program: xxxx - Forefront Installation, Package: DTS0004C, Advert: DTS20092 execmgr 3/22/2010 5:01:59 PM 1240 (0x04D8) Creating mandatory request for advert DTS20092, program xxx - Forefront Installation, package DTS0004C execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) CExecutionRequest::Overriding Service Windows as per policy. execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Executing program FFCS.bat in Admin context execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Execution Manager timer has been fired. execmgr 3/22/2010 5:01:59 PM 1780 (0x06F4) Execution Request for package DTS0004C program xxxx - Forefront Installation state change from NotExist to NotifyExecution execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Checking content location \\CONFIGMGRDTS.AD.xxxxxxx.xxxx.xxx\SMSPKGD$\DTS0004C\ for use execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Successfully selected content location \\CONFIGMGRDTS.AD.xxxxxxx.xxxx.xxx\SMSPKGD$\DTS0004C execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) GetFileVersionInfoSize failed for file \\CONFIGMGRDTS.xxxxxxx.xxxx.xxx\SMSPKGD$\DTS0004C\FFCS.bat, error 1812 execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Executing program as a script execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Invalid executable file FFCS.bat execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramBadEnvironmentMomEvent { AdvertisementId = "DTS20092"; ClientID = "GUID:A68FC566-77D2-4784-A3BE-6D1667444223"; CommandLine = "FFCS.bat"; DateTime = "20100323000159.933000+000"; DriveLetter = ""; MachineName = "OPPMCCS6090AA"; PackageName = "DTS0004C"; ProcessID = 412; ProgramName = "xxxx - Forefront Installation"; SiteCode = "DTS"; ThreadID = 1244; Win32ErrorCode = 2147942402; WorkingDirectory = ""; }; execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Raised Program Bad Environment Mom Event for Ad:DTS20092, Package:DTS0004C, Program: xxxx - Forefront Installation execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) EnterRsRuningState failed to run script FFCS.bat 0x80009106 execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) CreateMandatoryRequestRecursively xxxx - Forefront Installation failed at EvaluateRequestForExecution execmgr 3/22/2010 5:01:59 PM 1244 (0x04DC) Policy is updated for Program: xxxx - Forefront Installation, Package: DTS0004C, Advert: DTS20092 execmgr 3/22/2010 5:02:09 PM 2124 (0x084C) Thanks,DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2010 3:07am

Hello, No I did not try another share as all Source files are always stored under this admin share... I will try a shot... \\CONFIGMGRDTS\C$ is an admin share and the account AD\SVCCONFIGMGRDTS is in an AD Group (which contains all SCCM Accounts - Machine mames like CONFIGMGRDTS, Service accounts AD\SVCCONFIGMGRDTS like etc...) member of the Local Administrators Group... Is it this account AD\SVCCONFIGMGRDTS which is really use to access the share? It is the account defined under: System Center Configuration Manager > Site Database > Site Management > Site > Site Settings > Accounts there is an account defined as "Network Access Account, Client Push Installation" The TS is able to run by itself as it is a script which is already used through Distribution Package but I wanted to concatenate several commands and packages in one TS to avoid all manual launching for each itme itslef. anything special? Thanks, Dominique System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
March 23rd, 2010 7:01am

- your initial answer refers to "Sophos_Uninstall.cmd", the logfile to "FFCS.bat", so they are not related at all. IOW the logfile is useless - using \\CONFIGMGRDTS\C$ as the source for a TS script is not security best practise. I would create a custom share that contains script like that. Why are you using an UNC path to run the script from and why didn't you distribute it to DPs? - Client push installation is just used for ... guess what? ... client push installations (a ConfigMgr task to install the ConfigMgr client itself). It's never used in software distribution scenarios. The network access account comes into play when talking about software distribution: http://technet.microsoft.com/en-us/library/bb680398.aspx - the network access account does not have to be a member of the local admins on the siteserver
Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2010 10:48am

Hello, - "Sophos_Uninstall.cmd" and "FFCS.bat" are members of the Task Sequence which is failing. - I changed \\CONFIGMGRDTS\C$ to \\CONFIGMGRDTS\Packages and it seems working I need to check again this morning, ... it is failing on the FFCS.BAT I will open a new thread for it. - "Why are you using an UNC path to run the script from and why didn't you distribute it to DPs?" just because it was the path to the Run Command I will check again as I did not see any DP optrion on the task sequence using Run Command Line. - got it... - "The network access account comes into play when talking about software distribution: http://technet.microsoft.com/en-us/library/bb680398.aspx" I will review this as I saw a thread asking to confirm the NAC was in place for a Task Sequence... Thanks,DomSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
March 23rd, 2010 5:05pm

Hello, The command line seems working now with the new share... The next step which is the FFCS.bat item package is failing... An error occurred while preparing to run the program for advertisement "DTS20094" ("DTS0004C" - "UCLA - Forefront Installation"). The operating system reported error 2147942402: The system cannot find the file specified. Additional program properties: Command line: FFCS.bat Working directory: Drive letter (? = any): Possible cause: This message most commonly occurs when the program's command-line executable file could not be found, when a required drive letter connection to a distribution point could not be established, or when the program is configured to use the SMS Software Installation Account but the account is not specified, could not be found, or does not have the appropriate permissions. Solution: Check each of the items listed above. Reviewing why it works as a Distribution package and not through the task sequence? Then I updated the DP after changing the folder so it corrects the previous error and now: quote:The program for advertisement "DTS20095" failed ("DTS0004C" - "UCLA - Forefront Installation"). A failure exit code of 2 was returned. User context: NT AUTHORITY\SYSTEM Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 2 is considered a failure. Solution: For more information on the exit code, refer to the documentation for the program you are distributing. Within the options on the advertisement for the task sequence what is the one to be chosen, why? - Download content locally when needed by running task sequence - Download all content locally before starting task sequence - Access content directly from distribution point when needed by the running task sequence Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2010 9:28pm

Again: why do you run those batches using a UNC path? Just puth them in a package, distribute it to DPs and use "run in ... package": http://technet.microsoft.com/en-us/library/bb632992.aspx. Or just create a program (that calls the .bat) and use http://technet.microsoft.com/en-us/library/bb632474.aspx.
March 23rd, 2010 10:18pm

Now it works... Several points were missing: 1. the folder x86 was not correctly spelled!!! 2. the .bat was still calling a package used in test TSTxxxx instead of DTSxxxx This is showing that to transfer from Test to Prod it is not as easier as it seems :) packages do not get the same numbers depending on the servers, the prefix is different, the architecture is different, etc... Thanks everybody, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
Free Windows Admin Tool Kit Click here and download it now
March 23rd, 2010 10:47pm

Hello, It works for three servers and now 0x80091007 error on the next two... As it is a hash problem where could I checked the hash numbers used ... in the SMSTS.log I have the two hashes in conflict. The one on the DP is the Downloaded but where is the original? I am starting a new thread... Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support
March 24th, 2010 1:25am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics