Error ImageX - the system cannot find the file specified

[SoultakerPT]

Hello and greetings from Portugal!

I'm having a little problem here when trying to create a WIM file with MDT LTI process.

I'm getting an error during the Create WIM phase.

I've noticed through the ZTIBackup_imagex.log where the errors occurs but I just can't figured out why this is happening.

The file that imageX complains about it's on the right location, the machine didn't lost network and there's enough space on server.

Here's the log file:

ImageX Tool for Windows
Copyright (C) Microsoft Corp. All rights reserved.
Version: 6.1.7600.16385
Files/folders excluded from image capture by default:
 \$windows.~bt
 \$windows.~ls
 \winpepge.sys
 \Windows\CSC
 \Recycled
 \Recycler
 \$Recycle.Bin\*
 \System Volume Information
 \pagefile.sys
 \hiberfil.sys

Turning on VERIFY option for network share
Scanning files and directories...
[   0% ] Capturing progress 
[   1% ] Capturing progress 
[   2% ] Capturing progress: 14:42 mins remaining 
[   3% ] Capturing progress: 25:33 mins remaining 
[   4% ] Capturing progress: 45:00 mins remaining 
[   5% ] Capturing progress: 53:24 mins remaining 
[   6% ] Capturing progress: 58:25 mins remaining 
[   7% ] Capturing progress: 1:00:55 hrs remaining 
[   8% ] Capturing progress: 1:01:53 hrs remaining 
[   9% ] Capturing progress: 1:00:53 hrs remaining 
[  10% ] Capturing progress: 60:00 mins remaining 
[  11% ] Capturing progress: 59:27 mins remaining 
[  12% ] Capturing progress: 59:02 mins remaining 
[  13% ] Capturing progress: 58:33 mins remaining 
[  14% ] Capturing progress: 58:50 mins remaining 
[  15% ] Capturing progress: 58:23 mins remaining 
[  16% ] Capturing progress: 58:11 mins remaining 
[  17% ] Capturing progress: 57:27 mins remaining 
[  18% ] Capturing progress: 56:16 mins remaining 
[  19% ] Capturing progress: 54:34 mins remaining 
[  20% ] Capturing progress: 52:20 mins remaining 
[  21% ] Capturing progress: 50:23 mins remaining 
[  22% ] Capturing progress: 48:47 mins remaining 
[  23% ] Capturing progress: 46:54 mins remaining 
[  24% ] Capturing progress: 45:09 mins remaining 
[  25% ] Capturing progress: 43:50 mins remaining 
[  26% ] Capturing progress: 42:39 mins remaining 
[  27% ] Capturing progress: 41:16 mins remaining 
[  28% ] Capturing progress: 39:44 mins remaining 
[  29% ] Capturing progress: 38:16 mins remaining 
[  30% ] Capturing progress: 36:54 mins remaining 
[  31% ] Capturing progress: 36:03 mins remaining 
[  32% ] Capturing progress: 35:31 mins remaining 
[  33% ] Capturing progress: 34:50 mins remaining 
[  34% ] Capturing progress: 33:57 mins remaining 
[  35% ] Capturing progress: 32:55 mins remaining 
[  36% ] Capturing progress: 37:37 mins remaining 
[  37% ] Capturing progress: 46:18 mins remaining 
[  38% ] Capturing progress: 49:34 mins remaining 
[  39% ] Capturing progress: 50:10 mins remaining 
[  40% ] Capturing progress: 49:30 mins remaining 
[  41% ] Capturing progress: 48:14 mins remaining 
[  42% ] Capturing progress: 46:43 mins remaining 
[  43% ] Capturing progress: 45:07 mins remaining 
[  44% ] Capturing progress: 43:30 mins remaining 
[  45% ] Capturing progress: 41:55 mins remaining 
[  46% ] Capturing progress: 40:23 mins remaining 
[  47% ] Capturing progress: 38:54 mins remaining 
[  48% ] Capturing progress: 37:28 mins remaining 
[  49% ] Capturing progress: 36:05 mins remaining 
[  61% ] Capturing progress: 28:44 mins remaining 

[ ERROR ] D:\Maestro\VirtualMachines\Posto Balcao\Virtual Hard Disks\PostoBalcao.vhd (Error = 2)

Error imaging drive [D:\]

The system cannot find the file specified. 

[arwidmark]

I have seen these error multiple times at multiple customers. Most times it has been that the machines are running out of resources (like when usimg vm's and having the client and the server on the same physical host) or when having poor network equipment.

To verify this, simply attach another virtual disk (if it's a vm), or a physical disk if its a physical machine and run imagex manually, storing the wim on the second disk.

Rare exception has been strange ACL's or EFS encrypted files preventing imagex from completing, but again, most times it's related to vm resources or network hickups.

There is a KB article stating this to be related to disk space, that article is incorrect.

/ Johan

[SoultakerPT]

This really is a strange situation because this only happens when this file is there.

I've also turned off antivirus and nothing.

Always the same file and always at 61%.

This is a 9GB file. Don't know if this got something to do with it but I just can't see any bottleneck here. It's direct cable also.

Well...because I've some space free I'll do the imageX directly to another partition just to se what happens!