We deployed a function a few days ago and witnessed it show up in the portal, along with seeing logs show up in App Insight. Yesterday and today we no longer see the function in the portal or in VS Cloud Explorer. I know it's still there and running because I can see the transactions showing up in our database every 15 minutes(timer job).
Any help on what's going on and/or what caused it not to show up in the portal? And how to fix this?
Looks like you are suffering from Runtime 2.0.11888 breaking change.
Temporary 64-bit platform option is not supported, this option worked for previous versions but actually w3wp.exe process started as 32-bit.
Please switch to 32-bit in "General Settings" or you can use previous version by setting FUNCTIONS_EXTENSION_VERSION=2.0.11857-alpha. Next release will have true 64-bit support.
My functions disappear like yours after I switch Platform to 64-bit. They come back once back to 32-bit or set FUNCTIONS_EXTENSION_VERSION(under Application settings) as 2.0.11857-alpha.
Update
Begin with beta 2.0.11946 runtime, x64 support is back.
Related
I'm trying to remote debug an asp.net core 1.1 api app (targeting .net framework 4.5.2) that's running on Azure.
I attach the debugger via Server Explorer. The debugger attaches to the correct process. But any breakpoint I set has the message "The breakpoint will not currently be hit. No symbols have been loaded for this document."
All answers I've seen to such a problem assume that the modules window shows all modules loaded by my project, but in my case the modules window is empty!
I'm on VS2017 15.4.
If I remember correctly, I was previously able to remote debug the same project with version 15.2. The problem started occurring when I updated to 15.3 but I didn't pursue it at the time.
I submitted the problem on the MS forums: Can't remote debug Azure API app
and now I have received an official reply that it is indeed a bug in VS, and a fix will be available in the pending release (15.6).
They also suggested a workaround, which I tried and indeed worked: Manually Attach a Debugger to Azure Web Apps
Which involves:
Going to the web app Application settings in the Azure portal, and making sure that Remote debugging is enabled,
In the VS menu: Debug > Attach to Process..., entering the web app url with the debugging port, e.g.:
myapp.azurewebsites.net:4022
Then in the credentials that appears, entering the username & password that are available in the app's Publish Profile, which can be downloaded from the portal. If the username is $myapp, it should be entered like this:
$myappp\$myapp
Then choosing Managed(v4.6, v4.5, v4.0) code and then the name of the Core app.
Actually, I had found and unsuccessfully tried similar approaches before. The key for me was step 3. The others had suggested entering the username as .\$myapp, or myapp\$myapp. So make sure to enter it as written above.
BTW, seeing that the above blog post is from almost 2 years ago (Feb 2016), whereas the problem I'm experiencing was introduced only a few months ago, it seems to be a cure-all, and it is therefore worthwhile, for anyone who has to deal with remote debugging Azure apps, to save this information for future reference.
UPDATE:
After updating VS 2017 to version 15.5.2 the problem seems to have been fixed.
I have had the same issue with Visual Studio 2019. The fix for me was just to go in the VS menu: Debug > Attach to Process, and try to connect as describe by #Dan Z. The connection was not established, saying No connections found, but attaching a debugger from Cloud Explorer again, right after an attempt in "Debug > Attach to Process" is always successful. That is most probably a bug in VS
I have successfully used the WPRUI and WPA applications in the past, the last time a month ago, to identify performance problems in our C++ applications. But today I recorded a new trace of one of them, and open it just to see WPA crashing.
It's reproducible every time by opening an ETL and going to Graph Explorer -> Computation -> CPU Usage (sampled) -> unfold. Just clicking to see the CPU sampled graph list. Sometimes it crashes silently, sometimes with the dialog that lets you debug the crash.
Has anybody experienced problems like this? I don't see any support forum in the Windows Performance Toolkit site, and I would like of course to find a solution for this. Any hints are greatly appreciated, thanks in advance.
PS: reinstalling doesn't help. Neither does removing user preferences. The stack only showed me a problem accessing memory out of bounds, in a "Task" class, but I can't get the debug dialog to show again (it's crashing silently now, every time).
PS2: the only significant change I remember to have done in this past month is installing the CTP of Visual Studio 2015, and letting Windows upgrade a bunch of packages it had pending (I'm in a capped subnetwork and Windows doesn't upgrade automatically).
The VS2015 CTP installs a .Net 4.6 pre-release version. Maybe this .net versions causes the issue. So remove VS2015 CTP and the .Net 4.6 Preview and reinstall .Net 4.5.2.
I've been following the progress of VS 2013 as its progressed through its releases (Beta, RC, and now GA) and have had an overall positive feeling about the release. Today, I spent the day working entirely in the new version (GA Premium) to ensure that it provides all of the basic functionality needed by my team prior to adoption.
It works well for general dev tasks - given several of my favorite extensions haven't been ported yet - but while attempting to administer our Azure storage from within the IDE it appears to be removed from the previous release.
While in VS2012's Server Explorer, I'm able to link to Azure account to discover all of my top level objects - Cloud Services, Service Bus, Storage, and VMs. Now within VS2013 - following the same setup procedures from the previous version - I only see Mobile Services, SQL Databases, and Web Sites under the Windows Azure node of Server Explorer.
After a little googling I found little insight or even others asking the same thing (since GA) so I'm starting to wonder if it's just me or if this is the way it'll be from now on??? Can anyone confirm and/or provide evidence from Microsoft indicating that this is intentional?
Installing the Windows Azure SDK should give you all of the features you're looking for. You can find directions here: http://www.windowsazure.com/en-us/develop/visual-studio-2013/ for using the current version of the SDK with the VS 2013 GA release.
I've just installed the Visual Studio 2012 RTM on a Windows 7 x64 desktop.
Unfortunately, I'm very underwelmed by the performance of the out-of-the-box installation. Everytime I try to rename a file in the solution explorer, change to a MVC cshtml editor, open a designer view, or intellisense pops up when I start typing with the c# editor, the whole visual studio applications hangs for 5-10 seconds.
There are no customizations, plugins, extensions enabled here that do not get applied with the standard installation.
Has anyone else experienced this? Has anyone else found a way to log the application faults which occur, or detect the hang. I need some way to determine what is going wrong, in order to identify what needs to be altered to rectify the installation.
The problem is you are consuming the lot more resources of the system which is causing hung state of VS. Please close any of other application who is using more RAM. You can take the help of Task Manager to close those application. Please keep in mind if you are running SQL standalone database instance services then its also causes the hand issue. The best is keep you system free from running unuseful application or Go for System upgrade. :-)
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.