I'm trying to copy a zip file using command prompt from source to destination.
Size of the zip file is 1.14 GB.
COPY \Server1\DataFeeds\Dec\feed1.zip C:\Folder1
This works fine. I can see the zip file copied over to C:\Folder1 & it shows size correct, i.e. 1.14GB
COPY \Server1\DataFeeds\Dec\feed1.zip \upload.website.com\DavWWWRoot\Documents\Dec
This does not work as expected. I can see the zip file copied over to SharePoint unc location (\upload.website.com\DavWWWRoot\Documents\Dec), but it's just EMPTY FILE - SIZE 0 BYTES
What could be the reason that the copy not working for SharePoint location as destination?
How can I fix this? Thanks.
More Info: Here is the error logged in windows system log: Any help will be highly appreciated.
Application popup: cmd.exe - Delayed Write Failed :
Windows was unable to save all the data for the file. The data has been lost.
This error may be caused by a failure of your computer hardware or network connection.
Please try to save this file elsewhere.
Related
I have access to avd using webclient. When I open excel file and try to save it into my local machine I get an error and an empty tmp file is downloaded instead of the excel file.
When I copy an excel file to the download folder, it get it correctly. However not all users have access to windows desktop. So they can not copy to the download folder.
I used a Microsoft Remote desktop to do the same work and it works correctly when saving excel file.
Is it a limitation on when using web client or I missed a config on my browser?
I'm able to compile and use Active Sync 4.5 to copy and then run application files in a Windows CE based device. Whenever I copy a file to the device Active Sync will say it will convert the file.
This process of manually uploading the files using Active Sync is slow so I'm now sending the files directly using my application and a TCP sort of file receiver. File is being transferred fine (crc checked).
The problem is that the file does not run complaining with a generic message that the file cannot be opened. My first and only guess is related to this "conversion" process that Active Sync is doing.
I could not find any documentation related to what is is this process and how does it work. Is there any place I can find more information about this conversion? Or is there any tool that can pre-convert so I can transfer it?
The first idea about pre-convert was to copy the file to the device and the copy it back using Active Sync but when copying files out of Windows CE it will convert back to PC format.
So the issue is as follows.
I have created a VBA task that runs a query that returns some insignificant amount of data in our databases. It then does some simple calculations in the excel file, and finally it creates a new folder and it the saves the file to our department shared drive in Google Drive (we have a windows explorer path to the directory named G drive).
It works ok on my end but now I have sent the whole .xlsm file to my collegue and once she run the vba code, it throws an error saying Path/File Access Error. We have tried chaning the directory where it creates a folder and saves the file on her local C drive, and it works just fine.
Any ideas how to remedy this issue?
Instead of uploading to a windows explorer path, you should upload to an absolute path of google drive, as that is the same no matter who tries to access it. There is a guide here that accomplishes exactly that:
https://medium.com/coalmont/google-drive-api-using-excel-vba-80e3d7e41488
If for some reason that guide is not available, just google something like "vba excel upload google drive".
I am hoping someone has had this issue before and can help me resolve. I was working on a company project. I had just finished up and needed to publish my project to the server. When trying to publish, I got the error "This file is currently not available for use on this computer."
So then I tried to open one of the .cs files of the solution, and the error occurred again from trying to open the file. So I tried to grab the latest version from TFS thinking it would give me whichever file is missing, but when I click "Get Latest Version" on the project, the error message pops up there too.
I thought surely I will be able to delete the project locally and then remap it, but I can't even delete the project off my computer, as the error message pops up halfway through deletion. When it occurs there, however, I do get "Error 0x800710FE: This file is currently not available for use on this computer."
Also have tried deleting offline cached files through Control Panel > Sync Center > Manage Offline Files > Disk Usage > Delete temp files
I got this error for a small, test solution that was not using TFS. The default file location is the documents folder, which in my environment is synced using the Sync Center. I moved all of the solution files to a new local folder that was not included in Sync operations and the error went away.
Conclusion: storing VS files in a folder managed by Sync Center is likely a bad idea.
I got this error when trying to save an excel file served from a webpage.
The solution for me was to save it under a different filename. Possibly because I previously had a file with the same name open in excel.
I have tried copying the wwwroot directory from Windows Server 2012 R2 data center on Azure Cloud to Windows 8.1 over Remote Desktop Connection and FileZilla, and the copied folder size on Windows 8.1 is much less than the source folder on the server after copy operation completion.
The Source folder size is 683MB while the copied folder is 570MB. I have only found one close explanation for this on support.microsoft.com (support.microsoft.com/en-us/kb/2891362) which explains that this might be due to long paths that exceed the maximum allowable path length.
I would appreciate if anybody have experience on such matter to enlight me.
Thank you
A typical cause of these symptoms is that you have used an ascii/text transfer mode, so all CRLF line-endings got converted to CR only (one byte less for each line).
But you have provided way too little information, so we can only guess.
Download the directory tree back (to another folder) and compare against your original source folder.
Check if the problem is specific to a certain folder/file only or if all (or majority of) files got reduced proportionally.