Capture reference fails, has worked fine previously

[straytoasters]

SCCM 2007 R3.

 

Running a capture TS seems to go through all the right motions but fails after a while. The TS does create a .wim in the location it always has but when you look at the index in the .wim it only shows one part (it should show two). The file size is smaller then the previous captures, as I would expect given that it fails, but still if it is only seeing the first part (that typical 100 meg or so partition that Windows creates) I would expect the .wim to be much smaller. The (failed) .wim is around 3GB, the normal capture I get is around 4GB.

 

In the smsts log I see "failed to run the action : Capture Reference Computer. The system cannot find the file specified. (Error: 00000002; Source: Windows" and a few lines down further there is "unknown host (gethostbyname failed)". It seems to really get hung up on that one...as it keeps repeating that one almost from the start of the TS and after about 30 min it truly gives up and fails. In typical SCCM fashion, it doesn't seem to specify what file it cant find and as for host, since it DOES write a .wim file to the only machine (network share) it calls to, I'm not sure what host it is looking for.

 

In the ZTIBackup log there is this line "Error creating and image of drive D:,rc = 2", and a couple of lines down "ZTI ERROR - Non-zero return code by ZTIBackup, rc=2". In WinPE the D drive is of course the traditional C drive.

 

In the BDD log the same errors are mentioned.

 

In the ZTIBackup_imagex log the errors that come up are "[ERROR] D:\Windows\System32\NlsLexicons000a.dll (error = 53)" and a couple lines later (Error imaging drive [D:\].

 

I did run across this post (using the ZTIBackup log as a key reference) that seems to suggest that the area where ImageX puts its temp files could be the problem. This process has worked fine in that past but this (newer, updated) reference image is larger, however on at least one of the machines I have tried this on has 8GB ram (the article seems to indicate the temp storage is a ramdrive), so unless ImageX puts a default limit on the ramdrive I'm not sure this is the fix. As for the other suggestion on the page (auth issues) I doubt that as the TS IS ABLE to write an (apparently incomplete) .wim to the network share it always has been able to.

 

http://social.technet.microsoft.com/Forums/en-US/907fbcd5-af2d-48e5-a371-70f5526d6c38/cature-image-failing-mdt2010

 

Any suggestions appreciated.

 

StrayToasters