Hello, I am deploying Frefrontbthrough a Task Sequence and after 282 machines sucessfully deployed I have one machine which is showing an error in the execmgr.log: Created Process for the passed command line Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramStartedEvent { AdvertisementId = "SRV200DD"; ClientID = "GUID:9401B23C-7D90-4CA3-9F72-2C781826F161"; CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\TSLauncher.exe\""; DateTime = "20100629222518.332000+000"; MachineName = "VOPITPMO1"; PackageName = "SRV0008B"; ProcessID = 2452; ProgramName = "*"; SiteCode = "SRV"; ThreadID = 5412; UserContext = "NT AUTHORITY\\SYSTEM"; WorkingDirectory = "C:\\WINDOWS\\system32\\"; }; Raised Program Started Event for Ad:SRV200DD, Package:SRV0008B, Program: * M Execution Manager timer has been fired. Program exit code 87 Looking for MIF file to get program status Script for Package:SRV0008B, Program: * failed with exit code 87 smsts.log GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 6/29/2010 3:35:19 PM 6064 (0x17B0) Error getting package location and access account information. Code 0x80070057 TSLauncher 6/29/2010 3:35:19 PM 6064 (0x17B0) Error initializing TS environment. Code 0x80070057 TSLauncher 6/29/2010 3:35:19 PM 6064 (0x17B0) Task sequence launcher advertisement failed!. Code 0x80070057 TSLauncher 6/29/2010 3:35:19 PM 6064 (0x17B0) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSLauncher 6/29/2010 3:35:19 PM 6064 (0x17B0) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/29/2010 3:35:19 PM 6064 (0x17B0) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/29/2010 3:35:19 PM 6064 (0x17B0) What is exactly means? Any other log file to check? The error is showing every 10 minutes... Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

This error code is being raised by the FCS install and simply being returned by ConfigMgr. You must examine the FCS installer log files to see what's going on. These should be in the Forefront installation directory.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hi Jason, on the Forefront server or on the Forefront Client? On the Client nothing is arrived...no folder for Forefront... let me check if the Forefront server has anything... It seems it is not Forefront as the first task of the task sequence is the removal of SOPHOS and it has not been done either!!! Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

The FCS server shouldn't have anything as it doesn't even know anything about the client yet. What's in smsts.log?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Hello, one full set of smsts.log: Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Error getting package location and access account information. Code 0x80070057 TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Error initializing TS environment. Code 0x80070057 TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Task sequence launcher advertisement failed!. Code 0x80070057 TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/29/2010 4:45:27 PM 4268 (0x10AC) Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Error getting package location and access account information. Code 0x80070057 TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Error initializing TS environment. Code 0x80070057 TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Task sequence launcher advertisement failed!. Code 0x80070057 TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002 TSLauncher 6/29/2010 4:55:28 PM 2080 (0x0820) Thanks,Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 Support

Was this issue ever resolved? I have serveral workstations containing the same errors. It appears that the failure may involve WMI...

Same question, what's in your smsts.log?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

no time to work on this now... I will reopen the thread if I am getting a new error Thanks, DOmSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

