This post is more than 5 years old
5 Posts
0
5910
Unable to Push or Pull from 5020 or 7020
I am unable to push an image from WDM to my 5020 device, I receive the following error:
1:Merlin-Process-FAILURE [Wed Sep 28 11:39:37 2016][ERROR: Invalid image package. (error code : 101).][ERROR STAGE: Package validation.][REASON: The size of the mbr.img component in package script does not match the actual size of the mbr.img component.][SOLUTION: Re-register the valid image package.] (Package GOGO_0A0F_32GB)
I am also unable to pull an image from my 5020 device, I receive the following error:
1:Merlin-Process-FAILURE [Wed Sep 28 11:11:18 2016][ERROR: Error while uploading MBR file. Http Error code : .][ERROR STAGE: MBR validation.][REASON: Flash is corrupted or improper repository/network configuration.][SOLUTION: Disable anonymous authentication if enabled on software repository under MyWDM virtual directory or check the device flash.]
WDM 5.5.1 (clean upgrade from 5.0 to 5.5 to 5.5.1)
Server OS Windows Server 2008 R2 (dedicated)
Device: 5020 Windows 10 IoT Pro
Boot Agent 3.3.3 for WIE10
HAgent version: 6.3.5.9
eric-w
5 Posts
1
April 12th, 2017 11:00
Update:
Using the MR2 image with the following agents, I am able to push and pull images using a clean install of 5.7.2 on a Windows 2012 R2 server;
Boot Agent 3.4.4
Agent 12.1.4.2
eric-w
5 Posts
0
October 4th, 2016 08:00
I have read somewhere that my issue could be caused by our strict enforcement of NTLMv2. Reaching out to see if anyone else has NTLMv2 enforced and is able to deploy images?
RMontalvo
560 Posts
0
October 17th, 2016 15:00
The 5020 comes with several different Operating Systems installed. It looks like you are trying to install the WiE10 firmware and the message you are getting is that the device does not have enough disk space to fit the image. Verify the following on your thin client:
You may want to contact tech support since I think these issues are related and you may want to run the diagnostics to see if you get any errors.
marcb-2015
6 Posts
0
October 18th, 2016 13:00
I have the same problem here - latest build - with the latest win10 rollup (also latest BootAgent) and the 5020 refuses to pull an image, I'm working with support to resolve this and will post and results...also keeping an eye on this thread in case you find a fix before me :)
marcb-2015
6 Posts
0
October 18th, 2016 20:00
apologies for my wording :)
WDM 5.7 (1277)
5020 (D90Q10)
Image 11.010A08
HAgent 12.0.0.13
commands seem to work ok, i'll give 11.02 a go and report back.
RMontalvo
560 Posts
0
October 18th, 2016 20:00
I tried it and it works for me. Here's what I got:
I don't know if your WDM install is new or if it was working before.
If this is a new installation:
If this was working, run previous steps 3 and 4 above.
COMMENT: Do yourself a favor, and always include version numbers, and do not use "latest". If you need help, verifying what your versions are against what the people who are trying to help you have is impossible, since your "latest" may not be the same as my "latest".
marcb-2015
6 Posts
0
October 19th, 2016 14:00
No luck, still the same problem.
OS Build 11.02
HAgent 12.0.0.113
BootAgent 3.3.8
WDM 5.7
HA logs show nothing strange, just standard heartbeat checking in messages.
WDM Diagnostics are all green
eric-w
5 Posts
0
October 19th, 2016 16:00
Also as a test I have a 7020 brand new in the box. I upgraded it to BootAgent 3.3.8 and HAAgent 6.3.5.17 with the same result. Working with Dell, I will post results if we find any
eric-w
5 Posts
0
December 16th, 2016 14:00
Still same issue, I am trying 5.7.1 now, on the supported OS page it has Windows Server 2012 and Windows Server 2008 R2 Enterprise edition. I am currently using Windows Server 2008 R2 Standard edition. This shouldn't be an issue, just checking.