Jump to content


Sign in to follow this  
murda

PXE-E53: No boot filename received

Recommended Posts

I am getting that messages when I try to capture a SONY VGN BZ11XN.

 

WDS & PXE roles are installed

Also imported boot images X64 & X86

Added OS

Added drives in the bootimages

Made task sequence and I advertised.

 

Anyone know a solution?

Share this post


Link to post
Share on other sites


look at this post for some ideas

 

 

Alright, I am a bit further.

Still trouble shooting now with PXE client rebooting in PXE setup. Maybe because I am running on low disk space :P.

 

Anyway, does pxe say something when a capture has completed??

Share this post


Link to post
Share on other sites

if its rebooting in pxe setup then you need to read the smsts.log file to find out why *normally network drivers"

 

post the log here and i'll look at it

Share this post


Link to post
Share on other sites
if its rebooting in pxe setup then you need to read the smsts.log file to find out why *normally network drivers"

 

post the log here and i'll look at it

 

Yeah, normally it is and I already looked at it and there were no logs written in the smsts.log.

But I think my problem is indeed the network drives (Set 3 different network drives in the bootimage).

 

I've almost no time to setup SCCM and test it, only 8 hours a week.

 

But i'll keep posting my problems and solutions as much as i can (read: time :))

Share this post


Link to post
Share on other sites

This is my smsts log file. As you can see it stopped woking at 9th of march :) Which is offcourse not oké.

 

<![LOG[successfully intialized Logging for TS Manager.]LOG]!><time="17:06:01.491+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="5780" file="tsmanager.cpp:617">

<![LOG[Commandline: "C:\Program Files\SMS_CCM\TSManager.exe" /service]LOG]!><time="17:06:01.506+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="5780" file="tsmanager.cpp:60">

