Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Azcopy is failing. See the error. #6356

Closed
Skarakkattil opened this issue Mar 27, 2018 — with docs.microsoft.com · 17 comments
Closed

Azcopy is failing. See the error. #6356

Skarakkattil opened this issue Mar 27, 2018 — with docs.microsoft.com · 17 comments
Assignees
@AdamS-MSFT
Labels
cxp forum in-progress product-question storage/svc triaged

Comments

@Skarakkattil docs.microsoft.com
Copy link

User is an administrator on the machine. But Azcopy with my personal id which is an admin on the machine works. I am trying it from cmd prompt

Unhandled Exception: System.Runtime.Serialization.SerializationException: End of Stream encountered before parsing was completed.
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream)
at Microsoft.WindowsAzure.Storage.DataMovement.StreamJournal.Initialize()
at Microsoft.WindowsAzure.Storage.DataMovement.TransferCheckpoint..ctor(Stream journalStream)
at Microsoft.WindowsAzure.Storage.DataMovement.TransferContext..ctor(Stream journalStream)
at Microsoft.WindowsAzure.Storage.AzCopy.DirectoryTransferLauncher..ctor(ILocation source, ILocation dest, CommandLineParameters parameters)
at Microsoft.WindowsAzure.Storage.AzCopy.TransferLauncherBuilder.BuildTransferLauncher()
at Microsoft.WindowsAzure.Storage.AzCopy.BlobFileTransfer.DoTransfer()
at Microsoft.WindowsAzure.Storage.AzCopy.AzCopy.ExecuteTransfer()
at Microsoft.WindowsAzure.Storage.AzCopy.AzCopy.Execute(String[] args)
at Microsoft.WindowsAzure.Storage.AzCopy.AzCopy.Main(String[] args)

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@MohitGargMSFT
Copy link
Member

@Skarakkattil Thanks for your feedback! We will investigate and update as appropriate.

@MohitGargMSFT MohitGargMSFT removed their assignment Mar 28, 2018
@Skarakkattil docs.microsoft.com
Copy link
Author

Let me now if you need any additional detail. I ran Procmon.exe and could not see any access issues. User running is an administrator on the machine.

@AdamS-MSFT
Copy link
Member

@Skarakkattil Could you post your question in https://social.msdn.microsoft.com/forums/azure/en-US/home?forum=windowsazuredata
This question requires in depth troubleshooting and additional questions. It will be more appropriate for the forums channel since it's not related to the documentation.

@gbstan92
Copy link

@Adam-Smith-MSFT has any resolution been found? I believe we are experiencing something similar.

@seguler
Copy link
Contributor

seguler commented Apr 11, 2018

@EmmaZhu can you take a look at this ?

@gbstan92 are you trying to copy a whole drive ? AzCopy /Source:C:\ /Dest:...

@gbstan92
Copy link

Hi @seguler ! It is just a folder.This is the script used:

Set-Location "C:\Program Files (x86)\Microsoft SDKs\Azure\AzCopy"
.\AzCopy.exe /Source:C:*Inetpub*\logs /Dest:https://**//bc/ /DestKey:== /Y /XO /S

@seguler
Copy link
Contributor

seguler commented Apr 12, 2018

@EmmaZhu can you help ?

@EmmaZhu
Copy link

EmmaZhu commented Apr 13, 2018 •
edited
Loading

@Skarakkattil @gbstan92
Could you share version of AzCopy you are using?
Does this issue happen during a resume or a totally new transfer? If it's a resume, did you cancel the previous AzCopy process or kill it?

@Skarakkattil
Copy link
Author

Skarakkattil commented Apr 13, 2018 via email

@EmmaZhu
Copy link

EmmaZhu commented Apr 13, 2018

@Skarakkattil We do have issue on reading file/directory without access that we're working on a fix. But the error you shared, seems it's caused by trying to read a corrupted journal file.

AzCopy supports to resume last failed transfer, it keeps a journal file on the local disk. If last AzCopy process is killed or crashed, it may leave some corrupted journal file. It can report the error you meet when it tries to resume from the corrupted journal file.

Thanks
Emma

@Skarakkattil
Copy link
Author

Skarakkattil commented Apr 13, 2018 via email

@gbstan92
Copy link

Hi @Skarakkattil . The version is 7.0.25.

After clearing the journal, we are now getting a different error:
[2018/04/13 15:38:40][ERROR] Error parsing destination location "https://mylocation/myfolder": The underlying connection was closed: An unexpected error occurred on a receive. For more details, please type "Az
Copy /?:Dest" or use verbose option /V.

We use the same container for other log backups so the storage is definitely working fine.

@EmmaZhu
Copy link

EmmaZhu commented Apr 20, 2018

@gbstan92 The error message shows an error from network to me. Can you share the account name to me to take a look if it's OK? My email address is emmazhu@microsoft.com

@gbstan92
Copy link

Hi @EmmaZhu

Very sorry for the late reply. I've done some additional troubleshooting and found out that whenever I run the script the following System Error (Event 36871) gets generated:

"A fatal error occured while creating a TLS client credential. The internal error state is 10013"

This is a WS2016 box that has TLS 1.0 and 1.1 disabled. I understand that AzCopy might be using TLS 1.1. Any chance we can force it to use TLS 1.2?

@placidseven
Copy link

Can someone answer @gbstan92 query?

"I understand that AzCopy might be using TLS 1.1. Any chance we can force it to use TLS 1.2?"

@EmmaZhu
Copy link

EmmaZhu commented Dec 13, 2019

AzCopy 7.0 is built against .NET Framework 4.5. You can set the TLS version it uses by a registry, Please refer to
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#schusestrongcrypto for details.

@placidseven
Copy link

@EmmaZhu
Thanks for the reply. I assume the same for version 8.1 and 10?

I was actually coming here to post that I had found the below thread. I appreciate the information.

microsoft/azure-pipelines-tasks#10337
@TheJayMann AzCopy shipped with the Azure File Copy task should work fine with TLS 1.2. Refer this.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AdamS-MSFT AdamS-MSFT

Labels
cxp forum in-progress product-question storage/svc triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@EmmaZhu @BryanTrach-MSFT @seguler @MohitGargMSFT @AdamS-MSFT @Skarakkattil @gbstan92 @placidseven