ELM 19.5.0.27 Failing on copying image to filestore.

[Calvin Chan]

Trying to publish a new image today and on the last step, we ran into this error:  "The file copy was aborted after 5 transient errors."

Attached is a log from the ELM console. The credentials tests, connection tests all pass. The service account on the ELM has proper access to filestore... 

Doesn't seem like anyone else have had this problem.

 

Our environment is ESXi vSphere 6.5 

7.15 LTSR CU3
 

[Raymond Colon]

I was telling a colleague it could be an issue with BITS not running, but this is good to know. I think the OP is referring to the below. I post it for others.

 

http://steinotech.blogspot.com/

[David Ray]

I have noticed that I get this error (The file copy was aborted after 5 transient errors) now in 19.8 if the PVS server is out of space for the vdisks.  Took me a while to figure it out because I am sure in the past I would get a more salient message saying something about PVS and space.  I even think I have seen it since I have been on 19.8.  But I am certain I have gotten the abort after 5 errors message because of space.  Just got several this morning 'til I noticed the space problem.  Freed space and then the jobs worked.

 

/David

[Rob Zylowski]

Is this something that worked before or is it your first try?  

 

Do you have a template defined in your connector config?  Maybe try without the template as a test if you do?

 

Do you see any errors in your vcenter?  Or the host you chose for publishing?

 

if you open a ticket support can look at the detailed logs. 

[Calvin Chan]

10 minutes ago, Rob Zylowski1709158051 said:

Is this something that worked before or is it your first try?  

   This is something that worked previously, I added a new version to the platform layer for troubleshooting purposes on another support ticket.

 

10 minutes ago, Rob Zylowski said:

Do you have a template defined in your connector config?  Maybe try without the template as a test if you do?

  hmm, this connector for the output is on Citrix Provisioning Services, no template option on that page

 

Do you see any errors in your vcenter?  Or the host you chose for publishing?

  no error in vcenter, was able to create target device/packaging machine just fine, finalizing as well.

 

if you open a ticket support can look at the detailed logs. 

 

Thank you Rob for your prompt reply in this matter! that was quick.

[Rob Zylowski]

Have you upgraded your elm since it worked last?  If so did you update the agent in your pvs server?  

 

Does it only have the error with the new platform layer?  

 

If it does i would create a new platform layer with all the changes you are trying to make.  

[Calvin Chan]

I tested by trying to publish another image via a different template, and that didn't work either, which rules out the work I did on the platform layer revision. A wild google search revealed one other person has experienced this issue and it was caused by the certificate.  We re-install a fresh certificate on the ELM and problem has gone away. Thank you Rob for the assistance!

[Rob Zylowski]

Good to know i'll remember that one.

[Calvin Chan]

10 minutes ago, Raymond Colon said:

I was telling a colleague it could be an issue with BITS not running, but this is good to know. I think the OP is referring to the below. I post it for others.

 

http://steinotech.blogspot.com/

 

Thanks Raymond, you are correct - that is the blog page I found, I wasn't sure about the policy on posting blog pages here.

[Raymond Colon]

Your welcome and thank you for posting your solution, many people do not and I, we end up wondering, what happened. ;-)

 I do not think there are any restrictions.

[SCOTT LORENZEN]

On 9/19/2019 at 10:34 AM, David Ray said:

I have noticed that I get this error (The file copy was aborted after 5 transient errors) now in 19.8 if the PVS server is out of space for the vdisks.  Took me a while to figure it out because I am sure in the past I would get a more salient message saying something about PVS and space.  I even think I have seen it since I have been on 19.8.  But I am certain I have gotten the abort after 5 errors message because of space.  Just got several this morning 'til I noticed the space problem.  Freed space and then the jobs worked.

 

/David

 

David, thank you for this.  So in our environment, and I have seen this several times, in PVS we used the GUI to delete VHD's yet the system does not remove them.  We had run out of space as the GUI showed only two (2) VHD's yet in explorer we saw five (5) additional that were still on the file system.  Once removed everything worked as normal.

[Jochen Bauer]

Despite this being an old thread, here are my 2 cents:

Had the same error "The file copy was aborted after 5 transient errors."

 

The reason was in my case missing disk space as well.

 

Important tip: Show hidden files in explorer, because at first I was wondering why my drive was nearly full, but when summarizing the vhd files I never came close to that number.

After showing hidden files, I saw .tmp files from previously unsuccessful/aborted transfers from ELM, dated a few months back.

Removed them -> new image files could be transferred again!