none
MDT 2012 - Failed to Run Action: Install Operating System Access is Denied (Error: 0000005; Source: Windows) RRS feed

  • Question

  • Unable to deploy any image with WIM file. Vanilla or Custom Image gives the following error:

    ZTI Error – Unhandled error returned by LTIApply: invalid procedure call or argument (5)

    Litetouch deployment failed, Return code = -2147467259 0x80004005

    Failed to run action: Install Operating System.

    Access is denied (Error: 00000005; Source: Windows)

    Tried Giving Everyone Full rights to the deployment share

    Rebooted Server

    Updated Deployment Share

    Any ideas would be great!

    Thanks

    Rick


    Richard Ray

    Wednesday, July 3, 2013 6:53 PM

All replies

  • My first guess; Do you have OSInstall=YES in your customsettings.ini?

    Please upload bdd.log to internet and post link here. It will help us with further troubleshooting.

    Thursday, July 4, 2013 6:13 AM
  • hi

    Run "Update Deployment Share" and selected "Completely regenerate the boot images. I Think it will work 

    Thursday, July 4, 2013 12:04 PM
  • Are you running from WDS/PXE or from LiteTouch.vbs in full Windows?  As Michael side, will likely need to see the logs (toss up on a SkyDrive and provide the link) to further evaluate the issue.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

    Thursday, July 4, 2013 9:41 PM
    Answerer
  • out of nowhere i started receiving the same error, just after the operating system installation.  the machine reboots and bam, the red window with "access denied".  just last week everything was working fine.  desperate for some assistance.  thanks.
    Monday, August 19, 2013 3:42 PM
  • Is the MDT deployment share on a SAN? or other non-windows server?

    Press F8, and try running the imagex.exe/dism.exe /apply command manually. What errors does it give?


    Keith Garner - keithga.wordpress.com

    Wednesday, September 4, 2013 6:31 AM
    Moderator
  • We started noticing this same problem from our deployment server near the beginning of this month (09/2013), and haven't found a solution. Have you found anything to resolve your problem yet?

    Thank you.

    - Marcus Eyre

    Friday, September 13, 2013 5:44 PM
  • What does,"imagex.exe/dism.exe /apply do?
    Sunday, October 13, 2013 6:53 PM
  • When MDT applies the image to the local machine it's just a script wrapper around the command line action imagex.exe or dism.exe.  Chances are that there are permission problems on the server that are preventing image.exe or dism.exe from accessing the *.wim file. Running these commands directly should work, however if they do not then it's not an MDT problem, it's a server problem.


    Keith Garner - keithga.wordpress.com

    Monday, October 14, 2013 5:51 PM
    Moderator
  • Has anyone figured out what is causing this issue?

    We have disabled McAfee OnAccess on the MDT Workbench box, Windows Firewall is disabled, confirmed bootstrap.ini and cs.ini have to correct info, confirmed everyone group has full control of deployment share, used DART to access a command prompt to map to deployment server using same credentials in the bootstrap.ini, then successfully executed imagex /apply of the Win7 image (Imaged applied without issue). We have completely regenerated the boot images (Deleted the boot folder) and then ran update deployment share. Nothing seems to work This problem only just started this month for us. All was working fine until last week.

    Failed to run the action: Install Operating System.
    Access is denied. (Error: 00000005; Source: Windows)

    Interesting thing is the process actually applies the image and then on DISM is when it is actually failing with this error. The Applying image process gets to 100%, then DSIM.exe kicks off, then it bombs.


    djhicks

    Wednesday, October 16, 2013 8:45 PM
  • I am having the same issue listed above. 

    I have rebooted our 2012 server and regenerated the winpe boot file but still getting the error.

    I have posted all the log files here https://skydrive.live.com/#cid=57E5397C8C507949&id=57E5397C8C507949%21129

    I did try to map a drive to the share where the wim file is but I get an access denied. That's telling me I need to supply a user name and password to run the DISM.exe command manually. Until I get that solved I wanted to post this message in case someone has found an answer. 

    Any assistance in finding the answer would be greatly apprecated.


    Kris Da San Martino

    Tuesday, February 18, 2014 10:47 PM
  • Sorry, I can't view the bdd.log file on skydrive. did you mark the folder as public readable?


    Keith Garner - keithga.wordpress.com

    Wednesday, February 19, 2014 12:00 AM
    Moderator
  • https://skydrive.live.com/redir?resid=57E5397C8C507949!129&authkey=!AJDCfz7nGblrdQE&ithint=folder%2c.log

    Please try this link.


    Kris Da San Martino

    The SMSTS.log shows

    Expand a string: WinPEandFullOS TSManager 2/18/2014 1:35:48 PM 1508 (0x05E4)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 2/18/2014 1:35:48 PM 1508 (0x05E4)
    Process completed with exit code 5 TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    !--------------------------------------------------------------------------------------------! TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Failed to run the action: Install Operating System.
    Access is denied. (Error: 00000005; Source: Windows) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Sending status message . . . TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Set a global environment variable _SMSTSLastActionRetCode=5 TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Clear local default environment TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Let the parent group (Install) decides whether to continue execution TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Access is denied. (Error: 00000005; Source: Windows) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Sending status message . . . TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767) TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    **************************************************************************** TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)
    Task sequence execution failed with error code 80004005 TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)

    Wednesday, February 19, 2014 12:53 AM
  • Yes it is looks like an access denied issue but my login and full rights to that share and the files in it.

    I have tried re-applying my rights and even given "everyone" full access but it still fails at the same spot.

    Any suggestions on how to narrow down where the problem might be or what test I should try to find out what the issue might be?


    Kris Da San Martino

    Wednesday, February 19, 2014 3:28 PM
  • I found the fix.

    Here is a past from another post

    Was missing LTIBootsrap.vbs from the deployment share / scripts folder.

    Solution:

    Created new deployment share (only a temporary one) - went into the scripts folder of this share and copied the LTIBootstrap.vbs in my my deployment share.

    Tried to image again and worked perfectly.

    I found it by making the deployment copy its logs to the server while it is in process so i could see the logs as they are being created, much easier, and if you use config manager trace log tool it auto updates so you can see it produce the logs live :D.

    Hopefully this helps others in the same situation as me.

    Sean.

    After reading this post I checked my server and I was missing the vbs file.  So I created a second deployment share and moved the missing file over and it works.


    Kris Da San Martino

    • Proposed as answer by KDSM Wednesday, February 19, 2014 9:12 PM
    Wednesday, February 19, 2014 9:11 PM
  • I found the fix.

    Here is a past from another post

    Was missing LTIBootsrap.vbs from the deployment share / scripts folder.

    Solution:

    Created new deployment share (only a temporary one) - went into the scripts folder of this share and copied the LTIBootstrap.vbs in my my deployment share.

    Tried to image again and worked perfectly.

    I found it by making the deployment copy its logs to the server while it is in process so i could see the logs as they are being created, much easier, and if you use config manager trace log tool it auto updates so you can see it produce the logs live :D.

    Hopefully this helps others in the same situation as me.

    Sean.

    After reading this post I checked my server and I was missing the vbs file.  So I created a second deployment share and moved the missing file over and it works.


    Kris Da San Martino

    Yes as posted above the SMSTS.log also showed:

    The SMSTS.log shows

    Expand a string: WinPEandFullOS TSManager 2/18/2014 1:35:48 PM 1508 (0x05E4)
    Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf" TSManager 2/18/2014 1:35:48 PM 1508 (0x05E4)
    Process completed with exit code 5 TSManager 2/18/2014 1:51:00 PM 1508 (0x05E4)

    For future reference you can go to your MDT Deployment Toolkit\templates\distribution\scripts directory and copy any missing files.

    Thursday, February 20, 2014 3:12 AM
  • Thanks much for this... out of the blue my MDT 2012 server started giving the same access denied errors and sure enough the ltibootstrap.vbs was missing from my deploymentshare\scripts folder.  Once copying it back from MDT Deployment Toolkit\templates\distribution\scripts everything was back to normal.
    Tuesday, March 11, 2014 4:15 PM
  • This fixed the problem for me too :D 
    Set up the deployment server. Captured image. Did one deployment successfully.
    Then started getting the above "Access denied" error. Reset all permissions etc but nothing worked. Regenerated the boot images a hundred times. After seeing this post i checked for the LTIbootstrap.vbs file and it was missing!!! So after i copied it from the templates\scripts folder it was all working fine again!!
    Good one Microsoft - give us an access denied error message when a file goes missing on its own....!!!!

    Thank you so much to everyone who helped figure this out!!!

    Monday, April 7, 2014 2:28 AM
  • You sir, are a gentleman and a scholar.  Thank you.
    Tuesday, July 22, 2014 4:58 PM
  • 1 year later, and it happens to us. We have 5 WDS servers on 5 different subnets. Today, one of them started failing. Guess who gets to fix it? Glad I found this post or I might be chasing folder permissions all evening. Thank you!
    Thursday, February 19, 2015 12:31 AM
  • Oh yes thank god i found this post. Worked like a charm. Still couldn't fathom why the LTIBootStrap.vbs file would've gone missing though (we never ran LTILitetouch.vbs manually).

    This thread deserves to be sticky

    Friday, July 3, 2015 3:44 AM
  • Almost two years on the day and our system has the exact same problem. Took an entire day of troubleshooting and research before I found this thread. 

    Thursday, July 9, 2015 2:22 PM
  • I've been going around in circles for 24 hours banging my head against the wall with this.

    Thank you, this seems to have fixed the error. How the script went missing is a mystery but i think it may have happened whilst of was setting up DFS to our other site.

    So happy i can move on now and maybe get some sleep tonight.

    Friday, June 30, 2017 12:41 PM
  • Love you Sir <3  You just saved maybe my whole week!!!!
    Thursday, August 3, 2017 3:01 PM
  • This. Is. Wonderful.  

    Wish I would have found this 8 hours ago.  I didn't know that access denied = file is missing.

    Saturday, April 6, 2019 10:19 PM
  • This file is set to delete its self if it runs into an error:

    ' Make sure we ran something.  If not, pop up an error

    If not bFound then
    oShell.Popup "Unable to find LiteTouch.wsf needed to continue the deployment.", 0, "Script not found", 48
    iRetVal = 9981
    End if


    ' Delete ourselves

    On Error Resume Next
    oFSO.DeleteFile Wscript.ScriptFullName, true
    On Error Goto 0



    Tuesday, August 13, 2019 2:17 PM