Task Sequence Auto Apply Drivers fails - CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14
SCCM 2007 SP2 R2--
I have copied my working task sequences for Operation System Deployment (Windows 2008 R2) because I am introducing new hardware into our environment. After adding new drivers to the Boot image and to the Drivers catalog, I am now experiencing an issues
when running the TS.
In my SMSTS.log, I see these errors:
*************** SMSTS.LOG ********************************
Processing driver match result. OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
XML parsing error at line 1 char 1: Invalid at the top level of the document.
Request failed (Code 0x80040e14) OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
bSuccess == ((VARIANT_BOOL)-1), HRESULT=80004005 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,1116) OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
spXMLDoc.loadFromXML(pszResponse), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,536) OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
Server response: Request failed (Code 0x80040e14) OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
processDriverResponse( sResponseBody, fpCallbackProc, pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,457) OSDDriverClient 7/25/2012 9:48:01
AM 1296 (0x0510)
Failed to process driver catalog response. Code 0x80004005 OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
pDriverCatalog->match( deviceList, m_fpCallbackProc, m_pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,854) OSDDriverClient 7/25/2012 9:48:01
AM 1296 (0x0510)
pDriverInstaller->AutoInstallDrivers( pDriverCatalog, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,286) OSDDriverClient 7/25/2012 9:48:01 AM 1296
(0x0510)
Failed to auto provision driver. Code 0x80004005 OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
ProcessAutoProvision( pDriverInstaller, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,415) OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
Failed to auto provision drivers. Code 0x80004005 OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
Exiting with return code 0x80004005 OSDDriverClient 7/25/2012 9:48:01 AM 1296 (0x0510)
Process completed with exit code 2147500037 TSManager 7/25/2012 9:48:01 AM 1632 (0x0660)
!--------------------------------------------------------------------------------------------! TSManager 7/25/2012 9:48:01 AM 1632 (0x0660)
Failed to run the action: Post Install - Auto Apply Drivers.
Unspecified error (Error: 80004005; Source: Windows) TSManager 7/25/2012 9:48:01 AM 1632 (0x0660)
I have also checked my NLB MP's and have found this error in the MP_DriverMgr.log
********************* MP_DriverMgr.log *******************************************
CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14 MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
======================================= MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name : SERVERNAME
SQL Database Name : SMS_AM0_RPL
Integrated Auth : True
MPDB ERROR - EXTENDED INFORMATION
MPDB Method : ExecuteSP()
MPDB Method HRESULT : 0x80040E14
Error Description : Syntax error or access violation
OLEDB IID : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
ProgID : Microsoft OLE DB Provider for SQL Server
MPDB ERROR - INFORMATION FROM DRIVER
null MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
=======================================
MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14 MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
Failed to execute MatchDrivers task, hr=0x80040e14 MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
Response message sent to the client MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
Failed to execute task, hr=0x80040e14 MP_DriverManager 7/24/2012 12:47:50 PM 7436 (0x1D0C)
Executing Driver Request - Match MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
XML Schema support is not installed, XML validation will be skipped. MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14 MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
======================================= MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name : SERVERNAME
SQL Database Name : SMS_AM0_RPL
Integrated Auth : True
MPDB ERROR - EXTENDED INFORMATION
MPDB Method : ExecuteSP()
MPDB Method HRESULT : 0x80040E14
Error Description : Syntax error or access violation
OLEDB IID : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
ProgID : Microsoft OLE DB Provider for SQL Server
MPDB ERROR - INFORMATION FROM DRIVER
null MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
=======================================
MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14 MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
Failed to execute MatchDrivers task, hr=0x80040e14 MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
Response message sent to the client MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
Failed to execute task, hr=0x80040e14 MP_DriverManager 7/25/2012 9:48:01 AM 3740 (0x0E9C)
Any pointer where to look to troubleshoot this issue more?
Hi All Did you guyz find a resolution for this ? I am having same error while Installing Power edge R620
Below shows SMSTS.log
Failed to process driver catalog response. Code 0x80004005
OSDDriverClient 10/11/2012 12:31:21 PM
1084 (0x043C)
pDriverCatalog->match( deviceList, m_fpCallbackProc, m_pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,854)
OSDDriverClient 10/11/2012 12:31:21 PM
1084 (0x043C)
pDriverInstaller->AutoInstallDrivers( pDriverCatalog, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,286)
OSDDriverClient 10/11/2012 12:31:21 PM
1084 (0x043C)
Failed to auto provision driver. Code 0x80004005
OSDDriverClient 10/11/2012 12:31:21 PM
1084 (0x043C)
ProcessAutoProvision( pDriverInstaller, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,415)
OSDDriverClient 10/11/2012 12:31:21 PM
1084 (0x043C)
Failed to auto provision drivers. Code 0x80004005
OSDDriverClient 10/11/2012 12:31:21 PM
1084 (0x043C)
Below is the MP Driver log
CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14
MP_DriverManager 10/11/2012 11:12:59 AM
11228 (0x2BDC)
======================================= MP_DriverManager
10/11/2012 11:12:59 AM 11228 (0x2BDC)
MPDB ERROR - CONNECTION PARAMETERS
SQL Server Name : sqlserver
SQL Database Name : SMS
Integrated Auth : True
MPDB ERROR - EXTENDED INFORMATION
MPDB Method : ExecuteSP()
MPDB Method HRESULT : 0x80040E14
Error Description : Syntax error or access violation
OLEDB IID : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
ProgID : Microsoft OLE DB Provider for SQL Server
MPDB ERROR - INFORMATION FROM DRIVER
null MP_DriverManager
10/11/2012 11:12:59 AM 11228 (0x2BDC)
=======================================
MP_DriverManager
10/11/2012 11:12:59 AM 11228 (0x2BDC)
Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14
MP_DriverManager 10/11/2012 11:12:59 AM
11228 (0x2BDC)
Failed to execute MatchDrivers task, hr=0x80040e14
MP_DriverManager 10/11/2012 11:12:59 AM
11228 (0x2BDC)
Anyone found a resolution for this ?Storage drivver is H710 mini and because of this error,storage driver is not getting installed, and hence OS installation is failing
Similar Messages
-
SCCM 2012 SP1 - OSD Task Sequence - Auto Apply Drivers
I have a basic task sequence created, capture User State, reboot into Windows PE, Apply Operating system, apply Windows Settings, Auto Apply Drivers, Setup Windows and Configuration, Install Applications, Restore User state
The problem I'm having is auto Apply the drivers. My test system is a Dell Opitiplex 3010, with a realtek PCI GBE Family Controller being the only driver added to the driver database.
During the task sequence, I see it down loading the driver, then proceed though the whole sequence. The system restarts and brings up the login. Here is the problem, the network drivers don't install, so the system is still in a workgroup, with no user state
restore.
I repeat the task, this time during the Setup Windows and Configuration, I press F8, and copy the _SMSTaskSequence folder to C:\temp.
Once the task in complete, I see the network drivers saved in _SMSTaskSequence\Drivers & \contentCache. I able to install the network drivers from this location.
What am I missing, why are the network drivers not being setup correctly in Windows 7?
From the \logs\SMST.LOG, I can see the driver being installed correctly, but one the sequence is complete the driver has not been installed.
From the SMSTS.LOG:
Installing driver "Realtek PCI GBE Family Controller" OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Copying "C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5" to "C:\_SMSTaskSequence\drivers\1". OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Successfully installed driver "Realtek PCI GBE Family Controller". OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Entering ReleaseSource() for C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5 OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
reference count 1 for the source C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5 before releasing OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Released the resolved source C:\_SMSTaskSequence\ContentCache\BA4B1243-742B-4BFA-8245-89E7B33DE1C5 OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Microsoft ACPI-Compliant System'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Microsoft Basic Render Driver'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel(R) 6 Series/C200 Series Chipset Family USB Enhanced Host Controller - 1C26'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel(R) 82802 Firmware Hub Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic volume'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'ACPI Fixed Feature Button'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'HID-compliant mouse'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Motherboard resources'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'CD-ROM Drive'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'USB Root Hub'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'System timer'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic USB Hub'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'USB Input Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'ACPI Power Button'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'High Definition Audio Controller'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Motherboard resources'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Microsoft System Management BIOS Driver'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Intel Processor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'PCI Simple Communications Controller'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'HID Keyboard Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic volume'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'Generic Monitor'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Failed to find a suitable device driver for device 'USB Input Device'. OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Exiting with return code 0x00000000 OSDDriverClient 3/21/2014 5:52:37 PM 900 (0x0384)
Process completed with exit code 0 TSManager 3/21/2014 5:52:37 PM 1300 (0x0514)
!--------------------------------------------------------------------------------------------! TSManager 3/21/2014 5:52:37 PM 1300 (0x0514)
Successfully completed the action (Auto Apply Drivers) with the exit win32 code 0 TSManager 3/21/2014 5:52:37 PM 1300 (0x0514)Yes, I open a dos box during the Windows Setup, xcopy SMSTaskSequence to C:\temp
Then once Windows install is completed, I login to the local Admin account(only thing available), device manager and install the network driver from C:\temp\SMSTaskSequence\drivers\1
From Earlier in Setupact.log:
PnPIBS: C:\_SMSTaskSequence\drivers is listed as a driver path in unattend.xml ...
2014-03-25 12:27:22, Info PnPIBS: Found the file rt64win7.inf
2014-03-25 12:27:22, Info PnPIBS: Added driver C:\_SMSTaskSequence\drivers\1\rt64win7.inf to the list of drivers. -
Hi
i have MDT based Ts in configuration manager to build and capture image. I have started building drivers packages in Configuration manager. I am using VM as reference machine to build and capture image. Sine there is 'Auto Apply drivers' step in Build and
capture it looks like failing the VM. Can i disable this step in TS sequence when i am using it on Virtual machine? Has anyone experienced the same issue? any pointers pls. thanks.
Regards,Hi,
Yes you should disable the "Auto Apply Drivers" step when building a reference image usign a build and capture TS: If you use Hypoer-V no drivers are needed nd shoiuld not be isntalled.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
Problems with applying drivers
Hi.
I've had a struggling with applying drivers for a new machine model we started to use in our company.
I've made a step in our task sequence to apply drivers, if the wmi query returns version "ThinkCentre E73".
When i try to run the wmi code on the computer after installtions, it says "ThinkCentre E73"
So cant really see the reasons why its not installing the drivers.
Here is what the smstslog says about the step: *
Parsing step node: Lenovo ThinkCentre E73 TSManager
23-10-2014 11:12:30 1148 (0x047C)
Description: Lenovo ThinkCentre E73 TSManager
23-10-2014 11:12:30 1148 (0x047C)
ContinueOnError: TSManager
23-10-2014 11:12:30 1148 (0x047C)
SuccessCodeList: 0 TSManager
23-10-2014 11:12:30 1148 (0x047C)
A condition is associated with the step found
TSManager 23-10-2014 11:12:30
1148 (0x047C)
Found and operator. TSManager
23-10-2014 11:12:30 1148 (0x047C)
There are 1 operands TSManager
23-10-2014 11:12:30 1148 (0x047C)
**Processing expression node TSManager
23-10-2014 11:12:30 1148 (0x047C)
Found SMS_TaskSequence_WMIConditionExpression expression.
TSManager 23-10-2014 11:12:30
1148 (0x047C)
**In ProcessBuiltInCondition node: expression
TSManager 23-10-2014 11:12:30
1148 (0x047C)
There are 2 operands in the built in action
TSManager 23-10-2014 11:12:30
1148 (0x047C)
Operand Namespace=root\cimv2 TSManager
23-10-2014 11:12:30 1148 (0x047C)
Operand Query=SELECT * FROM Win32_ComputerSystemProduct WHERE Version = "ThinkCentre E73"
TSManager 23-10-2014 11:12:30
1148 (0x047C)
Successfully added 3 condition parameters TSManager
23-10-2014 11:12:30 1148 (0x047C)
Disable: TSManager
23-10-2014 11:12:30 1148 (0x047C)
Run in attribute: WinPE TSManager
23-10-2014 11:12:30 1148 (0x047C)
Timeout: TSManager
23-10-2014 11:12:30 1148 (0x047C)
DefaultVarlist found TSManager
23-10-2014 11:12:30 1148 (0x047C)
Variable name: OSDAllowUnsignedDriver TSManager
23-10-2014 11:12:30 1148 (0x047C)
Action command line: osddriverclient.exe /install:PS100033 /unsigned:%OSDAllowUnsignedDriver%
TSManager 23-10-2014 11:12:30
1148 (0x047C)
Adding instruction at 90 TSManager
23-10-2014 11:12:30 1148 (0x047C)
Processed all elements TSManager
23-10-2014 11:12:30 1148 (0x047C)
Adding end group instruction at 91 TSManager
23-10-2014 11:12:30 1148 (0x047C)
The next instruction after group will be at 92
TSManager 23-10-2014 11:12:30
1148 (0x047C)
Processing group TSManager
23-10-2014 11:12:30 1148 (0x047C)
Any ideas left?
It's not bringing an error or anything, and my best guess would be that it doesnt respond to the version number.
How can i troubleshoot ths further on?
Thanks in advanceJust try to add an additional LAN driver otherwise, which is signed by default. Within SCCM unsigned drivers are ignored by default. Did you download specific drivers or using Lenovo Update Retriever?
More about driver management on Dell, HP and Lenovo systems:
http://henkhoogendoorn.blogspot.nl/2013/12/download-driver-packages-for-dell-hp.html
And this one will do also: How to import Lenovo drivers in ConfigMgr easily:
http://henkhoogendoorn.blogspot.nl/2014/02/good-news-when-you-are-using-mdt-andor.html?spref=tw
In the past I used 4 numbers/figures as WMI query.
My blogs: Henk's blog | Follow Me on:
Twitter | View My Profile on:
LinkedIn -
Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)
Hi there
Patch Tuesday yesterday (10th June2014). As always we deploy new patches first to a test collection where Windows 7 updates automatically apply.
Upon trying to rebuild any of the machines in this test collection, we were presented with the following error message:
Failed to run task sequence. Error occurred while starting the task sequence (0x8007000E)
After searching about this, I found this page from Niall Brady, which explained the problem:
http://www.niallbrady.com/2013/05/17/after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log/
So I removed some of the machines from the test Windows update collection, and as per the advice in the above link, the error was gone and those machines could be built successfully.
So the problem is there were too many many policies downloaded (apps, packages and most of all updates) for the task sequence ram to store, hence the error.
Now...
...I have a question.
The next logical step to my mind is to patch our OS image with all missing patches, so these do not have to be downloaded at build time. Niall mentions this as one of the resolutions to this issue.
However there seems to be some confusion over whether this would actually make a difference.
I read through this link:
http://social.technet.microsoft.com/Forums/en-US/7e597b44-2586-4063-b6d0-cec48a7c11c7/sccm-2012-task-sequence-failure-0x8007000e?forum=configmanagerosd
There's seems to be no consensus on this.
Is SCCM 2012 clever enough to - when the task sequence is first started - to download ONLY the updates (policies) it detects as NOT present in the OS image...
or
Will it simply try to download policies for ALL items deployed to it, whether the updates are present in the OS image or not?
I will be disappointed if SCCM 2012 SP1 CU2 isn't clever enough to only download policies at build time for the apps, packages and updates it detects as needed.
I'd be grateful for some clarity on this.
Regards,
John, Glasgow.Hi Jason
Thank you for replying, I appreciate it.
1) We currently have 15 or 16 software update groups for Office updates, dating back a month or two. The latest software update group contains all the patches in the previous software update groups plus the patches released on 10th June. Do you recommend
deleting all but the latest software update group?
2) I'm almost reluctant to ask this, but based on what you have advised, is it the case that when the task sequence executes, it will download policies for each update in each software update group regardless of whether it has already downloaded a policy
for an update in a previous software update group? So in effect it's downloading policies (for updates) it has already downloaded?
3) I'm not clear on why there would be no policy for an image; in Niall Brady's informative page on the 8007000E error, he writes the following:
"The reason it has run of space could be due to four possibilites: too many applications, too many Windows updates, too many Task Sequence steps, too many referenced packages'.
Can you shed some light on why there isn't a policy for an image?
Thanks again for replying,
John. -
OSD - Failed to run Task Sequence. An error occurred while starting the task sequence (0x8007000E).
Failed to run Task Sequence.
An error occurred while starting the task sequence (0x8007000E)."
While OSD, picks up task sequence but fails in resolving task sequence dependencies. SMSPXE identifies device is not in database (unknown).
SMSTS.log shows
ThreadToResolveAndExecuteTaskSequence failed. Code(0x8007000E)" in SMSTS.LOG, have seen other articles suggesting failure due to lack of storage (RAM) but this task sequence has worked in past.
By the way, if I create a stand alone media, we are able to image the workstation. What has changed in the task sequence such that the workstation is unable to download policies due to lack of storage (RAM) on workstation. Workstation has 2 GB of RAM.I have found a work around for the issue, even though the computer is unknown, there were software updates targeted to the ALL SYSTEMS collection which applies to All Unknown Computers and therefore to x64 Unknown Computer and x86 Unknown Computer.
We had a SCEP ADR applying definition updates to All Systems, we applied the ADR to a different collection, removed all the SCEP updates to All Systems and successfully re-imaged the workstation. Following article was of great help in identifying the problem
after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log
Thanks Gerry for your assistance. -
Occasional Task Sequence fail (1 out of 5) with Error 615 Your Password is too short
We have a task sequence that fails to install software and updates with an error liek this: Operation System Error 615: The password you provided was too short for the computers password policy. Please provide a longer password.
With all software installations I always tick the continue on failure. Consequently in a task sequence you see the entire list of installation requirements fail with this error. This includes Applications, Packages and Software Updates. Without any amendment,
the next time it is run, it runs successfully. Add to this the issue that the task sequence no longer displays the progress bar after rebooting into windows (x64) and it all points to the OSD process being a bit flaky.
By the way, we are installing Win7 x64 (No x86 anymore) over PXE.
So any pointers with this would be very gratefully received.
Anthony Sheehy - MCP, MCITPHere is the status message sent to Configuration Manager:
The task sequence execution engine failed executing the action (Freefall Sensor) in the group (Install) with the error code 2278559764
Action output: 7"'
Verified policy is compiled in 'root\ccm\policy\machine' namespace
content location count = 1
Invoking Execution Manager to install software
FALSE, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,251)
0, HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\installsoftware.cpp,764)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\WGS00137
reference count 1 for the source C:\_SMSTaskSequence\Packages\WGS00137 before releasing
Delete source directory C:\_SMSTaskSequence\Packages\WGS00137
Released the resolved source C:\_SMSTaskSequence\Packages\WGS00137
pInstall->Install(sPackageID, sProgramName), HRESULT=87d01014 (e:\nts_sccm_release\sms\client\osdeployment\installsoftware\main.cpp,361)
Failed to invoke Execution Manager to Install Software for PackageID='WGS00137' ProgramID='Silent Installation' AdvertID='WES20013' hr=0x87d01014
InstallSoftware failed, hr=0x87d01014
Install Software failed, hr=0x87d01014. The operating system reported error 615: The password provided is too short to meet the policy of your user account. Please choose a longer password.
And here's the group policy that is applied to that OU:
Enforce password history
0 passwords remembered
Maximum password age
0 days
Minimum password age
0 days
Minimum password length
0 characters
Password must meet complexity requirements
Disabled
Of course, the password complexity issue is a non-starter: How come SCCM 2007 task sequences did not have the same problem? Why does the Task Sequence work
sometimes and not others. All passwords I provide to Configuration Manager all conform to complexity rules anyway.
The relevant SMSTS.log portion is below:
<![LOG[Variable name: _SMSSWDProgramName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsswd.exe /pkg:WGS00137 /install /basevar: /continueOnError:]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 90]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Applications]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_28f01c04-7229-4152-85e2-f2f43daf92b2,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_382fdd99-2228-452d-a6f0-63e543ce628d /basevar: /continueOnError:True]LOG]!><time="18:06:06.660-60"
date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 91]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[
Parsing step node: Language Packs]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
<![LOG[Description: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:462">
<![LOG[ContinueOnError: true]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:466">
<![LOG[SuccessCodeList: 0]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:474">
<![LOG[(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="0" thread="1804" file="ccmxml.h:582">
<![LOG[No condition is associated with the step.]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:670">
<![LOG[Disable: ]LOG]!><time="18:06:06.660-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:483">
<![LOG[Run in attribute: FullOS]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:491">
<![LOG[Timeout: ]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:495">
<![LOG[DefaultVarlist found]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:579">
<![LOG[Variable name: OSDApp0Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp0Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp1Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp2Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp3Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp4Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp5Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp6Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Description]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7DisplayName]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDApp7Name]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Variable name: OSDAppCount]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:620">
<![LOG[Action command line: smsappinstall.exe /app:ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_9df3ec9a-e691-4106-b274-46c4c6c319b9,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_42e28566-b339-4773-92cf-05b8e748d996,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_305b4a34-0b5a-46fe-82dd-c57a5897e063,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_379afca3-f48e-486b-8848-296223481edd,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_502bf2db-e1c8-42ac-a499-61320d661cc3,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_455a6de9-fe98-47ed-8dab-e860dd4681ed,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_1707c97e-b4bb-4827-9117-02e79435213e,ScopeId_69AC7FA1-9E68-49C4-8D43-9BA17630A64D/Application_a17f2337-ad2e-42cb-9813-c9e167a85050
/basevar: /continueOnError:True]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:522">
<![LOG[Adding instruction at 92]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:524">
<![LOG[Processed all elements]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:333">
<![LOG[Adding end group instruction at 93]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:402">
<![LOG[The next instruction after group will be at 94]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:408">
<![LOG[
Parsing step node: Opt In to CEIP and WER]LOG]!><time="18:06:06.676-60" date="05-28-2012" component="TSManager" context="" type="1" thread="1804" file="tsxml.cpp:458">
Anthony Sheehy - MCP, MCITP -
Hi,
Environment ConfigMgr 2012 R2
Replace Scenario: Capture data to a USB external drive and Restore it from USB external drive.
Steps taken:
1) Created Computer Association with New computer and Source computer
2) Deployed UDI replace Task Sequence to Source computer and captured data to a USB external drive
3) Run UDI Task Sequence from Boot Media to Restore data from USB External drive which had the captured data.
Issue:
My task sequence failed to restore data from USB external drive.
Is there a fix
Any help is greatly appreciated it.I created a query to see the deployment logs in real time. I see the TS fails when running "Request State Store" task. Here are the logs.
Severity Type Site code Date / Time System Component Message ID Description
Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11141 The task sequence execution engine failed execution of a task sequence. The operating system reported error 1: Incorrect function.
Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Error in the task sequence) in the group (Gather Logs and StateStore on Failure)
with the error code 1 Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' SwdAction = '0001' Set command line: Run command line Working dir 'not
set' Executing command line: Run command line Process completed with exit code 1 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft Deployment Toolkit version: 6.2.5019.0 The task sequencer
log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ZTI deployment failed, Return Code = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
Information Milestone POK 7/22/2014 4:13:14 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Copy Logs) in the group (Gather Logs and StateStore on Failure)
with exit code 0 Action output: ... 扴捡杫潲湵潬潴尠停䭏偃䍓䵃卐䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就瑺獩瑥慢正牧畯摮氮杯潃祰湩㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯穜楴慴潴潬潴尠停䭏偃䍓䵃卐䍜彍潓牵散�潌獧䍜剏ⵐ䠳䑗塐就潃祰湩㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯作䑓敓畴坰穩牡潬潴尠停䭏偃䍓䵃卐䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就协卄瑥灵楗慺摲氮杯潃祰湩㩃坜义佄南停湡桴�潬潴尠停䭏偃䍓䵃卐䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就慐瑮敨屲湕瑡整摮䍇潃祰湩潬㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯䉜䑄氮杯挠湯整瑮潴尠停䭏偃䍓䵃卐䍜彍潓牵散尤协屄潌�Console
> Successfully resized the shadow copy storage association Return code from command = 0 Cleaning up default wallpaper registry keys Process completed with exit code 0 zticopylogs processing completed successfully. Command line returned 0.
Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Move State Store) in the group (Gather Logs and StateStore on Failure)
with exit code 0 Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript.exe "C:\_SMSTaskSequence\WDPackage\scripts\ztimovestatestore.wsf"' SwdAction = '0001' Command line for extension .exe is "%1" %* Set
command line: Run command lineWorking dir 'not set' Executing command line: Run command line Process completed with exit code 0 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft Deployment
Toolkit version: 6.2.5019.0 The task sequencer log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. ztimovestatestore processing completed successfully. Command line returned 0.
Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Gather) in the group (Gather Logs and StateStore on Failure) with
exit code 0 Action output: ... (BIOS is 'DELL - 1072009'). Property IsVM is now = False Finished getting virtualization info Connection succeeded to MicrosoftVolumeEncryption There are no encrypted drives Property IsBDE is now = False Processing
the phase. Determining theINI file to use. Using COMMAND LINE ARG: Ini file = CustomSettings.ini Finished determining the INI file to use. Added new custom property MYCUSTOMPROPERTY Using from [Settings]: Rule Priority = DEFAULT ------ Processing the
[DEFAULT] section ------Process completed with exit code 0 ------ Done processing CustomSettings.ini ------ Remapping variables. Property TaskSequenceID is now = Property DeploymentType is now = NEWCOMPUTER Finished remapping variables. ZTIGather processing
completed successfully. Command line returned 0 ReleaseSource() for C:\_SMSTaskSequence\Packages\POK0000F. reference count 1 for the source C:\_SMSTaskSequence\Packages\POK0000F before releasing Released the resolved source C:\_SMSTaskSequence\Packages\POK0000F.
Information Milestone POK 7/22/2014 4:13:03 PM MININT-P6E4T6G Task Sequence Engine 11130 The task sequence execution engine skipped the action (Use Toolkit Package) in the group (Gather Logs and StateStore on Failure) because
the condition was evaluated to be false.
Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Set Error Code) in the group (Gather Logs and StateStore on Failure)
with exit code 0 Action output: Finished with error code 0.
Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11124 The task sequence execution engine started the group (Gather Logs and StateStore on Failure).
Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11122 The task sequence execution engine skipped the group (Cancelled Wizard Group) because the condition was evaluated to be false.
Error Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Connect to State Store) in the group (State Restore) with the error code 1
Action output: ... ( 0x80070035 ) , trying to connect without username. The network path was not found. Unable to connect to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Sleeping for 15 seconds. Unable to connect to share: The network path was notfound. ( 0x80070035 ) , trying to
connect without username. The network path was not found. Unable to connect to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Sleeping for 20 seconds. Unable to connect to share: The network path wasnot found. ( 0x80070035 ) , trying to
connect without username. The network path was not found. Unable to connect to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Sleeping for 25 seconds. Process completed with exit code 1 ERROR - Unable to map a network drive to
\\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Unable to connect to 563807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f ZTI ERROR - Non-zero return code by ZTIConnect,
rc = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
Warning Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11138 The task sequence execution engine ignored execution failure of the action (Request State Store) in the group (State Restore).
Error Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Request State Store) in the group (State Restore) with the error code 16389
Action output: ... etting Media Certificate. Sending request to MP
http://abcdefg.xyx.xyz.local. Setting message signatures. Setting the authenticator. CLibSMSMessageWinHttpTransport::Send: URL: abcdefg.xyx.xyz.local:80 CCM_POST /ccm_system/requestRequest was successful. migInfoRequestMessage.DoRequest (m_sResponse,true),
HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1098) pClientRequestToMP->DoRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2778) ExecuteRestoreRequestToMP(migInfoFromMP),
HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2903) ExecuteRestoreRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\main.cpp,84) OSDSMPClient finished: 0x00004005 reply from server
is 'NoReply' ClientRequestToMP::DoRequest failed (0x80004005). ExecuteRestoreRequestToMP failed (0x80004005). ExecuteRestoreRequest failed (0x80004005).. The operating system reported error 1: Incorrect function. -
Install Applications in task sequence - fails if there is no source
I found an odd issue in SCCM 2012 SP1. I have many applications that install perfectly when deployed. There is no source for the application because it is a network based install, and needs to be. If I try to add the application to the
"Install Application" method in a task sequence, it looks successful. But then re-edit the task sequence and it will tell you there is an issue with the "Install Application" method. The app will not install when you run the
task sequence either. If you then add a content folder to the application, it works like a charm.
In the meantime, I am providing a dummy content location for these apps so I can get things running. But has anyone run into this? Seems so odd that task sequences don't like apps without content.These are Autodesk application installs. When the deployments are built, they are built to a network location and INI files are generated with paths in them. In the past, I manually edited these files to use local relative pathing, so they
could be used as content, downloaded to the system, and executed locally by SMS. I found issues with install Source locations though (yes, even with using SCCM's built in source control), that made me really want to change the INI's back to network locations,
so now there is no more need for content.
I will have to look into the DCR. -
ConfigMgr client no longer installing during task sequence SCCM 2007
I've been trying to create an image and deploy an image of Dell Latitude E6430 laptops that while the deployment of the image works it does not install the SCCM client (configmgr client). This used to work in my environment but no longer does.
I can deploy the client manually either through the SCCM console or from the client itself. But during the task sequence deploying a captured image it does not install and thus and software I need installed as part of the TS does not get installed.
But the rest of the image works fine including driver deployment, sysprep, domain join, etc. If I watch the job run I do see it start downloading the SCCM client during the TS job but then reboots and that's it. Not sure where to look to see what
could be going on. I read somewhere about a possible driver issue but if the rest of the TS works and all drivers install then how could it be that? If anyone has any suggestions I would greatly appreciate it! Oh by the way I'm still using
SCCM 2007, haven't upgraded yet. Thanks!
Brian SteinWhat's interesting is in the smsts.log file it shows that part of the TS completed successfully. So I'm going to try importing the cab files just to make sure I'm all set with that and I will change my TS to NOT auto apply drivers but rather I'll point
directly to the new driver package I created from the extracted cab and will follow up then. If interested a copy of the smsts.log file found inside the _SMSTaskSequence folder on the client machine (2/3 of the way down I 'bolded' the line where it seems
to say the configmgr client step succeeded:
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ara.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ara.exe ]LOG]!><time="13:49:12.259+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-chs.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-chs.exe ]LOG]!><time="13:49:12.305+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-cht.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-cht.exe ]LOG]!><time="13:49:12.337+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-csy.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-csy.exe ]LOG]!><time="13:49:12.352+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-dan.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-dan.exe ]LOG]!><time="13:49:12.368+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-deu.exe ]LOG]!><time="13:49:12.399+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ell.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ell.exe ]LOG]!><time="13:49:12.415+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-enu.exe ]LOG]!><time="13:49:12.446+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-esn.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-esn.exe ]LOG]!><time="13:49:12.508+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-fin.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-fin.exe ]LOG]!><time="13:49:12.539+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-fra.exe ]LOG]!><time="13:49:12.555+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-heb.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-heb.exe ]LOG]!><time="13:49:12.586+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-hun.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-hun.exe ]LOG]!><time="13:49:12.602+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ita.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ita.exe ]LOG]!><time="13:49:12.633+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-jpn.exe ]LOG]!><time="13:49:12.649+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-kor.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-kor.exe ]LOG]!><time="13:49:12.680+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-nld.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-nld.exe ]LOG]!><time="13:49:12.695+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-nor.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-nor.exe ]LOG]!><time="13:49:12.727+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-plk.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-plk.exe ]LOG]!><time="13:49:12.758+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ptb.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ptb.exe ]LOG]!><time="13:49:12.773+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-ptg.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-ptg.exe ]LOG]!><time="13:49:12.805+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-rus.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-rus.exe ]LOG]!><time="13:49:12.820+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-sve.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-sve.exe ]LOG]!><time="13:49:12.851+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/BITS25/windowsxp-kb923845-x86-trk.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/BITS25/windowsxp-kb923845-x86-trk.exe ]LOG]!><time="13:49:12.867+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/client.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/client.msi ]LOG]!><time="13:49:13.756+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/hotfix/KB977384/sccm2007ac-sp2-kb977384-x86-enu.msp to C:\_SMSTaskSequence\Packages\RPS00005\i386/hotfix/KB977384/sccm2007ac-sp2-kb977384-x86-enu.msp ]LOG]!><time="13:49:13.787+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/msrdcoob_x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/msrdcoob_x86.exe ]LOG]!><time="13:49:13.819+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/msxml6.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/msxml6.msi ]LOG]!><time="13:49:13.881+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/wimgapi.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/wimgapi.msi ]LOG]!><time="13:49:13.897+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/windowsinstaller-kb893803-v2-x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/windowsinstaller-kb893803-v2-x86.exe ]LOG]!><time="13:49:14.084+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/windowsupdateagent30-x86.exe to C:\_SMSTaskSequence\Packages\RPS00005\i386/windowsupdateagent30-x86.exe ]LOG]!><time="13:49:14.302+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/i386/wmirdist.msi to C:\_SMSTaskSequence\Packages\RPS00005\i386/wmirdist.msi ]LOG]!><time="13:49:14.318+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-deu.exe ]LOG]!><time="13:49:14.427+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-enu.exe ]LOG]!><time="13:49:14.505+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-fra.exe ]LOG]!><time="13:49:14.583+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/BITS25/windowsserver2003-kb923845-ia64-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/BITS25/windowsserver2003-kb923845-ia64-jpn.exe ]LOG]!><time="13:49:14.661+300" date="02-26-2014"
component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/msrdcoob_ia64.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/msrdcoob_ia64.exe ]LOG]!><time="13:49:14.692+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/msxml6_ia64.msi to C:\_SMSTaskSequence\Packages\RPS00005\ia64/msxml6_ia64.msi ]LOG]!><time="13:49:14.911+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/ia64/windowsupdateagent30-ia64.exe to C:\_SMSTaskSequence\Packages\RPS00005\ia64/windowsupdateagent30-ia64.exe ]LOG]!><time="13:49:15.316+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/sccm_client.bat to C:\_SMSTaskSequence\Packages\RPS00005\sccm_client.bat ]LOG]!><time="13:49:15.332+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-chs.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-chs.exe ]LOG]!><time="13:49:15.363+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-cht.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-cht.exe ]LOG]!><time="13:49:15.394+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-deu.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-deu.exe ]LOG]!><time="13:49:15.410+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-enu.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-enu.exe ]LOG]!><time="13:49:15.535+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-esn.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-esn.exe ]LOG]!><time="13:49:15.566+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-fra.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-fra.exe ]LOG]!><time="13:49:15.597+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ita.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ita.exe ]LOG]!><time="13:49:15.613+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-jpn.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-jpn.exe ]LOG]!><time="13:49:15.675+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-kor.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-kor.exe ]LOG]!><time="13:49:15.706+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ptb.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-ptb.exe ]LOG]!><time="13:49:15.737+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-rus.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/BITS25/windowsserver2003.windowsxp-kb923845-x64-rus.exe ]LOG]!><time="13:49:15.769+300"
date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/msrdcoob_amd64.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/msrdcoob_amd64.exe ]LOG]!><time="13:49:15.784+300" date="02-26-2014" component="OSDSetupHook" context="" type="1"
thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/msxml6_x64.msi to C:\_SMSTaskSequence\Packages\RPS00005\x64/msxml6_x64.msi ]LOG]!><time="13:49:16.112+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380"
file="downloadcontent.cpp:1177">
<![LOG[Downloaded file from
http://SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80/SMS_DP_SMSPKGD%24/RPS00005/x64/windowsupdateagent30-x64.exe to C:\_SMSTaskSequence\Packages\RPS00005\x64/windowsupdateagent30-x64.exe ]LOG]!><time="13:49:16.377+300" date="02-26-2014" component="OSDSetupHook"
context="" type="1" thread="1380" file="downloadcontent.cpp:1177">
<![LOG[Download done setting progress bar to 100]LOG]!><time="13:49:16.377+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="downloadcontent.cpp:1182">
<![LOG[c:\_smstasksequence\packages\rps00005\i386 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\ia64 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\x64 is a directory. Setting directory security]LOG]!><time="13:49:16.408+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\bits20 is a directory. Setting directory security]LOG]!><time="13:49:16.814+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\bits25 is a directory. Setting directory security]LOG]!><time="13:49:16.814+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\hotfix is a directory. Setting directory security]LOG]!><time="13:49:16.829+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\i386\hotfix\kb977384 is a directory. Setting directory security]LOG]!><time="13:49:17.297+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\ia64\bits25 is a directory. Setting directory security]LOG]!><time="13:49:17.407+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[c:\_smstasksequence\packages\rps00005\x64\bits25 is a directory. Setting directory security]LOG]!><time="13:49:17.516+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="hashdir.cpp:653">
<![LOG[Content successfully downloaded at C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.578+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3131">
<![LOG[Copying SMS client package source from "C:\_SMSTaskSequence\Packages\RPS00005" to "C:\_SMSTaskSequence\OSD\RPS00005".]LOG]!><time="13:49:17.578+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:1504">
<![LOG[Locating architecture-specific OSDGina.dll]LOG]!><time="13:49:17.687+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:428">
<![LOG[Successfully copied file OSDSETUPHOOK.EXE to C:\WINDOWS\SYSTEM32]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
<![LOG[Successfully copied file TSProgressUI.exe to C:\WINDOWS\SYSTEM32\_SMSOSDSetup]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
<![LOG[Successfully copied file tsres.dll to C:\WINDOWS\SYSTEM32\_SMSOSDSetup\1033]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="basesetuphook.cpp:364">
<![LOG[Saving desktop wallpaper information.]LOG]!><time="13:49:17.703+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:1553">
<![LOG[Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3431">
<![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\RPS00005 before releasing]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3438">
<![LOG[Delete source directory C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.719+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3461">
<![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\RPS00005]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1380" file="resolvesource.cpp:3471">
<![LOG[Exiting ConfigureEx: 0x00000000]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="0" thread="1380" file="basesetuphook.cpp:1592">
<![LOG[Process completed with exit code 0]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:1102">
<![LOG[Installing hook to 'C:\WINDOWS']LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="setupwindows.cpp:785">
<![LOG[Command line for extension .EXE is "%1" %*]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/install:C:\WINDOWS" /version:6.1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/install:C:\WINDOWS" /version:6.1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:805">
<![LOG[Installing OSD setup hook]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1392" file="osdsetuphook.cpp:276">
<![LOG[Setup hook install completed successfully]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupHook" context="" type="1" thread="1392" file="vistasetuphook.cpp:111">
<![LOG[Process completed with exit code 0]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="commandline.cpp:1102">
<![LOG[OfflineRegistry::Init("C:\WINDOWS")]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:168">
<![LOG[Loading offline registry hive "C:\WINDOWS\system32\config\software" into HKLM\OfflineRegistry1]LOG]!><time="13:49:17.750+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:60">
<![LOG[Loading offline registry hive "C:\WINDOWS\system32\config\system" into HKLM\OfflineRegistry2]LOG]!><time="13:49:18.545+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:60">
<![LOG[CurrentControlSet is mapped to ControlSet001]LOG]!><time="13:49:19.169+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:215">
<![LOG[SMS Client is not installed]LOG]!><time="13:49:19.185+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="setupwindows.cpp:1633">
<![LOG[Unloading offline SOFTWARE registry hive]LOG]!><time="13:49:19.185+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:270">
<![LOG[Unloading offline SYSTEM registry hive]LOG]!><time="13:49:19.263+300" date="02-26-2014" component="OSDSetupWindows" context="" type="0" thread="2032" file="offlineregistry.cpp:284">
<![LOG[Exiting with code 0x00000000]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="OSDSetupWindows" context="" type="1" thread="2032" file="setupwindows.cpp:1751">
<![LOG[Process completed with exit code 0]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="commandline.cpp:1102">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="instruction.cxx:3010">
<![LOG[Successfully complete the action (Setup windows and ConfigMgr) with the exit win32 code 0]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="instruction.cxx:3036">
<![LOG[Sending status message . . .]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:292">
<![LOG[Send a task execution status message SMS_TSExecution_ActionCompleteInfo]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:314">
<![LOG[MP server SCCM1.ROSNET.ROSLYNSCHOOLS.ORG and port 80. SSL=false. CRL=false.]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:458">
<![LOG[Site code: RPS]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:489">
<![LOG[Client machine name: new6430]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:494">
<![LOG[Client Identity: GUID:EBA20587-9DCD-4F19-B999-F6FA0E56D6CD]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:496">
<![LOG[Advertisement ID: RPS20136]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:505">
<![LOG[Package ID: RPS000E1]LOG]!><time="13:49:19.294+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utility.cxx:507">
<![LOG[Sending StatusMessage]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:3806">
<![LOG[Formatted header:]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:1500">
<![LOG[<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>727ba42b-9664-4eea-8690-e285a795b870</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2014-02-26T18:49:19Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="4220"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:1501">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: SCCM1.ROSNET.ROSLYNSCHOOLS.ORG:80 CCM_POST /ccm_system/request]LOG]!><time="13:49:19.325+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="libsmsmessaging.cpp:7446">
<![LOG[The request has succeeded. 200 OK]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="libsmsmessaging.cpp:7734">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:782">
<![LOG[Clear local default environment]LOG]!><time="13:49:19.341+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:807">
<![LOG[The action (Setup windows and ConfigMgr) requested a retry]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:263">
<![LOG[Reboot to local harddisk]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:458">
<![LOG[_OSDGinaIsConfigured variable set to TRUE]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:537">
<![LOG[_SMSTSServiceStartType variable set to ]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:549">
<![LOG[Calling RebootSystem()]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:567">
<![LOG[OSD type of task sequence. ignore the service window setting]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="engine.cxx:669">
<![LOG[Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.]LOG]!><time="13:49:19.403+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utils.cpp:829">
<![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="13:49:19.419+300" date="02-26-2014" component="TSManager" context="" type="1" thread="1452" file="utils.cpp:829">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=9]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:386">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=8]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:668">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=8]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:414">
<![LOG[Save the current environment block]LOG]!><time="13:49:19.435+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:833">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="13:49:19.450+300" date="02-26-2014" component="TSManager" context="" type="0" thread="1452" file="executionenv.cxx:782">
Brian Stein -
Dell Driver Packages breaks OSD Task Sequences?
I'm completely stumped here... I had an OSD Task Sequence that was working perfectly. Then I imported some Dell Driver Packages with the Dell Client Integration Pack and suddenly, OSD doesn't work anymore.. I made no changes to the Task Sequence itself (steps
are listed below).
The weird thing is, when the OSD is actually running, the progress bar goes through all of the steps and the Monitoring space on the deployment shows each step completing successfully, but every step after "Apply Operating System" doesn't actually
take effect. When rebooted, I find the computer has not joined the domain, has not applied any drivers, has not installed the SCCM client, didn't install any of the applications, and didn't install the updates. It's like the task sequence just
stopped actually writing to the hard drive and just pretended to go through the motions.
Does anyone have any idea what could have happened? This same task sequence used to work just fine. Could just having driver packages available on the DPs break the OSD even though they're not even referenced in the task sequence?
-Install Operating System
-Restart in Windows PE
-Partition Disk 0
-Apply Data image 1
-Apply Operating System
-Apply Windows Settings
-Apply Network Drivers
-Apply Device Drivers
-Setup Operating System
-Setup Windows and Configuration Manager
-Install Java
-Install Adobe Acrobat Reader XI
-... install a few more applications
-Install UpdatesAs Torsten said, yes, you will need to examine the logs. Post the contents of smsts.log here if you don't know what to look for
Here's a reference to help you find the location of the logs:
http://richardbalsley.com/location-of-smsts-log-when-using-configuration-manager-operating-system-deployment
Also:
What OS are you trying to apply?
What version of WinPE are you using?
Are you using Auto Apply Drivers or Apply Driver Package steps to install drivers? If Auto Apply Drivers, do you have them limited by category? -
When is it safe to update a task sequence?
We have a fairly busy environment, with OSD happening all the time. We have been updating our major task sequences off hours, but I wonder if that is even necessary. After testing in QA, is it safe to update the task sequence at any time without bothering
or confusing workstations that are in the middle of an OSD operation?
I think I understand that the task sequence is pulled down to the local hard drive very early in OSD, and it doesn't return to re-read the task sequence after that. Is that correct? If that's true then we don't need to worry about workstations losing their
place in the task sequence if we update it while they are executing the task sequence.
Thank you for any light others can shed on this.
Gary
Gary Knigge, Senior Systems Analyst Division of Technology Services University of Wisconsin-River Falls Wisconsin, USACorrect, the machine downloads the task sequence at the beginning of the process and uses that cached copy throughout, so modifying the task sequence will not affect any deployments already executing.
That said, the biggest risk you face in modifying production task sequences is content. If you add a task referencing content that is not yet fully deployed and available, you will cause any subsequent executions to fail. This is especially true of
adding new Driver Packages as there is a known issue with the content not being recognized as valid until Rev2 (you not only have to distribute it to your DPs but also subsequently update the DPs to rev the content). -
DBReadInteractionSpec Execute Failed Exception.
I am new bie and pleae help me I am getting the below error while trying to testing the webservice from sample application validatecreditcheck
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: DBReadInteractionSpec Execute Failed Exception. Query name: [getCreditValidationSelect], Descriptor name: [getCreditValidation.Creditcardinfo]. Caused by Exception [EclipseLink-6003] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.QueryException Exception Description: The number of arguments provided to the query for execution does not match the number of arguments in the query definition. Query: ReadAllQuery(name="getCreditValidationSelect" referenceClass=Creditcardinfo sql="SELECT CCNUMBER, STATUS FROM CREDITCARDINFO WHERE (CCNUMBER = ?)"). See root exception for the specific exception. This exception is considered not retriable, likely due to a modelling mistake. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:808) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:384) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:187) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:889) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:379) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:194) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Client received SOAP Fault from server : Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: DBReadInteractionSpec Execute Failed Exception. Query name: [getCreditValidationSelect], Descriptor name: [getCreditValidation.Creditcardinfo]. Caused by Exception [EclipseLink-6003] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.QueryException Exception Description: The number of arguments provided to the query for execution does not match the number of arguments in the query definition. Query: ReadAllQuery(name="getCreditValidationSelect" referenceClass=Creditcardinfo sql="SELECT CCNUMBER, STATUS FROM CREDITCARDINFO WHERE (CCNUMBER = ?)"). See root exception for the specific exception. This exception is considered not retriable, likely due to a modelling mistake. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:362) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:1004) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:750) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:802) ... 79 more Caused by: oracle.j2ee.ws.client.jaxws.JRFSOAPFaultException: Client received SOAP Fault from server : Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: DBReadInteractionSpec Execute Failed Exception. Query name: [getCreditValidationSelect], Descriptor name: [getCreditValidation.Creditcardinfo]. Caused by Exception [EclipseLink-6003] (Eclipse Persistence Services - 2.3.1.v20111018-r10243): org.eclipse.persistence.exceptions.QueryException Exception Description: The number of arguments provided to the query for execution does not match the number of arguments in the query definition. Query: ReadAllQuery(name="getCreditValidationSelect" referenceClass=Creditcardinfo sql="SELECT CCNUMBER, STATUS FROM CREDITCARDINFO WHERE (CCNUMBER = ?)"). See root exception for the specific exception. This exception is considered not retriable, likely due to a modelling mistake. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1040) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:826) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:358) ... 82 more
View Log MessagesSaveClose934428 wrote:
The number of arguments provided to the query for execution does not match the number of arguments in the query definition
Your query is expecting an argument that seems you are not passing, check your DB operation.
Cheers,
Vlad -
Hi All,
It has been mentioned to be that it is possible to have both "Apply Driver Package" and "Auto Apply Device Drivers - PNP' " specified in the same task sequence, with some kind of logic specified that if the Apply Driver Package step does
not run due to the hardware wmi query not being valid then the 'Apply Device Drivers -PNP' will run instead. Vice-versa - if the "Apply Driver Package" wmi query is correct and driver package applied then the 'Auto Apply Device Drivers -PNP'
will not run and be skipped.
Is this possible ?
I can't seem to find any documentation or reference indication this can be done. :-(
Many thanks everyone..To add some info here, note that the end result of both tasks is the same. Neither actually *installs* drivers in any way. Both simply copy the drivers to the target system and inject them into the image being deployed where they are then available to Windows
Setup (which runs during the Setup Windows and ConfigMgr task) to install based upon the Windows Setup standard PNP detection.
Thus, using both task types, depending upon what is in the driver packages and what is detected by the OSD PNP detection (which differs slightly from the OS PNP which is far more complex and has been described as a "black art"), potentially injects
more drivers into the image potentially making more drivers available to Windows Setup. This could of course increase your deployment time.
I've thought about this approach before and it is technically valid, but I've never had to resort to it. I've always just made sure that the drivers packages are complete. If you're trying to address the scenario of hardware without a explicit driver package,
I could see it working but I could also see it causing problems because drivers are weird. In general, I would recommend always testing new hardware and anything not accounted for is considered unsupported.
Jason | http://blog.configmgrftw.com | @jasonsandys -
Task Sequence fails on "Apply Driver Package" when PXE-booting but not with bootable media
I have an issue where my Task Sequence fails during 'Apply Driver Package' when PXE-booting but works ok when booting from CD or USB-stick. It fails withe error code 0x80070002 and when pressing F8 and checking the ipconfig there's a 169.254.x.x address.
Somehow it looses it's real ip during the process.
I'm grateful for any advice!Please enable verbose logging for Task sequence, then upload the smsts.log to Skydrive.
0x80070002 error is too generic, which cannot be used to determine the cause.
Juke Chou
TechNet Community Support
Maybe you are looking for
-
Planning to upgrade my CPU. Would like help in proceeding -- OP sys is Win XpPro. 1. Which BIOS should I flash? Understand that 1.9 BIOS has given problems. Have scanned Syar's 7025 listings, but would appreciate help in deciding the one to use. 2
-
Header & Footer in pdf file converted from html
I am using Acrobat Professional on WinXP and Firefox. This is the first time I tried to convert a saved html file to pdf and it works. However the converted file have the html pagename at the header and the filename, location, date created at the foo
-
Conversion string from a system unit to another
Hi all i've a problem i'm talking with an oscilloscope. when i ask it some information like X or Y scale, it answers me a string (like 0.0016 to indicate 1.6m or 0.0000005 to indicate 500n). I'm finding difficulties because the first string to number
-
FI-AA Normal and Special Periods
hi, In Asset Accounting there are normal and special periods for a fiscal year,why do we use the special periods? Vinay
-
Why would my SG200-26P loose its fixed ip?
Hi there. I have 4 of these switches that seem to have lost their ips. They were fixed to 192.168.x.6,7,8,9 via the management inteface. It seems there was a power outage that reset most of the network. It was for less than 1 hr. Once things powered