Task Sequence error - this is a new one!

[JacobE]

So I sent out a TS last night to update 5 applications and all were successful bar one machine...heres the log file.

 

 

========================= [ smsboot.exe ] ========================= Reboot 25/06/2014 23:00:14 15132 (0x3B1C)

SMSTSRebootDelay=60 Reboot 25/06/2014 23:00:14 15132 (0x3B1C)

SMSTSRebootMessage=Your machine is being upgraded, please standby for restart. Reboot 25/06/2014 23:00:14 15132 (0x3B1C)

SMSTSRebootRequested=HD Reboot 25/06/2014 23:00:14 15132 (0x3B1C)

Process completed with exit code 0 TSManager 25/06/2014 23:00:14 17332 (0x43B4)

!--------------------------------------------------------------------------------------------! TSManager 25/06/2014 23:00:14 17332 (0x43B4)

Successfully completed the action (Restart Computer) with the exit win32 code 0 TSManager 25/06/2014 23:00:14 17332 (0x43B4)

Set authenticator in transport TSManager 25/06/2014 23:00:14 17332 (0x43B4)

Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Clear local default environment TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Updated security on object C:\_SMSTaskSequence. TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Set a global environment variable _SMSTSNextInstructionPointer=3 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Set a TS execution environment variable _SMSTSNextInstructionPointer=3 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Set a global environment variable _SMSTSInstructionStackString=0 1 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Set a TS execution environment variable _SMSTSInstructionStackString=0 1 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Save the current environment block TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Executing command line: "bcdedit.exe" TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Process completed with exit code 0 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Failed to write volume id file to disk E:. 80070013 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Failed to convert protected paths to unqiue ID. Error code 0x80070013 TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Failed to reboot the system. Error 0x(80070013) TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Failed to initialize a system reboot.

The media is write protected. (Error: 80070013; Source: Windows) TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Fatal error is returned in check for reboot request of the action (Restart Computer).

The media is write protected. (Error: 80070013; Source: Windows) TSManager 25/06/2014 23:00:16 17332 (0x43B4)

An error (0x80070013) is encountered in execution of the task sequence TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Set authenticator in transport TSManager 25/06/2014 23:00:16 17332 (0x43B4)

Task Sequence Engine failed! Code: 80070013 TSManager 25/06/2014 23:15:31 17332 (0x43B4)

**************************************************************************** TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Task sequence execution failed with error code 80070013 TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Cleaning Up. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Removing Authenticator TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Cleaning up task sequence folder TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Failed to delete directory 'C:\_SMSTaskSequence' TSManager 25/06/2014 23:15:31 17332 (0x43B4)

SetNamedSecurityInfo() failed. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

SetObjectOwner() failed. 0x80070005. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Deleting volume ID file E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Successfully unregistered Task Sequencing Environment COM Interface. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TSManager 25/06/2014 23:15:31 17332 (0x43B4)

==========[ TsProgressUI started in process 7788 ]========== TsProgressUI 25/06/2014 23:15:31 12856 (0x3238)

Unregistering COM classes TsProgressUI 25/06/2014 23:15:31 12856 (0x3238)

Shutdown complete. TsProgressUI 25/06/2014 23:15:31 12856 (0x3238)

Process completed with exit code 0 TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Successfully unregistered TS Progress UI. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Start to cleanup TS policy TSManager 25/06/2014 23:15:31 17332 (0x43B4)

End TS policy cleanup TSManager 25/06/2014 23:15:31 17332 (0x43B4)

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 25/06/2014 23:15:31 17332 (0x43B4)

GetTsRegValue() is unsuccessful. 0x80070002. TSManager 25/06/2014 23:15:31 17332 (0x43B4)

End program: TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Error executing Task Sequence Manager service. Code 0x80070013 TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Sending error status message TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Set authenticator in transport TSManager 25/06/2014 23:15:31 17332 (0x43B4)

Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs TSManager 25/06/2014 23:15:32 17332 (0x43B4)

 

 

Its such a weird one, it's saying it cannot write to the volume e: yet the applications shouldn't even be writing to E: and should all be writing to C:\

 

Anyone seen this before?

Ta

[teamfox201]

I think it creates the folder on the drive with the most space. That computer must have multiple drives or partitions where E: is bigger than C:

[JacobE]

Hi there,

Thanks for the reply, I looked into this more and found out the machine in question had a USB stick plugged in, a 16gb one and it tried writing to that (which would not be possible as we don't allow USB sticks to be written to.

 

Why it defaulted to E, I'm not sure still. C had over 200gb free on it.