Internal error: write outside of allowed area

What version are you using?  Did you grab the 1749 release?  It's supposed to support all current versions of Windows and secure boot.  I don't use TPM/secure boot so can't test.  In the past, I would disable secure boot, image/deploy and re-enable if need be.

Using version 1749.  

No difference with secure boot off.  

Still fails at end of task with Internal error: write outside of allowed area.

Also have shut off TPM 2.0 and reimaged.  Same error.  

Experiencing this issue with HP 820G4 128GB NVMe SSD.

I tried changing deployment settings (universal deploy, unicast and multicast, etc.) with no success. I am able to successfully pull the images to the laptops when booting from the standalone media. I even set up a new test server to see if I was able to successfully deploy but still receive the same error when booting to the PXE server.

Same issue here. Just posted about it as well. Dell Optiplex 7050 desktop with onboard Samsung PM961 NVMe 256 GB.

There is a problem with the 1749 release.

Unfortunately you'll have to:

Uninstall build#1749 and install build#1755. In order to completely reinstall product you should:

- Navigate to program files and features- remove all components that belong to Acronis Snap Deploy

- Navigate to C:\Program Data\ and remove Acronis folder completely

- Navigate to C:\Program Files(x86)\Common Files and remove Acronis folder

- Navigate to C:\Program Files\Common\ and remove Acronis folder.

I also had to make new bootable media and a new image of the laptop.  But the problem has been solved. 

Where did you get build 1755? Is that a beta build? Did a Acronis Rep send you a link for the download?

Got it from support.  It does not indicate that it's Beta.

My issue was also resolved with build 1755 which I acquired from contacting support. 

Same issue here.  Can someone send me a link to build 1755?  

Thanks all

I am also wanting the latest build.  I have an open support ticket for the same issue and have requested the link with no response yet.

I wish Support would just post the new builds here on the forum without the need for everyone to start requesting.

Hello Everyone,

I've uploaded a copy of 1755 to our FTP server. To access FTP:

•    Click on the following link [] and copy the link to the FTP account you’ll find on the opened page. 
•    Open Windows Explorer (e.g. click My Computer). 
•    Paste the copied link into the address bar of Windows Explorer. 

To learn more, check: https://www.youtube.com/watch?v=tG499XLTEos 

Alternatively, you can upload the files via FTP clients. Please use the following link and credentials:

To learn more please visit the following KB article http://kb.acronis.com/content/5991

Thank you, 

After updating I have a new problem to deploy my image file.

I Tried to create a new image because I have this error but it was the same result.

event code="5" id="39" level="4" line_tag="0x70E26A1BA387E775" message="Source '\\**\**\***.tib' is unavailable." module="126" time="1507541879"

Dominique,

I would assume a new image created with 1755 would have corrected that issue.  Unfortunately, I haven't had time to test out 1755.

Did you make new bootable media using 1755?

Ekaterina,

Do you recommend doing a clean install of the new build or is "upgrading" on top of 1749 sufficient?

Per Chris L's post on a clean install:

Uninstall build#1749 and install build#1755. In order to completely reinstall product you should: - Navigate to program files and features- remove all components that belong to Acronis Snap Deploy - Navigate to C:\Program Data\ and remove Acronis folder completely - Navigate to C:\Program Files(x86)\Common Files and remove Acronis folder - Navigate to C:\Program Files\Common\ and remove Acronis folder.

 

Thanks all.

I do a clean install and create a new image (v1755).

Deployment succeed but how could I do with my older image file please?

I can confirm that re-capturing the image using build 1755 and re-deploying worked.  Dominique, do you have a machine with the image available that you could re-capture using Master Image creator?  

I created a new boot PE USB.  The Acronis boot doesn't work properly with the share location and the Lenovo T470.

Chris, did you integrate the network/storage drivers into the PE image?

When moving to 1755 to get around the "Message: Internal error: write outside of allowed area" we are now getting the following errors when deploying our images built in 1749.

Source '\\fakepath\fakeimagefile10192017.tib' is unavailable.
Additional info:
--------------------
Error code: 31
Module: 55
LineInfo: 70E26A1BA387E775
Fields: $module : "osd_server_vs_1755"
Message: Source '\\fakepath\fakeimage10192017.tib' is unavailable.

Hello Everyone,

Some information on the compatibility issues in builds 1755 and 1749. 

First of all, yes, I'm afraid there could be indeed compatibility issues when attempting to deploy 1749 archives with the components of 1755. As far I as understood, the issue is directly related to the fix for "Deployment of image of UEFI machine to the same machine fails with error "Internal error: write outside of allowed area" , where the fix was to remove the support of archives created with Acronis Backup 11.7. Therefore, components of 1755, which do not support 11.7 archives, might not work with the images created by the build where 11.7 archives compatibility is enabled. 

In this situation I could only suggest either re-creating the master images with 1755 or raising a support ticket, so that our engineers can address your particular scenario.

Thank you!

Is there any update on this issue.

I would like to get my snap deploy finally working.

Hi,

If you are using the build 1755 and experience the issue with failing deployment of images created with 1749 over PXE (error message  "Source is unavailable"), then the workaround would be either re-creating the master images with1755 or using the standalone deployment. If both variants are not suitable, please raise a support ticket, so that our engineers can collect necessary information from your environment and check with the development team whether it's possible to fix the issue with a custom build. 

Thank you, 

I hope there is another solution in the works.  This is the kind of issue that will weigh heavily on our upcoming decision to stay with Acronis vs moving to a competitors product.

Agree.

And, asking us to put in additional tickets for these known issues is counterproductive.  I'm not saying I will not, but I keep hoping a new build will be posted soon.

Months later and this is still not resolved and 1755 is still not posted as the latest version.  I went through this to get 1749.  I am VERY seriously considering moving elsewhere as I need to buy more licensing soon and am not inclined to support this behavior with my company's cash.  We have tons of work to do without having to screw around waiting on support to make the latest release available by request only and then having to build new images.

It feels like the entire software industry has decided that it's ok to use their customers as beta testers and that they have all kinds of time to jump through hoops to get the product, that's supposed to save them time and admin effort, to work.

</RANT>

Same boat here.

I have just recently received a quote for a renew, but am too scared to proceed as I don't know what the future holds.  I know that we are not going backwards for deployments; all of our future systems will be based on NVNe tech.

As a non-profit, we can not take that risk.

Last week I had a meeting with my IT director and we will not be renewing our support this year, and searching for another solution.

If I am going to need to recreate all of my images, I might as well do it in another piece of software.

Closing the thread. If you encounter the same issue, please refer to https://forum.acronis.com/comment/435546#comment-435546