OSD to Surface fails to PXE Boot and returns PXEGetPXEData Failed with 0x80004005

Scenario: When trying to Image Windows 8.1 to a Surface Pro, Surface Pro 2 and Surface Pro 3 I have downloaded the latest Surface Firmware and Drivers (August 18th 2014 I believe), the NIC's are in the x64 PXE Boot Image. I have verified that no DHCP Option
67 is set, and that SpanningTree PortFast is enabled. All other Images function correctly, Windows 7 Sp1 works. We use the Microsoft USB NIC, and we PXE boot and download the PXE Image fine, then it comes into windows and goes to detect the NIC, at which point
it fails and reboots.
The Surface has had Firmware update on it to the latest.
It appears the NIC just stops working, which makes me think that the latest Driver pack for Surface does not contain the PXE boot versions for their NIC.
Trying the Docking Station (which utilizes NIC ASIX AX888772) exhibits the same problem.
The NIC stays active until the OSD Screen comes up, it fails trying to load the Surface NIC though (or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which
make me think this is the case even more so.
Doing a USB PXE Boot also fails to load the NIC.
Going to F8 and doing IPCONFIG /RENEW verifies the NIC is not active.
I see tons of postings on the Surface being a nightmare to image.
Errors:
Failed to Download pxe variable file. Code (0x0000001)
PXEGetPXEData Failed with 0x80004005
Anybody having any other experiences out there, or have anything else they could think to try?
David Baur

(or the NICs in the Driver pack they just released do not include a PXE Boot Driver...the Drivers once imported do not show any as being Boot Critical...which make me think this is the case even more so.
There are no "PXE boot versions" of drivers at all. What you described just indicates that there is no driver in winpe that matches the hardware. WinPe is based on the respective version of the full os so you have to add Win8.x drivers to the boot image.
The architecture also has to match. Have you added NIC drivers to the boot image at all?
NIC drivers are never boot critical if I am not mistaken.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

PXE Boot and RIS not working

I'm trying to boot a toshiba SP6100 from ris but getting
PXE-T01:File not found
PXE-E3B: TFTP error - File not found
PXE-MOF: Exiting Intel PXE ROM.
No problem what so ever when booting other mashies (Other brands).
When trying to boot from a Remote boot disk i get:
Error: Could not found a supported network card.....
PC is running latest bios (1.9)
Any suggestions?

Hi
I have found an interesting Microsoft Knowledge Base Article Q304992.
It deals with the PXE Boot and RIS server method, perhaps it could help you!
Pelox

Trying to do pxe-boot and kickstart install on sunfire x4150 using NET MGT

I am trying to do pxe-boot and kickstart install on sunfire x4150 using NET MGT port. Is this doable? The eth0 port works fine, but the NET MGT port does not seems working. It gets the IP, gateway, mask and other info, but would not start the install. I heard that the NET MGT port is not capable of doing pxe-boot, please let me know if this is true.
Your help is appreciated.
Sheng

The NET MGT port is for the ILOM. That interface is not visible to the Host OS so no it cannot be used for host communication including PXE booting...

My widget browser keeps showing "failed getting widget feed" and keeps saying "failed getting widget feed and make sure you are connected to the internet" when I am connected to the internet. How do I fix this?

my widget browser keeps showing "failed getting widget feed" and keeps saying "failed getting widget feed and make sure you are connected to the internet" when I am connected to the internet. How do I fix this?

Widget Browser is gone. Adobe pulled the plug on it quite a while ago.
See this related discussion from earlier today.
Widgets a Gone Gone
Nancy O.

Surface Pro 3 PXE Boot Error

Hi there,
I am using MDT 2013 on a WDS 2008 R2 and everytime i tried to image the tablet via PXE boot through the Surface Pro 3 ethernet adapter, i get this error:
Wizard Error:
A connection to the deployment (my deployment share) could not be made.
The following network device did not have a driver installed.
PCI\VEN_11AB&DEV_2B38&SUBSYS_045E0001&REV_00
Retry: Try again to connect to the deployment share.
Cancel: Give up, cancelling any in-progress task sequence.
PLEASE HELP!

I bought a Belkin USB2.0 adapter and connected to my Pro 3 while the Pro 3 ethernet adapter is connected as well. So 2 network cables are needed. I pxed boot using the Pro 3 ethernet adapter and deploy the image using the Belkin2.0 adapter. Error didnt
come back and deployment was successful. I mean this is a workaround but it works in my environment. The Belkin2.0 drivers are in WinPE and MDT.

PXE Boot and Task Sequence slowness

I have been assured that our subnet 10.10.156.x is all 100MB. Yet when I PXE up and run our CM2012 task sequence it takes over 1 hour
just to resolve the task sequence. Forget trying to actually do the OSD since that would take about 6 hours.
Before I go back to networking I wanted to explain what I did to this forum to make sure I did things right.
Our CM2012 server is also our one and only MP. It is also a DP for most of our small company. Our CM2012 server is on subnet 10.10.141.x. Yes, it has a static IP address.
Our 10.10.156.x subnet is in the same phsycal building as the 10.10.141.x subnet. .141 is for servers and .156 is for workstations.
We have a server that holds all of our DHCP scopes. On this DHCP server I found the 10.10.156.x scope. I added the following:
066 Boot Server Host Name: 10.10.141.54 (which is our CM2012 server)
067 Bootfile name: \smsboot\x64\wdsnbp.com
When I go to any workstations on the 10.10.156.x subnet I PXE boot up, it does see 10.10.141.54 and it launches the CM2012 OSD task wizard. But as I said it is slower than glue and un-useable at this time.
Did I setup this up right or do I need to do something else? Or is our networking team full of it?
mqh7

Ok, I did that. I saw no errors and in fact it all looked fine. It just took a long time. so I talked to our top network tech. He said the IP address means nothing. It is all about what the wall Ports are connected too in the
server/network room. So this does appear to be an internal networking problem we need to solve.
last question: If you have 100MB ports is that considered slow for a CM2012 OSD? our .WIM and all installed applications are close to 5GB of data. So is 100MB good or should it all be Gigibit?
mqh7

PXE boot and video mode

Hello all,
I posted about this problem a while ago but now I have more information.
6.5 SP2 IR1.
The problem: Booting from CD results in a video mode with far more lines and
column than booting PXE. PXE is always 80x25, on many different hardware
types. I want it to be like the CD.
Theoretically, the video mode is controlled by the vga= parameter on the
kernel's command line. For PXE, the kernel command line comes from <imaging
server>\sys\tftp\cmds, various files therein. Here are the contents of a
typical file:
KERNEL boot/linux
APPEND initrd=boot/initrd vga=0x314 install=tftp://$TFTPIP/boot
rootimage=/root PROXYADDR=$PROXYADDR TFTPIP=$TFTPIP splash=silent
PXEBOOT=YES mode=5
Notice the vga= parameter.
I can modify this vga parameter any way I like, without effect. I have
tried:
- removing the parameter entirely
- setting it to ask
- setting it to vga_ask
- setting it to single-digit numbers e.g. 1, 2
- setting it to other 0x3nnn options
- setting it to extended
It should be possible for anybody to replicate this simply by changing the
vga parameter in one of your CMD files and booting that particular PXE
option. I suggest using "ask" as it is the one that would give the most
visibly obvious evidence of working or not working.
The boot loader for PXE appears to be linld.com. So, I took my PXE
materials and Novell's linld (to ensure same version) and ran them from DOS.
When I run them from DOS, the vga= parameter DOES have an effect; it behaves
exactly as it should.
So, the situation appears to be that linld launched via PXE ignores the vga
parameter while linld launched manually from DOS does not, on the same
hardware.
Working with linld under DOS yielded some interesting information. The text
files specifying the kernel command line parameters for PXE are not actually
in anything remotely like the format linld requires. Having KERNEL and
APPEND keywords is more characteristic of other boot loaders. If you run
linld without parameters under DOS, it gives you very terse command line
information, which is as follows:
LINLD v0.97
Syntax:
LINLD [image=<file>] [initrd=<file>] [vga=vgamode] [cl=<kernel cmdline>]
vgamode: ask,extended,normal or dec/oct/hex number
Use quotes: "cl=..." if you need spaces in cmdline
Use cl=@filename to take cmdline from file
So compared to the CMD file provided for PXE, what linld would really want
is this:
linld image=boot/linux initrd=boot/initrd vga=0x314 [email protected]
where params.txt would contain:
install=tftp://$TFTPIP/boot
rootimage=/root
PROXYADDR=$PROXYADDR
TFTPIP=$TFTPIP
splash=silent
PXEBOOT=YES
mode=5
(It's worth noting that things are actually even slightly more complicated,
because the variables used in the CMD file (e.g. $PROXYADDR) don't actually
work; I have not found any way to use variables on the command line.)
All this tells me that before Novell launches linld, it is internally
processing the contents of these CMD files and spitting out a command line
that linld can really work with. My experience indicates that the vga
parameter is being incorrectly handled in this process.
I cannot figure out where the DOS environment that must exist during the PXE
boot process is coming from. (There must be a DOS environment, because
linld is a DOS Linux launcher.) It was easy to tell with the old preworx
materials, because you could see the .bin files which were nothing but
images of DOS boot floppies; it was even possible to open them in
third-party PXE utilities. I see no comparable files in the current boot
materials. The only other interesting file is loadlin.dnx, but I suspect it
is not involved because the old preworx process had DNX files as well and
they served a different purpose. Consequently I can't look at what is
happening when linld is launched, so I can't get any further in trying to
figure out the problem.
I would be very interested to know whether anybody out there can get their
PXE materials to respond sensibly to vga=ask.
If you can, I'd be interested to know the dates and times of all the backend
NLMs, in case my problem is due to incorrect updating/version mismatch.
If anybody can shed light on the innards of what happens when linld is
launched during PXE boot, I would love to know.
Thanks,
Lisa.

Lisa,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

SLM2005: PXE booted clients freeze up, fail to reboot

I use the SLM2005 at a couple of locations, but at one of them the Thin Clients behind it freeze up and will not PXE boot when cycled. It never worked quite right, and I always assumed it was some bug in Linux LTSP, but the problem went from intermittent and infrequent to intermittent and frequent to persistent in the span of about three weeks. Bypassing the switch seems to resolve it. My assumption is now that the switch is in some way defective, especially in light of the fact that a nearly identical setup at another location does not suffer from this issue.
The problem is that Cisco phone support has expired for this product, and at $75 it is about the same price as a new one.
I was thinking about trying a firmware upgrade, and just messing around with the firmware in general, but as they say "time is money". When I buy a switch, managed or not, I expect it to "just work".
What would you guys do if you were me?

I've also just encountered a failure to associate using LXE MX9 scanners with a Summit card. Moving the setting from CCX FULL to CCX OPTIMIZED in the SCU resolves but is not a recommendation from Honeywell/LXE. have you had any response from TAC or Teklogix?

SATA problem at boot and resume: softreset failed (1st FIS failed)

Hi all,
Since a kernel update about a month ago, and an accompanying reboot, I've been seeing "softreset failed (1st FIS failed)" messages at boot time. These slow boot by twenty seconds or so and, at times, I see messages about reducing SATA speed to 1.5Gb/s. I see similar messages on resuming from sleep.
I want to know if this problem suggests HDD or SATA controller failure. Smartmon tools isn't showing problems with the drive, as far as I can tell. I don't know how to test the motherboard, controller or link speed.
So:
1) Is anyone else seeing this?
2) What is FIS?
3) What other tests can I do?
Thanks!

