Jump to content

Search the Community

Showing results for tags 'wizard is already running'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. I have an issue that follows me around and pops up at arbitrary times. I can have a task sequence working great for months, then make some changes and get this issue to "pop" out of nowhere. The issue is that the task sequence will try to start over on itself for no reason and it can always be narrowed to a custom script or app install (but not always the same one). The error in the smsts log is "Another task sequence wizard is already running." In the smsts.log the behavior is that after something executes, all of a sudden TSMBootStrap.exe fires up out of nowhere, ruining the in-flight sequence. Here's an excerpt of the failure from smsts.log. For context, all this batch script does is run RunDLL32.exe and load some registry keys from an .inf file. I know this is but one way to load registry keys, it happens to be a holdover from some previous deployments. Point is, it works fine, and just happens to be "the one" that caused an issue this time. Other scripts AND app installs arbitrarily caused this in the past, and I don't know what the trigger is. Simply moving the script or app to a different step in the sequence is often enough to get the behavior to stop. Note that there is no script-induced reboot here, I know that can cause issues. Expand a string: cmd.exe /c %SCRIPTROOT%\Registry\Set-ClientRegistry.bat TSManager 12/30/2016 2:59:57 PM 5240 (0x1478) Expand a string: TSManager 12/30/2016 2:59:57 PM 5240 (0x1478) Start executing the command line: cmd.exe /c %SCRIPTROOT%\Registry\Set-ClientRegistry.bat TSManager 12/30/2016 2:59:57 PM 5240 (0x1478) !--------------------------------------------------------------------------------------------! TSManager 12/30/2016 2:59:57 PM 5240 (0x1478) Expand a string: WinPEandFullOS TSManager 12/30/2016 2:59:57 PM 5240 (0x1478) Executing command line: cmd.exe /c %SCRIPTROOT%\Registry\Set-ClientRegistry.bat TSManager 12/30/2016 2:59:57 PM 5240 (0x1478) ==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 12/30/2016 3:02:49 PM 4808 (0x12C8) Command line: "C:\MININT\Tools\X64\TsmBootstrap.exe" /env:SAStart TSMBootstrap 12/30/2016 3:02:49 PM 4808 (0x12C8) Current OS version is 10.0.14393.0 TSMBootstrap 12/30/2016 3:02:49 PM 4808 (0x12C8) Another Task Sequence Wizard is already running. Wait for this to complete and try again. TSMBootstrap 12/30/2016 3:02:49 PM 4808 (0x12C8) Exiting with return code 0x80004005 TSMBootstrap 12/30/2016 3:10:52 PM 4808 (0x12C8) ==========[ TsProgressUI started in process 1828 ]========== TsProgressUI 12/30/2016 3:10:52 PM 3556 (0x0DE4) Unregistering COM classes TsProgressUI 12/30/2016 3:10:52 PM 3556 (0x0DE4) Shutdown complete. TsProgressUI 12/30/2016 3:10:52 PM 3556 (0x0DE4) See what happened there? Something caused TSMBootStrap to spring up out of nowhere and ruined the sequence, which had many steps remaining. (I am not certain what is going on during the nearly 3 minutes after batch file execution attempt - that is a mystery, the file only takes a few seconds to run). The .bat file never got to finish, and never made a return code. When things are working normally I will get a Return Code 0 from the batch file execution. The actual return code here - 0x80004005 - Access Denied - is from TSMBootStrap, trying to access something and throwing this error presumably because the task sequence is already running! Thanks for reading!
  • Create New...