I just started playing around with Azure platform. I tried to upload a simple application to Azure cloud to see how it works. For that I m using Eclipse Indigo and the eclipse plug-in for Azure.
However I get the following error while publishing to the cloud:
" Filed uploading deployment package (.cspkg)"
I searched aroudn and I see that other people have the same problem.
The size of the application is 382MB !!!!! I guess that s why I Get this error.
However why is the size that large?I only have a hello world app with one .jsp file.
When running to the emulator I point to the server installation that I want to use. Is afterwards the whole installation being uploaded to the cloud while publishing? Even in this case , I use Tomcat which is about 50 MB? Where are the rest 230Mb coming from ?
How can i reduce the size of my app?
I d also like to know whether the Eclipse plug-in for Azure is supported by Eclipse Indigo. I read on the Azure site that Eclipse Helios is required.
Related
I have a small web app developed with Asp.Net Core 1.1 deployed on Azure and it works well. I just migrated the project to use Asp.Net Core 2.0 and tried to deploy it on Azure. The deployment went fine but when I open the site, I get a 502.5 error. When I check my Azure log stream, I get the following error:
This error occurs when a CGI application does not return a valid set
of HTTP headers, or when a proxy or gateway was unable to send the
request to a parent gateway. You may need to get a network trace or
contact the proxy server administrator, if it is not a CGI problem.
Useless to say that it works well on my development machine with the same code. Note that I'm also using Entity Framework Core 2.0 although I deactivated the database creation on Azure (to check if it was not the cause).
For information, the way I migrated from 1.1 to 2.0 is by changing the target framework settings to "netcoreapp2.0" and by using the NuGet package "Microsoft.AspNetCore.All". Just to be sure, I also deleted my publish profile and recreate one.
Is it possible that Asp.Net Core 2.0 is not yet available on Azure ? I'm fairly new to Asp.Net Core, so I don't know when new releases are made available on Azure.
EDIT
When I try to run my app with dot net CLI via the debug console as proposed by natemcmaster, I got the following issue:
Unhandled Exception: System.IO.FileLoadException: Could not load file
or assembly 'Microsoft.AspNetCore.Hosting.Abstractions,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
The located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
I downloaded the DLL on my desktop and check the version with Dot Net Peak and indeed, the DLL is 1.1.2, although I created the project with Visual Studio and directly publish it, so is it an issue with Visual Studio ? Or Nuget ?
the issue was actually coming from the fact that, at first, my web app was using .net core 1.1, which deploys all the DLL in the "wwwroot" folder of the web application. However, with asp.net core 2.0, it does not do that anymore as the DLL are picked up from a global store. However, as Visual Studio does not clean the destination folder before a publish, I ended up with a situation where the 1.1 DLL were in my wwwroot, so the web site was picking up these ones instead of the 2.0 ones in the store folder.
This is explained in more details here: https://github.com/Azure/app-service-announcements-discussions/issues/2#issuecomment-313816550
Others have explained the reason why this is happening. I'd like to provide another – arguably easier – solution to the problem.
Just change the settings so that you remove files that are already on Azure – see below:
Check for log files either in the portal or by remotely accessing D:\home\LogFiles.
Sometimes, the logs won't indicate what is going wrong. Another good way to investigate further is to try launching your ASP.NET Core app from the Debug Console. If you are missing a shared framework version or there is another startup error, this will be more visible from the Debug Console.
Go to
https://(your web site name here).scm.azurewebsites.net/DebugConsole/
Your site will be in D:\home\site\wwwroot. You can launch it by executing:
cd D:\home\site\wwwroot
dotnet MyWebApp.dll
If you app still fails to launch, make sure that D:\home\site\wwwroot\web.config is available and configured to use ASP.NET Core Module. https://learn.microsoft.com/en-us/aspnet/core/hosting/aspnet-core-module
In my case, It was caused by having a space in the Project Name.
I can readily add a space, publish => 502.5.
Remove space, publish => good to go.
Hard to believe but I am duplicating it readily with above.
Also using "Remove Additional Files at Destination" per #Sam's Answer
See https://github.com/Azure/app-service-announcements/issues/14
"The rollout is expected to complete by Friday June 30th."
In my case the issue occurred because AppService at that time supported 2.0.0-preview2-006497 but I had 2.0.0-preview3-006890 installed which was used on build.
So I added global.json to use preview 2 SDK and it worked then
I don't know if this could help someone one day but in my case, I was using :
-Microsoft.AspNetCore.All 2.0.5
Downdrage to Microsoft.AspNetCore.All 2.0.3 resolve my problem
This happens when your version of ASP.NET Core cannot be matched on the server.
The simplest solution is to change your settings to deploy the app as self-contained, so it doesn't matter if Azure can match the framework version. Also, delete the files already on Azure, so you don't have issues when upgrading, as explained by #Sam.
Here's my setup:
An MVC web project that is hosted in azure
VS2012 and VS2013
Windows Azure SDK 2.2
IIS Express 8 - 8.0.1557
The MVC project is using castle windsor, and there are performance counters being created during application start up.
When I run the project locally (via emulator) I am find that during the performance counters creation an exception is being thrown however the performance counters are created and copied across to azure table storage.
Exception:
The directory specified for caching compressed content C:\Users\danielc\AppData\Local\dftmp\Resources\c2fd1c9b-d6c5-49af-942d-715c8f1ccc1c\temp\temp\RoleTemp\iisexpress\IIS Temporary Compressed Files\767ba5ae-0038-4c32-a70c-3d2f671e37ed is invalid. Static compression is being disabled.
When I try and find this location, it does not exist, which implies to be that it maybe a permission issue, but I dont know how to change the permissions for the emulator.
To add to my headache, I am in a team of 6, all of which are not experiencing this issue. Furthermore when it is deployed to azure it works fine as well.
My question therefore is, has anyone experienced this issue before and know a solution?
Steps taken so far:
Uninstall and install azure sdk 2.2
Install azure sdk 2.3
Install azure sdk 2.4
Uninstall and install IIS Express 8
Uninstall IIS Express 8 and install IIS Express 7.5 (which turned out did work as not supported but just clutching at straws really)
Thanks
So I believe I have got to the bottom of it. It would appear the instance count in the ServiceConfiguration.cscfg is 4, but when set to 1 it runs fine.
It is very odd that my colleagues who work with this other configuration are not experiencing the issue.
I am new to Azure. I am trying to start my application in VS2012 (debugging). I am getting the error below:
There was an error attaching the debugger to the IIS worker process for URL 'http://learning.cloudapp.net:82' for role instance 'deployment18(13)......'. Unable to start debugging on the web server. The underlying connection was closed: An unexpected error occurred on a receive.
My application is working fine when I hosted it in IIS. It worked fine when I set the website project as the start up project. But when I set the azure project as start up project and start debugging I am getting the error. I have tried almost everything I could find on the internet. Can anyone please help?
Thanks,
Mahesh
One time I got this by loading an older Azure solution on a newer machine, another time after I upgraded to Azure SDK 2.0.
I was using IIS Express instead of regular IIS.
Each time the only thing that fixed was:
Install Azure SDK 2 via Web Platform Installer
Install Azure Powershell tools via Web Platform Installer
Create a new Azure Project -- do not use your old azure cloud project. Do not try to get it to work-- start fresh.
Foreach web/worker role that you use to have in your previous azure projects, create new web/worker roles for those as well. Do not try to get the old ones to work-- start fresh. Copy the content/files from your old ones into the new projects.
So basically, install the latest tools and then create new assemblies/packages/projects to replace the old ones.
I have a web application asp.net to deploy to Windows Azure. This application contains one web role. I try to run it on local first. But when debugging, I catch this error from VS2010: "Window Azure Tools for Microsoft Visual Studio
The Web Browser can not be started. To resolve this problem, you must restart Windows."
I have restarted windows several times, but there was no luck.![enter image description here][1]
I've search so hard to find the solution for this problem but there's nothing seems work for me. I'm a newbie in Windows Azure, it's really a big trouble with me. Please help me! Thanks a lot. Best Regards.
There could be two problems:
Problem with your IIS settings: It is possible that there is a problem with your IIS in your machine which could not be restarted when VS2010, wants to run it.
To verify it what you can do it launch your Web Role using "View in Browser" setting and see if your Web Role can run in IIS, you will see the web role started in a URL as http:\localhost:XXXXX and that would be the first step to resolved.
Problem will your Windows Azure SDK which could not launch the WebBrowser to run in IIS
If you don't have problem in this step #1, then it is possible that Windows Azure SDK has some problem trying to start your IIS from external process and this could be caused by corrupted SDK installation or any other reason.
If that is the case try:
remove all Windows Azure SDK components from your machine.
Restart the machine, Install Azure SDK from here for VS2010
After SDK install, restart the VS2010 in admin mode and try created a hello world webrole and see what happens.
I have a web application asp.net to deploy to Windows Azure. I try to run it on local first. But when debugging, I catch this error from VS2010:
"There was an error attaching the debugger to the IIS worker process
for URL 'http://127.255.0.0:82/' for role instance
'deployment16(6).WindowsAzureProject2.WebApplication3_IN_0'.
Unable to start debugging on the web server ......."
I've search so hard to find the solution for this problem but there's nothing seems work for me. I'm a newbie in Windows Azure, it's really a big trouble with me.
I had similar problem with Windows 8, debuging a cloud application with Visual Studio 2012 RTM and Azure SDK 1.71, when trying to launch the application into the compute emulator. It was a very simple app, but I used Azure diagnostics. At the end these are two things I have changed that have work for me, both turning on Windows 8 features (so go to Win8 and open 'Turn Windows Features On/Off'.
Activate the checkboxes for:
Internet Information Services Hostable Web Core
Internet Information Services > World Wide Web Services > Application Development Features > ASP.NET 4.5
Internet Information Services > World Wide Web Services > Health and Diagnostics > Tracing
Internet Information Services > Web Management Tools > IIS Management Scripts and Tools
That worked for me, it makes sense, as I'm using Visual Studio 2012 and trying to get some trace information using diagnostics in Azure.
I hope this will work for you or give some tip about the problem. In the case of being useful information, remember to vote as response or as value tip.
Thanks,
Mike
This usually happens when there's a problem with the project to be deployed to the emulator (WindowsAzureProject2 in your case).
Try the following:
Check %UserProfile%\AppData\Local\dftmp\IISConfiguratorLogs\IISConfigurator.log file for the error messages. See more details in this answer.
Make sure your project can be started without the emulator. It's a web project, so just try to start it as a regular web project. Or publish it to the separate folder and try to create a website in IIS of it.
Check your *.csdef and *.cscfg files to make sure all the configuration is correct.
Make sure that the build output of your project is not empty. You can do this by going to IIS, find the site with the name similar to deployment16(6).WindowsAzureProject2.WebApplication3_IN_0, right click --> Explore.... Make sure that this folder is not empty and contains all the files required to start a web project successfully.
BTW, there's a similar question: Debugger can't connect when starting local azure project
Follow step 11 from http://www.microsoft.com/en-us/download/details.aspx?id=35448. Worked for me on Windows 8 with Oct 2012 SDk
I just have today the same problem trying to Debug locally with Azure Storage Emulator in Windows 7. So in the Azure project properties, in Web tab, I checked the radio button 'Use IIS Express' and it debugged without problem. I hope this helps someone.
I encountered this exact same problem when I upgraded an existing Azure solution to the Azure SDK 2.1. After some hunting around I uncovered that the upgrade had automatically set the "Local Development Server" setting to "Use IIS Web Server".
Changing the "Local Development Server" setting to "Use IIS Express" fixed the problem immediately.
To access this setting right-click the Azure cloud project file in your solution, select the "Properties" option, tab down to "Web" and you'll see the following setup.
Also, make sure you run Visual Studio as administrator
Please check the version of emulator you have installed. If your code is created in older sdk and you have a new emulator installed it will give you this error.
Check the version of Azure APIs in your project, go to Project > references and right click on Azure dlls to check the version, same sdk version must be installed on the system, higher are optional as azure 2.x are not backward compatible.