I am having the same issue. This started after upgrading from kernel 3.16.4-1-ARCH to 3.17.1-1-ARCH.
[root@sirschmoopy ~]# journalctl -b | grep ata10
Nov 08 04:32:40 sirschmoopy kernel: ata10: SATA max UDMA/133 abar m8192@0xfe7fe000 port 0xfe7fe180 irq 18
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: limiting SATA link speed to 1.5 Gbps
Nov 08 04:32:40 sirschmoopy kernel: ata10: softreset failed (1st FIS failed)
Nov 08 04:32:40 sirschmoopy kernel: ata10: reset failed, giving up
[root@sirschmoopy ~]# lspci
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge
00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (ext gfx port 0)
00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 4)
00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5)
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 41)
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40)
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
00:16.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:16.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control
01:00.0 VGA compatible controller: NVIDIA Corporation GF100 [GeForce GTX 470] (rev a3)
01:00.1 Audio device: NVIDIA Corporation GF100 High Definition Audio Controller (rev a1)
02:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 03)
03:00.0 SATA controller: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
03:00.1 IDE interface: JMicron Technology Corp. JMB361 AHCI/IDE (rev 02)
04:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Last edited by dmartins (2014-11-08 10:32:15)

Satellite U300-13U fails to boot and Recovery disc fails to work too