TS LOGS: Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Error getting package location and access account information. Code 0x80070057 TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Error initializing TS environment. Code 0x80070057 TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Task sequence launcher advertisement failed!. Code 0x80070057 TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle. Error code 0x80070002 TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSLauncher 12/30/2010 1:00:01 AM 3628 (0x0E2C) Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) GetPrivateProfileString() failed to get SMS Client GUID from file. Code 0x00000000 TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) Error getting package location and access account information. Code 0x80070057 TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) Error initializing TS environment. Code 0x80070057 TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) Task sequence launcher advertisement failed!. Code 0x80070057 TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle. Error code 0x80070002 TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSLauncher 12/30/2010 1:10:02 AM 5580 (0x15CC) EXECMGR LOGS: Mandatory execution requested for program * and advertisement R0520163 execmgr 12/30/2010 1:00:00 AM 5608 (0x15E8) Creating mandatory request for advert R0520163, program *, package R05001A3 execmgr 12/30/2010 1:00:00 AM 5608 (0x15E8) Execution Request for package R05001A3 program * state change from WaitingDependency to WaitingDependency execmgr 12/30/2010 1:00:00 AM 5608 (0x15E8) CExecutionRequest::Service Windows Manager has allowed us to run. execmgr 12/30/2010 1:00:00 AM 5608 (0x15E8) Executing program in Admin context execmgr 12/30/2010 1:00:00 AM 5608 (0x15E8) Execution Manager timer has been fired. execmgr 12/30/2010 1:00:00 AM 3448 (0x0D78) Execution Request for package R05001A3 program * state change from WaitingDependency to NotifyExecution execmgr 12/30/2010 1:00:00 AM 5608 (0x15E8) Executing program as a task sequence. execmgr 12/30/2010 1:00:00 AM 5608 (0x15E8) Successfully prepared command line "C:\WINDOWS\system32\CCM\TSLauncher.exe" execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Command line = "C:\WINDOWS\system32\CCM\TSLauncher.exe", Working Directory = C:\WINDOWS\system32\ execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Created Process for the passed command line execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramStartedEvent { AdvertisementId = "R0520163"; ClientID = "GUID:5919B171-F2E9-44D7-84E1-xxxxxxxxxx"; CommandLine = "\"C:\\WINDOWS\\system32\\CCM\\TSLauncher.exe\""; DateTime = "20101230070001.021000+000"; MachineName = "xxx-xx-xxxxxxxx"; PackageName = "R05001A3"; ProcessID = 2320; ProgramName = "*"; SiteCode = "xxx"; ThreadID = 5608; UserContext = "NT AUTHORITY\\SYSTEM"; WorkingDirectory = "C:\\WINDOWS\\system32\\"; }; execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Raised Program Started Event for Ad:R0520163, Package:R05001A3, Program: * execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Program exit code 87 execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Looking for MIF file to get program status execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Script for Package:R05001A3, Program: * failed with exit code 87 execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistWarningProgramErrorEvent { AdvertisementId = "R0520163"; ClientID = "GUID:5919B171-F2E9-44D7-84E1-xxxxxxxxxxxx"; DateTime = "20101230070001.646000+000"; ExitCode = "87"; MachineName = "xxx-xx-xxxxxxxxx"; PackageName = "R05001A3"; ProcessID = 2320; ProgramName = "*"; SiteCode = "xxx"; ThreadID = 5608; UserContext = "NT AUTHORITY\\SYSTEM"; }; execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Raised Program Error Event for Ad:R0520163, Package:R05001A3, Program: * execmgr 12/30/2010 1:00:01 AM 5608 (0x15E8) Execution is complete for program *. The exit code is 87, the execution status is FailureRetry execmgr 12/30/2010 1:00:01 AM 3448 (0x0D78) Non fatal execution error 0x80008100 encountered for program * execmgr 12/30/2010 1:00:01 AM 3448 (0x0D78) Program * has been tried 1 times, will retry later execmgr 12/30/2010 1:00:01 AM 3448 (0x0D78)

This really should be another thread as I think this are different issues. But ... Error code 87 = "The parameter is incorrect." This is being returned by whatever command-line is being run in your program and may be subject to the author of that executable. ConfogMgr simply runs the command-line you tell it to in the program and this error code was the result.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

The parm is a call to a default TS action (System Reboot). This only occurs on some workstations therefore it is not the result of incorrect syntax.

Someone at the beginning of the thread mentioned this appears to be WMI. We are running into the same error on some systems during XP to Win7 migration and I agree that it is likely WMI. In our case since we're blowing away the XP install and bringing the system to Windows 7 we are simply rebuilding the repository and this resolves the issue (client takes a few mins to repair itself after the WMI rebuild). If the system was going to stay XP I would do a WMIDIAG and see what that brings and do some real troubleshooting (rebuilding the WMI repository is not recommended by Microsoft).