<![LOG[successfully registered Task Sequencing COM Interface.]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="5780" file="environmentlib.cpp:768">

<![LOG[Executing as a service]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="5780" file="tsmanager.cpp:647">

<![LOG[started ServiceMain]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tsmanager.cpp:300">

<![LOG[Failed to restore logs from cache. Execution history may be lost.]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="tsmanager.cpp:390">

<![LOG[Task Sequence Manager executing as service main thread]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tsmanager.cpp:417">

<![LOG[Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="environmentscope.cpp:250">

<![LOG[Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="environmentscope.cpp:250">

<![LOG[Failed to locate the local data path. The files needed to resume the task sequence are missing. This could be because the task sequence finished while in Windows PE. Please check the largest available partition for SMSTSLog\smsts.log file for more information.

The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="17:06:01.663+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="tsmanager.cpp:1101">

<![LOG[Task Sequence Manager could not initialize Task Sequence Environment. code 80070002]LOG]!><time="17:06:01.663+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="tsmanager.cpp:1289">

<![LOG[Task sequence execution failed with error code 80070002]LOG]!><time="17:06:01.663+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="tsmanager.cpp:785">

<![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="17:06:01.663+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tsmanager.cpp:578">

<![LOG[successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="17:06:01.678+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="environmentlib.cpp:855">

<![LOG[Executing command line: C:\Program.exe Files\SMS_CCM\TsProgressUI.exe /Unregister]LOG]!><time="17:06:01.694+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="commandline.cpp:805">

<![LOG[CreateProcess failed. Code(0x80070002)]LOG]!><time="17:06:01.694+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="commandline.cpp:997">

<![LOG[Command line execution failed (80070002)]LOG]!><time="17:06:01.694+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="commandline.cpp:1221">

<![LOG[Getting active request access handle]LOG]!><time="17:06:01.772+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:2991">

<![LOG[Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002]LOG]!><time="17:06:01.772+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:3006">

<![LOG[Error - could not get package and program IDs. code 80070002]LOG]!><time="17:06:01.772+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:3034">

<![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="17:06:01.788+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="utils.cpp:3061">

<![LOG[Policy cleanup done]LOG]!><time="17:06:01.881+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:2515">

<![LOG[Error executing Task Sequence Manager service. Code 0x80070002]LOG]!><time="17:06:01.881+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="tsmanager.cpp:452">

<![LOG[sending error status message]LOG]!><time="17:06:01.881+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tsmanager.cpp:456">

<![LOG[MP name must be set in an environment variable]LOG]!><time="17:06:01.897+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="tsmanager.cpp:1554">

<![LOG[Non fatal error sending status message. Code 0x80004005]LOG]!><time="17:06:01.897+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="tsmanager.cpp:1720">

<![LOG[successfully finalized logs to SMS client log directory from C:\Program Files\SMS_CCM\Logs]LOG]!><time="17:06:01.897+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tslogging.cpp:1536">

<![LOG[Resuming SMS Components]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tsmanager.cpp:1021">

<![LOG[Waiting for CcmExec service to be fully operational]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:4097">

<![LOG[CcmExec service is up and fully operational]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:4102">

<![LOG[Getting SoftwareDistribution pause cookie]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:2675">

<![LOG[Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2691">

<![LOG[Error - could not get pause cookie for SoftwareDistribution. code 80070002]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2711">

<![LOG[Getting SoftwareUpdates pause cookie]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:2675">

<![LOG[Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2691">

<![LOG[Error - could not get pause cookie for SoftwareUpdates. code 80070002]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2711">

<![LOG[Getting System Health Agent pause cookie]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:2675">

<![LOG[Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2691">

<![LOG[Error - could not get pause cookie for System Health Agent. code 80070002]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2711">

<![LOG[Getting active request access handle]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="utils.cpp:2832">

<![LOG[Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002]LOG]!><time="17:06:01.913+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2847">

<![LOG[Error - could not get asccess handle for the active request. code 80070002]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="3" thread="3572" file="utils.cpp:2865">

<![LOG[iIDFromString() failed.]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="swdupdatescontroller.cpp:298">

<![LOG[Task Sequence Manager could not release active TS request. code 80004005]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="swdupdatescontroller.cpp:326">

<![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="utils.cpp:2744">

<![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="utils.cpp:2744">

<![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="utils.cpp:2744">

<![LOG[Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="utils.cpp:2892">

<![LOG[stopping Task Sequence Manager service]LOG]!><time="17:06:01.928+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tsmanager.cpp:487">

 

the smspxe.log gives the following error:

 

WARNING: _SMSTSSiteSigningCertificate Not Set. This might cause client failures in native mode. smspxe 25/03/2009 11:21:29 2692 (0x0A84)

WARNING: _SMSTSRootCACerts Not Set. This might cause client failures in native mode. smspxe 25/03/2009 11:21:29 2692 (0x0A84)

WARNING: _SMSTSCertStoreName Not Set. This might cause client failures in native mode. smspxe 25/03/2009 11:21:29 2692 (0x0A84)

WARNING: _SMSTSCertSelection Not Set. This might cause client failures in native mode. smspxe 25/03/2009 11:21:29 2692 (0x0A84)

Share this post


Link to post
Share on other sites

as it says

 

Failed to restore logs from cache. Execution history may be lost.]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="2" thread="3572" file="tsmanager.cpp:390">

<![LOG[Task Sequence Manager executing as service main thread]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="tsmanager.cpp:417">

<![LOG[Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="environmentscope.cpp:250">

<![LOG[Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created]LOG]!><time="17:06:01.584+-60" date="03-09-2009" component="TSManager" context="" type="1" thread="3572" file="environmentscope.cpp:250">

<![LOG[Failed to locate the local data path. The files needed to resume the task sequence are missing. This could be because the task sequence finished while in Windows PE. Please check the largest available partition for SMSTSLog\smsts.log file for more information.

The system cannot find the file specified. (Error: 80070002; Source: Windows

 

so can you search your hard disc for the FULL smsts.log file

 

start by looking in X:\Windows\Temp\SMSTSLog\ and C:\SMSTSLog and C:\_SMSTaskSequence.

 

once you find the log, post it all here as an attachment or email it to me

 

cheers

anyweb

Share this post


Link to post
Share on other sites
as it says

 

 

 

so can you search your hard disc for the FULL smsts.log file

 

start by looking in X:\Windows\Temp\SMSTSLog\ and C:\SMSTSLog and C:\_SMSTaskSequence.

 

once you find the log, post it all here as an attachment or email it to me

 

cheers

anyweb

 

Ah logs in WINPE build, I was checking my SCCM server.

Btw: My wds server is in native mode and my SCCM site in mixed mode, is this good?

 

EDIT: I was in CMD at WINPE but it just rebooted ...

Share this post


Link to post
Share on other sites

try and get me the winpe logs and i'll be able to help

 

WDS in native mode is fine, SCCM in mixed mode, also fine

 

cheers

anyweb

Share this post


Link to post
Share on other sites
try and get me the winpe logs and i'll be able to help

 

WDS in native mode is fine, SCCM in mixed mode, also fine

 

cheers

anyweb

 

alright: I managed to get the logs and looked at it with SMS trace.

 

This one failed:

 

SMSPXEIMAGES$ Failed to connect to "\\servername\SMSPXEIMAGES$\SMSPKG\SMS00001"

Share this post


Link to post
Share on other sites

then you need to verify that you have distributed your boot images to both the normal DP and PXE DP

Share this post


Link to post
Share on other sites
then you need to verify that you have distributed your boot images to both the normal DP and PXE DP

 

I did distribute the DP's. I can acces the share when i am in cmd (winpe).

 

Any suggestion? Should I create new DP's ? Can I do that ?

smsts.txt

Share this post


Link to post
Share on other sites

you have to fix this

 

Failed to connect to "\\Servername.domain.be\SMSPXEIMAGES$\SMSPKG\CRO00001" (1909)

 

then

 

Content location request for CRO00001:11 failed. (Code 0x80040103)

 

find out what package that is (CRO00001:11) and re-distribute it...

Share this post


Link to post
Share on other sites
you have to fix this

 

 

 

then

 

 

 

find out what package that is (CRO00001:11) and re-distribute it...

 

Thats my bootimage X86 and I distribute it towards the 2 DP's. (still no luck)

 

But when I PXE boot I see my comp saying x64 architecture? (could that be the problem? should I use X64 boot file?)

 

EDIT: With X64 boot image I get another error: Failed to download pxe variable file. code (0x000001)

 

I think this issue, not getting an ip in WINPE with the X64 boot image and intel driver:

http://social.technet.microsoft.com/Forums...3529b3f/#page:1

http://blogs.technet.com/mcs-ireland-infra...nager-2007.aspx

 

But that is something for friday.

 

EDIT: Imported a new X64 Intel driver into the X64 boot images and I am getting an IP now. But I have the same issue as above. Not able to acces my share ://

Share this post


Link to post
Share on other sites

post your new smsts.log file and i'll look at it to see whats wrong now

 

cheers

anyweb

Share this post


Link to post
Share on other sites
post your new smsts.log file and i'll look at it to see whats wrong now

 

cheers

anyweb

 

Will post it when I am back at work. So I'll post every log pxe & smsts log.

Share this post


Link to post
Share on other sites

delete your X86 bootimage package and recreate it, then distribute it, then update the DP's

 

then try again,

 

cheers

anyweb

Share this post


Link to post
Share on other sites
delete your X86 bootimage package and recreate it, then distribute it, then update the DP's

 

then try again,

 

cheers

anyweb

I will try your suggestion later.(if this step below doesn't get solved)

I am one step forward now.

 

I set the Network acces account as domain account. This let me go one step further in acces rights towards the share.

Now I am getting the following error:

 

Task Sequence: Capture "name" has failed with the error code (0x00000032).

 

Here is the log file.

smsts.log

Share this post


Link to post
Share on other sites
I will try your suggestion later.(if this step below doesn't get solved)

I am one step forward now.

 

I set the Network acces account as domain account. This let me go one step further in acces rights towards the share.

Now I am getting the following error:

 

Task Sequence: Capture "name" has failed with the error code (0x00000032).

 

Here is the log file.

 

post-1-1222694919.jpg

 

This is my tasksequence but i removed the "Build the reference machine" part.

What I am trying to do is capturing a regular pc in the domain using pxe boot. I thought it was possible :o

 

Maybe that's why i am getting these errors ...

 

I am just trying a regular "Build & Capture" and it is currently formatting disk C and it failed bringing the pc in the domain. Seems a network driver issue.

Share this post


Link to post
Share on other sites

its not capturing because youve entered some details incorrectly, what did you enter in the capture settings ???

Share this post


Link to post
Share on other sites
its not capturing because youve entered some details incorrectly, what did you enter in the capture settings ???

Capture the reference machine

Join workgroup (joining domain - OU with admin credentials)

prepare configmgr client (changed nothing)

prepare OS (changed nothing)

Capture the reference machine (filled in UNC path of the SCCM share for capturing the OS and filled in the domain admin account)

 

Thats about it.

Share this post


Link to post
Share on other sites

actually here is where your problem starts

 

The step (Prepare ConfigMgr Client) must be running in full OS

 

Failed to run the action: Prepare ConfigMgr Client.

The request is not supported. (Error: 80070032; Source: Windows)

 

can you please verify what boot image you are using to capture with (32 or 64)

Share this post


Link to post
Share on other sites
actually here is where your problem starts

 

 

 

can you please verify what boot image you are using to capture with (32 or 64)

 

Tried bot 32 and 64bit boot image.

 

Always the same error. Created new task sequence etc but no advance.

 

Guess I am stuck now.

 

edit: log files from my failed capture task included.

smsts.log

smsts_.log

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...