Hi All,
I have the above computer (or should I say my wife) & it has been nothing but a right pain since the first day we got it.
I have had it about 2 years & must have had to reformat the HD at least 6-8 times using the Product Recovery Disc as laptop wouldn't boot.
The laptop runs Vista.
Anyway problem I have now is that once again laptop fails to boot but for some reason Product Recovery disc also fails to work.....
What can I do...
I have read on various forums that it might work if I reformat the HD first using some s/w on a bootable CD but how/ what S/W do I use.....?
The laptop has a 160Gb SATA HD installed. How can I check this is all working.
I have no idea if current problem is S/W or hardware related..
Does Toshiba have a utility I can use...?
Many thanks for any help....
John

Hi Paolo,
Thks for the reply. I have made some success since I posted. I actually downloaded Ubuntu & created a boot up disk. I have managed to successfully load this alongside the Vista (which doesn't work) & everything seems OK - so all I can say is that it must be somekind of s/w issue or perhaps damaged sectors or something on the Vista install.
I am happy to use Ubuntu - it will be interesting to see if I have to do anymore reformats in future...
Thks, John

Boot and OS install issues with K8T Neo2 F

Can anybody shed light on my difficulties?
Assembled a new computer yesterday. First power-on produced nothing except 3 (2,3,4) red leds on d-bracket. After reading several postings, tried the following:
Swapped around memory modules;
Did repeated JBAT1 data clears (NB if you happen to get a board with the V1.0 user guide, note that the JBAT1 diagram appears upside down - pin one is closest to the SATA slots (page 2 - 24). The MSI downloadable user guide (V1.2) has that error corrected (page 2-25)
The only memory config that doesn’t produce three red leds is with one 512 stick installed in channel 3 (green).
Can now get to the point where Windows XP boots to the point where install is about to start, and then advises me that it can’t find a hard disk!
Have dis/reconnected the sata cable (using different cables) and checked the bios setup but can find nothing strange except that setup refers to the hard disk as BBS 0 (RAID) ST3120827AS - the reference to “RAID” worries me.

Paul, there have been people here that have had to strip their system down to the bare minimum hardware to get windows to complete the install, so try that. I had trouble completing my windows install as long as I was trying to install the RAID drivers at F6. So I ignored the prompt at F6 and windows installed fine. Then I installed my RAID drivers afterward.
These things are extremely sensitive when it comes to memory. I had the same problem you are having. Mine was cured by a BIOS upgrade to ver. 3.3. The simplest way to do it is to use "Live Watch". It will locate BIOS ver 3.3 for you, and download it to a floppy along with the flash program, and make it bootable all in one easy step. Then all you have to do is boot from the floppy you just made, and follow the instructions. Very simple.
I've read all these stickies and posts now going way back, and IMHO anyone who wants to use RAM thats not on the list should do so at their own risk. Interestingly enough, the recommended list from MSI is not the same as the list from AMD. And the memory manufacturers have their own lists of RAM that they say will work with this board. I'm using 2x 512 sticks of GEIL from the MSI recommended list.
Check out these links to see what I mean. By the way, if you haven't noticed, most of the older posts about memory problems are with respect to the K8T Neo FIS2R which is a socket 754 single channel board, so although they are similar, they're not the same. My point is just because his K8TNeo FIS2R works fine with brand "X" RAM doesn't mean your K8T NEO2 FIR will.
http://www.msi.com.tw/html/products/mainboard/testreport_pdf/6702E/memory.pdf
http://www.crucial.com/store/listparts.asp?Mfr%2BProductline=MSI+%28Micro+Star%29%2B+Motherboards&mfr=MSI+%28Micro+Star%29&cat=RAM&model=MS-6702E+%28K8T+Neo2-FIR%29&submit=Go
http://www.mushkin.com/epages/mushkin.storefront/EN/product/991140
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Athlon_64_Unbuffered_DIMM_AVL.pdf
http://www2.amd.com/us-en/Processors/TechnicalResources/1,,30_182_869_9460%5e9461,00.html?1094454813
Good luck!

MacBook Pro 13 2010 running Mountain Lion: will not boot and shows a folder with a flashing question mark. Will not start in 'safe mode' i.e holding shift on start up - nor can I call up any utilities with the OSX shortcuts. Any thoughts?

Following an automatic update, the machine wouldn't boot. Screen came on (shows white) - then either showed a 'No-Entry' Sign and a spinning cog, or a folder with a qusetion mark. I tried to start the machine in different modes ( eg. holding shift after the tone ) but nothing worked. after leaving the machine alone for 1 hour. It worked perfectly again. I did a 'verify disk' check which found no problems. 2 hours later it then froze ( In - Photoshop). Could not force quit, so shut down, and have not been able to boot again since (white lit screen - flashing folder with question mark) . I have also taken the hard drive out and checked the connections which seem fine. Any suggestions? - Is the Hard Drive dead. : other info : It was also running parallels 8, with Windows 7. at the time of the update....

This article may help: A flashing question mark appears when you start your Mac.

Dequeue Business event (AQ or AppsAdapter) in OSB and return results fails

I am new to OSB. The scenario is to publish out the results to SFDC (SalesForce.Com) any changes in EBS.
The Dequeueing works well within OSB. However when I am trying to return the results back.. It is failing. Is it because Dequeueing wsdl has only an input structure
and does not have an output structure?

I get the following error message
BEA-382040: Failed to set the value of context variable "body". Value must be an instance of {http://schemas.xmlsoap.org/soap/envelope/}Body. So basically the input definition of the Event is
<soapenv:Envelope   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header   xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soapenv:Body>
<even:WF_EVENT_T   xmlns:even="http://xmlns.oracle.com/xdb/APPS/EventListener">

<PRIORITY>1.051732E7</PRIORITY>

<SEND_DATE>string</SEND_DATE>

<RECEIVE_DATE>string</RECEIVE_DATE>

<CORRELATION_ID>string</CORRELATION_ID>

<PARAMETER_LIST>

<PARAMETER_LIST_ITEM>

<NAME>string</NAME>

<VALUE>string</VALUE>
</PARAMETER_LIST_ITEM>
</PARAMETER_LIST>

<EVENT_NAME>string</EVENT_NAME>

<EVENT_KEY>string</EVENT_KEY>

<EVENT_DATA>string</EVENT_DATA>

<FROM_AGENT>

<NAME>string</NAME>

<SYSTEM>string</SYSTEM>
</FROM_AGENT>

<TO_AGENT>

<NAME>string</NAME>

<SYSTEM>string</SYSTEM>
</TO_AGENT>

<ERROR_SUBSCRIPTION>ZQ==</ERROR_SUBSCRIPTION>

<ERROR_MESSAGE>string</ERROR_MESSAGE>

<ERROR_STACK>string</ERROR_STACK>
</even:WF_EVENT_T>
</soapenv:Body>
</soapenv:Envelope>
and then I replace the body with
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
</soap:Header>
<soapenv:Body>
<get:GetSystemDateInput xmlns:get="http://xmlns.oracle.com/pcbpel/adapter/db/GetSystemDate"/>
</soapenv:Body>
</soapenv:Envelope>
before the call to the business service GetSystemDate and then I get this error
<soapenv:Envelope   xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>
BEA-382040: Failed to set the value of context variable "body". Value must be an instance of {http://schemas.xmlsoap.org/soap/envelope/}Body.
</faultstring>
<detail>
<con:fault   xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382040</con:errorCode>
<con:reason>
Failed to set the value of context variable "body". Value must be an instance of {http://schemas.xmlsoap.org/soap/envelope/}Body.
</con:reason>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>stage1</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

IMac won't boot and has flashing folder with question mark on gray screen

I just bought a new iMac. I have been trying all week (with no success) to transfer files and apps from my previous iMac. The last time I tried to transfer, I used target mode on the old computer. It looked as if it was finally working, so I left with 2+ hours remaining on the transfer. When I returned, the computer was frozen and nothing would work. So I held the power button to turn it off. When I tried to turn it back on, there was only a gray screen with a flashing folder with a question mark. I feel like I have tried everything listed in other discussions. The only thing I am not able to try is to reinstall Lion because the new computer did NOT come with an OSX disc of any type. Any suggestions?

Go to > OS X Lion: About Lion Recovery

Conundrum - PXE boot fails vs. "reinstall OS from software center" succeeds

Hi All.
I am facing a bit of a conundrum..
In our offices I am seeing some strange behaviour when trying to PXE boot into a TS to reinstall or install OS.
If I use F12/PXE boot then the deployment fails during OSD.
If I take a client (the same client as I tried pxe booting with) that is fully installed and reinstall OS via software center then the deployment completes.
Any ideas what could be wrong?
Kindest regards, Martin

Daniel:
Clients are both laptops & desktops.
I "feels" like it's the network that's acting up but I really can't see where.
PXE boot works.. it's not until it tries to apply the OS...
whether it's a timeout or what it is I cannot say..
Gerry: After all will you be likely to rebuild your entire estate in-situ any time soon?
You know... we are actually On the verge" of upgrading & Streamlining our entire network infrastructure..
But I'd still love to solve the problem..
We never had this issue when we only had MDT as deployment tool.
it's not until sccm came into the picture that this issue has arisen.
Kindest regards, Martin

OSD to Surface fails to PXE Boot and returns PXEGetPXEData Failed with 0x80004005

Similar Messages

Maybe you are looking for