Unable to upload files to CIPRES endpoint - Globus Transfer

[Mario Sandoval]

I'm trying to upload a .trees file from my Beast  output directly from my computer to CIPRES endpoint using Globus Transfer, but there is an error: System Error: unable to transfer! Also got this message: " Either this endpoint is not accessible or does not have any files/directories that belong to you ...  ". I have installed Globus transfer software but I don't know what's happening. My file is ~5 GB  size.

Does anybody knows how to solve this problem?

Thank you in advance,

Best 

Mario

[Mark Miller]

When I had this problem, it was because the files I wanted to move were not in the directory connected to Globus.

The local endpoint, Globus Personal, is linked to a single directory, and your file must be in that directory, or a subdirectory.

Can you confirm that the file is in the location that Globus Personal recognizes?

Mark

[Mario Sandoval]

Hi Mark,

Yes, I have moved my file to the default directory (Documents). I have also tried assigning a new folder/path on my desktop to make sure it is not a Windows permissions issue. 

I can actually see my files in the CIPRES portal (Globus transfer), but when I click the TRANSFER button I get the same error message. I have noticed that when I click on "My Endpoints" my endpoint has another buttom "Activate Endpoint". Do you think that could be the reason why I can't transfer my files?  

Thank you for your help.

Mario

[Mark Miller]

Hi Mario

I apologize for the slow response, for some reason the google app only notified me of the pending message today.

I have been waiting for the response.

Very sorry about that.

I would definitely activate the endpoint and see what happens. Please let me know how it responds.

Mark

[Mark Miller]

Dear Mario,

We investigated this issue on our side. We found that activating the endpoint is key. Also, we found that if a user has more than one endpoint discovered, at present, CIPRES will only try to activate the first one. If you have more than one, it could cause an issue. We found that the user had to delete the other two endpoints to activate the correct one. We will be working to fix that issue. Let me know if this impacts you.

Sincerely,
Mark Miller