I cannot launch Apache Web UI after clicking the Monitor icon in ADF. 401 error - airflow

I cannot launch Apache Web UI after clicking the Monitor icon in Azure Data Factory.
Within the "Manage" tab within ADF I have created an Airflow. Its status is "Running".
When I click on the "Import files" icon I was able to import and select folders okay.
But when I click on the Monitor icon next to it, I am directed to a new web page with "Unauthorised 401" error on it.
In the MSFT docs it states and shows I should be directed to the Apache Airflow Web UI page instead. Azure AD is integrated with that service, apparently.
In the screenshot you can see I have two Airflow instances and you can see the "Import files" and monitor icons. It is the monitor icon button, here, that is sending me to the error message.
the Monitor icon
I was expecting to be sent to the Apache Airflow Web UI page.
Azure Managed Apache Airflow Web UI

I also tried in my environment, and it is working fine for me.
Created Airflow in Azure data factory.
I am getting directed to the Apache Airflow Web UI page.
Try with enabling Preview Experience this option is to try new features. Some examples of what is currently in preview.
As this feature is in public preview and issue still persist. You can raise support ticket to Microsoft from here for more assistance on this.

Related

Cannot move forward when publishing Azure Web App

I am using VS 2019 and web app is asp.net. I have signed into my Azure/Microsoft account through VS. When I tried to publish the app, I got the screenshot below. Somehow the "Next" button is greyed out so I cannot move forward to create my publish profile. By the way, I am learning Azure and using the free App Service Plan now.
You need to create App Serviceļ¼š
see: Publish your web app.
Here is what happened. To associate with Azure, a Microsoft account is linked to an Azure Directory. When I sign into Visual Studio with the Microsoft Account, the link is supposed to established automatically. But somehow it was not for my case. In Visual Studio, open "Personalization Account" page, click "Apply Filter" link, the next scene is where I can select which directory to be linked. I had only one directory but somehow it was not checked. Once I checked it, I am able to publish.

Open Console Application inside Unified Service Desk

I have a requirement where i need to open a Console Application inside Unified Service Desk v4.1.
The issue with me is I am able to open the console application inside Unified Service Desk, However I am unable to write anything inside it. The console application is just appearing as an image inside USD.
So, how can I open the console application inside Unified Service Desk and make the Console application work?
Console application is actually hosted using CCA application. The issue with these applications are once opened, then they become unresponsive.
1. Create a UII Windows Forms Adapter
2. Trigger the process and execute your console application
3. Using Win32.dll setParent Command, pull the application inside your Adapter and that would be it.
Hope this will help

How ti fix the "You do not have permission to view this directory or page." issue in Azure web app services?

I have a simple web app which if I deploy to Azure through Intelij (Using Azure App plugin ) the app works perfectly. But when I tried deploying using Jenkins the log says deployment successful , but when I try to navigate to the site it says "You do not have permission to view this directory or page." Am I missing anything ?
As per my understanding as My project is working fine when deployed using Intelij, but not working through Jenkins, so the problem will be in my Jenkins Job. Here is the configuration I am using :
Publish Files
Files :target\spring-mvc-example.war
Source Directory(optional):target
Target Directory(optional): webapps
Could you please restart the website and check once.
For testing/debugging purposes you can turn on the Azure detailed messaging, and turn back off when its ready for production. To do so, you have to follow these two steps,
Login to Azure > App Services (left side menu) > Your Web App > Diagnostics logs (search box is at the top if you can't find it), then turn on Detailed Error Messages or turn on all of the logging options, up to you. Now add the following in your Web Config file, In your Web Config file add BEFORE system.web closing tag, . Similarly, add BEFORE . Finally, upload the Web Config to Azure and cross your fingers. If you follow the steps correctly, that will show the error messages in detail and hopefully from there

Newly created Asp.net Web App can ONLY RUN ONCE (in VS2017)

Intro:
When i run an asp.net web app that is freshly created, it runs just fine.
However, it runs only for the 1st time. Subsequent runs will fail with this message:
The only way to make it run again is to restart VS2017.
Not even restarting IIS/IISExpress will make it work again.
At this point my instincts tell me there is something stupid/silly going on. What on earth is going on here?
Here is my configuration:
I am using Visual Studio 2017 Version 15.8.4
.Net Framework Version 4.7.03056
Project: Asp.net Web Application (.Net Framework) ==> MVC
This is being run under - IIS Express (Internet Explorer)
Here are more details about the error im seeing:
The error page simply says "Can't reach this page".
When i click on the "More information" expansion link, i see following (mentioned above):
There was a temporary DNS error. Try refreshing the page.
Error Code: INET_E_RESOURCE_NOT_FOUND
Now, if i click on the "Fix connection problems" button, the Windows Network Diagnostics window popups up and says:
The remove device or resource won't accept this connection
If i click on "View detailed information" link at the bottom of this popup, i see following details:
The device or resource (localhost) is not set up to accept connections on port 'X' (where X is my localhost dev port).
Summary:
In the end, there is no real reason why port 'X' is not working any more. If i change the port number from Visual Studio the web app will run. But as i mentioned before, restarting Visual Studio will allow me to run for the 1st time.
* Updated *
I found a great work-around solution. Instead of running (F5), i
simply choose a view (.CSHTML) and execute that view itself
(right-click --> View in browser). This seems to work just fine every
time without messing up the port.

Application Insights extension breaking Azure web app

I had Application Insights running smoothly on an Azure Web App via the AI SDK, reporting to an AI instance hosted in Azure.
The only niggle was it didn't show detailed dependancy diagnostics, according to this page this was because I was using the SDK only, I needed to "Instrument your web app on the server", which looking at the docs can't be done if you already have an instance of AI running....helpful!
Reluctantly I deleted the AI instance, stripped the SDK from my code so I was starting fresh, and followed the steps, however as soon as I finished the process in the previous link my website broke and now responds to every single request (MVC5 and Web API) with an empty 404 request
The AI status page is showing green ticks for everything, and I can't discern anything from diagnostic log dump from KUDO or manage to remotely debug the site.
Deleting the AI extension under Web App -> Extensions in the Azure portal and then restarting the web app fixes the problem.
I've run out of ideas on how to fix this, is there anything else I can do to get to the bottom of the problem?
To fix this problem, delete the following 2 files from your web app's (or slot's) filesystem:
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation32\ProductionBreakpoints_x86.config
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation64\ProductionBreakpoints_x64.config
You can do this easily through Kudu.
Edit: Apparently this is/was an issue with the ProductionBreakpoints interacting with precompiled views. Microsoft has informed me a fix should be out within the next couple days. The version of Application Insights extension I have now that is still broken is 2.4.6 - I will post the "fixed" version when I can confirm it.
Edit 2: Confirmed this is fixed in 2.4.7 which is out now.

Resources