I'm receiving an error when just trying to upload a file into a container in Azure, using the portal. It seems the UI for uploading files changed a bit, so I'm a little inclined to believe the problem may be due to an update, but I just wanted to be sure and see if there's anything I can check or do on my end. Tried a couple different files that I've uploaded, before today, successfully- they errored out as well.
Would anyone know why I'd suddenly be receiving this error?
Failed to upload 1 out of 1 blob(s):
blob_test.xml: Failed to fetch
I noticed this also. It seems like the upload button is enabled too soon. If I select a file or files then press upload right away it often fails. If I wait 10-20 seconds after the upload button is enabled it seems not to fail.
Waiting even for five minutes didn't help me but refreshing the page did
A combination of the two worked for me. refreshed the page + wait for a little while before clicking on upload
Related
I've been struggling to get my update to go through. I incremented my version in the manifest and updated a lot of code, I upload the new package successfully and submit, but I never see the manifest version update in the chrome web store and there are no errors. The draft of the package always shows the same version as well (0.0.0.1 as I have never had a successful update). When I submit the status goes to pending and then public.
My only guess is that something is wrong with my account. This update includes moving from manifest v2 to v3 as well although I feel like I'd get an error if something was wrong there.
I've tried to resubmit this multiple times over the past 3 weeks and always the same lack of update.
There were a few .pem files in a random node module. I hadn't realize I should just remove node_modules from the zipped up package, but for some reason it only errored out and warned me about including .pem files sometimes. Most of the time updating the package seemed to work fine and didn't error. Very strange. Regardless it is fine now!
I've checked for possible duplicate and found one, but having implemented his solution and not finding any luck, thought I'd ask the experts.
Crashlytics has been setup on my app properly. But it isn't reporting the errors in my dashboard. I've attached a picture from my terminal. The crash is being handled and an attempt is made to send it to the dashboard.
Perhaps there is a delay from the time I setup crashlytics for the first time? It has been up and running for at least 30 minutes. And I've also downloaded the google-services-json file again after setting it up.
Any suggestions?
Everything is fine. There was just a delay in the reporting. The crashes have started showing up now, but they aren't as instant as I thought they would be. Much more detailed than Google Developers crash report though.
I have a Azure App Service app that I'm trying to get deployed.
Today I ran into an issue where .NET informed me (via the yellow screen of death when I browse to the URL of my app) that I had a missing DLL (for the purposes of this question I don't think it really matters).
I used FileZilla to publish my changes in an attempt to do a manual deployment first and then work my way to automate it.
After so many attempts to fix it I later realized that the error message never changed. I did something more severe and renamed my bin folder into something completely different and the exact same error message would appear.
I've stopped the service, restarted it, and as mentioned, renamed folders, etc. and still the exact same error message persisted.
I also decided to open up the Azure Portal Console for my App Service app to browse a bit and to my amazement, nothing seemed to have reflected at all. The FTP shows one thing and the Console shows another.
Would anyone have any idea as to why this is happening?
I eventually got it to work and I will share what I tried.
I deleted the web app and created it again (I found this to be important the first time around). This was quite time consuming and did help but it wasn't long before the same problem happened again.
Then I finally found a solution that seems to give me consistent results:
I kept on editing the Web.config which seems to force a recompile and clear some sort of cache. So each time the web app stopped updating, I would make a slight change in the Web.config, upload it via FTP and the app finally updates.
If anyone has any more details on this, it would be greatly appreciated.
I have just installed Wordpress in a new Azure Web Application and everything is running fine at the moment.
However, I am getting notifications that I am exceeding the storage file system quota (1GB).
I went to check the value on the Azure Portal and the strange thing is that the storage usage is varying from 12% to 100% every single minute! Somehow the measurement must be crazy, since I am not changing a bit in my website nor have huge files there.
12% must be the realistic value for Wordpress. I have tried to reset the website and check log files to see if there is anything wrong, but did not find anything.
How can I fix that?
Igor.
You might want to try de-activating the most recent plugins you installed 1 by 1 to see if this corrects the issue. There could be a bug in one of them that has some type of loop that generates a large log file.
At the end of the same day the problem disappeared. It seems everything is stable now, but if happened once, it might happen again. I will keep you posted in case I experience this problem again.
Thank you.
I've been using the export database feature on Azure for the past year without problems.
However during the past week the feature seems to error more than it actually works. On some occasions the export takes an hour or more (where it used to be a minute or less) and on other occasions it errors without completing the job. On the Info Screen in Azure it says "Status - Pending" over and over again.
Does anybody know what I should do? Should I create another container? Could there be something else wrong?
Thanks for reading
It seems this happens from time to time due to Azure problems. For anybody who encounters this, the perfectly adequate workaround is to use Sql Server Management Studio, select the database and Export Data-Tier Application.
Here is another post on the same issue:
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/bb66505e-7008-4555-b8cd-eec9ae25066f/unable-to-export-db-via-portal?forum=ssdsgetstarted