Skip to main content

Source is unavailable

Thread needs solution
Beginner
Posts: 1
Comments: 0

Hello,

When deploying an image that is located on a Netware file system by using UNC paths as pointers, the Error Code 7 (0x7E007) appears in the log and the deployment is cancelled stating that the Source (path to TIB file) is unavailable.

When deploying the exact same image from a Local Windows 7 workstation Share as the source, the deployment is successful.

Is there an incompatibility with Novell UNC paths? This worked in Snap Deploy Version 3.

thank you

Attachment Size
error.txt 767 bytes
0 Users found this helpful
Forum Star
Posts: 88
Comments: 4769

Hello Computer Services,

Thank you for your post.

The error message indicates an issue with the network, it is possible it is related to Novell UNC paths, however, there is little information about it at the moment.

Our Support representative is currently working on your case and should you need any help with it feel free to contact me directly.

Please let me know if you have additional questions.

Thank you.

Beginner
Posts: 1
Comments: 3

This issue appears similar to mine. Deployment fails with the same error every time.

Failed to process the session.
Additional info:
--------------------
Error code: 1
Module: 52
LineInfo: 7DD5E03A29333D6B
Fields: $module : "E:\Program Files\Acronis\OSDeployServer\ds_invoker.exe"
Message: Failed to process the session.
--------------------
Error code: 7
Module: 126
LineInfo: 70E26A1BA387E862
Fields: $module : "E:\Program Files\Acronis\OSDeployServer\ds_invoker.exe"
Message: Source 'W:\M91base_Win732__Office2010_install_Bolton.tib' is unavailable.

Beginner
Posts: 1
Comments: 3

I have now moved the .tib file to a local drive and this is now deploying.

For some SnapDeploy reason doesn't like a mapped drive. I'm not sure if this is down to Network teaming or another reason.

Beginner
Posts: 2
Comments: 3

I am having the same issue with builds 1749 and 1755.  The only difference is that my image resides on a local secondary drive (D:\).  This is NOT a mapped drive.  

Forum Moderator
Posts: 113
Comments: 4338

Eric Grau wrote:

I am having the same issue with builds 1749 and 1755.  The only difference is that my image resides on a local secondary drive (D:\).  This is NOT a mapped drive.  

Hello Eric,
I'd recommend you updating to the latest released build 1808, re-creating the image with this build and re-attempting deployment. If the issues persists, please start a new discussion in Acronis Snap Deploy 5 forum and post the whole error message along with the details on your deployment task (are you using the PXE or installed an Agent directly onto the target machine, have you tested the standalone deployment?)
Thank you,