/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


K2000 WIM file capture failure [Error while writing to network: 10054]

03/29/2017 1514 views
Ever since the update to v4, I have not been able to capture a WIM file from my Golden Master.

K-Image capture works fine, but deploying K-Images is painfully slow (but better than nothing).

The error that I am seeing is that it is claiming it is unable to write to the network. (which can't be true if K-Image capture is working fine).

An extra maybe relevant info nugget is that this is a UEFI image of Windows 10.

Here is a copy of the log output: 

2017-03-23 06:54:37-0800 [info] Klonewin - Start [Build: Nov  1 2016 07:49:51]
2017-03-23 06:54:37-0800 [info] ...Capture: True
2017-03-23 06:54:37-0800 [info] ...Deploy: False
2017-03-23 06:54:37-0800 [info] ...ImageName: 35
2017-03-23 06:54:37-0800 [info] ...ImageType: wim
2017-03-23 06:54:37-0800 [info] ...LocalDir: C:\
2017-03-23 06:54:37-0800 [info] ...TempDir:
2017-03-23 06:54:37-0800 [info] Capture Image - Start
2017-03-23 06:54:37-0800 [info] ...Original Capture Location: [C:\]
2017-03-23 06:54:37-0800 [info] ...Drive Size=61109, Space Needed=13862, Available=47247
2017-03-23 06:54:37-0800 [info] ...Creating temp dir: C:\K2_2017-03-23_06-54-37
2017-03-23 06:54:37-0800 [info] ...Capture Directory: C:\
2017-03-23 06:54:37-0800 [info] ...Image File: C:\K2_2017-03-23_06-54-37\C.wim
2017-03-23 06:54:37-0800 [info] ...Temp Directory: C:\K2_2017-03-23_06-54-37
2017-03-23 06:54:37-0800 [info] ...Compression Type: 1
2017-03-23 06:54:37-0800 [info] ...Verification: 0
2017-03-23 06:54:37-0800 [info] ...Capturing...
2017-03-23 06:58:01-0800 [warning] Capture Image Scanning Message: (null) [err = 0]
2017-03-23 07:15:52-0800 [warning] Capture Image Scanning Message: (null) [err = 108666]
2017-03-23 07:15:55-0800 [info] ...Capture complete!
2017-03-23 07:15:55-0800 [info] gOptImageName=35, gOptLocalDir=C:\K2_2017-03-23_06-54-37
2017-03-23 07:15:55-0800 [info] Hashstore Client (Version 4.0.695)-start
2017-03-23 07:15:55-0800 [info] Ready to copy 2 items (5.40 GB).
2017-03-23 07:15:55-0800 [error] Error while writing 11 bytes to network: 10054
2017-03-23 07:15:55-0800 [info] Items processed: 0 (0 B)
2017-03-23 07:15:55-0800 [info] Items transferred: 0 (0 B)
2017-03-23 07:15:55-0800 [error] Error while writing 37 bytes to network: 10054
2017-03-23 07:15:55-0800 [info] Hashstore Client-end [0]
2017-03-23 07:15:55-0800 [error] Failed to complete successfully.
2017-03-23 07:15:55-0800 [error] Error while writing 0 bytes to network: 10054
2017-03-23 07:15:55-0800 [info] ...Deleting image dir: C:\K2_2017-03-23_06-54-37
2017-03-23 07:15:55-0800 [info] Klonewin - Done, exit code: -1

And here is the log output of a sucessful K-Image capture:

2017-03-23 07:16:37-0800 [info] Klonewin - Start [Build: Nov  1 2016 07:49:51]
2017-03-23 07:16:37-0800 [info] ...Capture: True
2017-03-23 07:16:37-0800 [info] ...Deploy: False
2017-03-23 07:16:37-0800 [info] ...ImageName: 36
2017-03-23 07:16:37-0800 [info] ...ImageType: k-image
2017-03-23 07:16:37-0800 [info] ...LocalDir: C:\
2017-03-23 07:16:37-0800 [info] ...TempDir:
2017-03-23 07:16:37-0800 [info] Hashstore Client (Version 4.0.695)-start
2017-03-23 07:17:41-0800 [info] Ready to copy 129958 items (17.07 GB).
2017-03-23 07:58:25-0800 [info] Items processed: 129958 (17.07 GB)
2017-03-23 07:58:25-0800 [info] Items transferred: 5236 (3.17 GB)
2017-03-23 07:58:25-0800 [info] Hashstore Client-end [1]
2017-03-23 07:58:25-0800 [info] Copy completed successfully.
2017-03-23 07:58:25-0800 [info] Klonewin - Done, exit code: 0
2017-03-23 07:58:25-0800 [info] Klonewin - Start [Build: Nov  1 2016 07:49:51]
2017-03-23 07:58:25-0800 [info] ...Capture: True
2017-03-23 07:58:25-0800 [info] ...Deploy: False
2017-03-23 07:58:25-0800 [info] ...ImageName: 36
2017-03-23 07:58:25-0800 [info] ...ImageType: k-image
2017-03-23 07:58:25-0800 [info] ...LocalDir: S:\
2017-03-23 07:58:25-0800 [info] ...TempDir:
2017-03-23 07:58:25-0800 [info] Hashstore Client (Version 4.0.695)-start
2017-03-23 07:58:25-0800 [info] Ready to copy 186 items (24.7 MB).
2017-03-23 07:58:27-0800 [info] Items processed: 186 (24.7 MB)
2017-03-23 07:58:27-0800 [info] Items transferred: 5 (212.0 KB)
2017-03-23 07:58:27-0800 [info] Hashstore Client-end [1]
2017-03-23 07:58:27-0800 [info] Copy completed successfully.
2017-03-23 07:58:27-0800 [info] Klonewin - Done, exit code: 0


1 Comment   [ + ] Show comment

Comments

  • Hi TheAustinDave,

    Do you really think that different ports or protocols are being used by the KDE to send k-Image and wim files to the server?

    This setup worked just fine before the big 4.0 update. I guess I will wait for Quest's engineers to have a look and see what is wrong. I will report back the findings once it is fixed.

All Answers

-1
When capturing the image, does the data go between two different subnets - If yes can you create an RSA in the same subnet, sync the data to the RSA and then try to deploy the WIM image again?

Another way to see what might be happening is do a tracert between the two subnets and see where the data is flowing, most likely its getting a time-out from a router or other appliance perhaps. The above test if successful would indicate this is the cause.


Answered 03/29/2017 by: TheAustinDave
Brown Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