When Configuring Microsoft Identity Platform inside VS for my publishing profile, I am getting the following errors:
****Failed to Update Azure AD app
Failed to configure Update Azure AD Failed to configure dependency
Microsoft identity platform identityapp.aad1****
If you are added Read directory Data permission while configuring azure Active directory in visual studio
Add the Directory.Read.All permission to the your app registered under active directory through Azure portal.
Related
Environment
MacOS 10.14.6 Mojave, Visual Studio For Mac v8.7.9
API service built on .NET Core framework
Issue: I have a .NET Core project that has a web deploy publish profile to deploy updates to the windows server running on EC2 (IIS).
When I was working on windows, I could easily deploy it through the web deploy UI in the visual studio but after I migrated to the macOS, cannot find such option in the visual studio. I can click on the existing web deploy publish option but it always fails because I need to provide the password somewhere. I tried to add <Password> under the pubxml file but it doesn't read as a valid tag.
Existing publish profiles
Error
/usr/local/share/dotnet/sdk/3.1.403/Sdks/Microsoft.NET.Sdk.Publish/targets/PublishTargets/Microsoft.NET.Sdk.Publish.MSDeploy.targets(140,5): error : Web deployment task failed. (Connected to the remote computer using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.)
/usr/local/share/dotnet/sdk/3.1.403/Sdks/Microsoft.NET.Sdk.Publish/targets/PublishTargets/Microsoft.NET.Sdk.Publish.MSDeploy.targets(140,5): error : Make sure the site name, user name, and password are correct. If the issue is not resolved, please contact your local or server administrator.
/usr/local/share/dotnet/sdk/3.1.403/Sdks/Microsoft.NET.Sdk.Publish/targets/PublishTargets/Microsoft.NET.Sdk.Publish.MSDeploy.targets(140,5): error : Error details:
/usr/local/share/dotnet/sdk/3.1.403/Sdks/Microsoft.NET.Sdk.Publish/targets/PublishTargets/Microsoft.NET.Sdk.Publish.MSDeploy.targets(140,5): error : Connected to the remote computer ("ec2-3-92-105-216.compute-1.amazonaws.com") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
/usr/local/share/dotnet/sdk/3.1.403/Sdks/Microsoft.NET.Sdk.Publish/targets/PublishTargets/Microsoft.NET.Sdk.Publish.MSDeploy.targets(140,5): error : The remote server returned an error: (401) Unauthorized.
Publish failed to deploy.
Currently I have not yet found the answer for that but I've found a kind of work around.
I publish the project to a folder (be careful with dotnet parameters) and after that manually copy files in "bin/Release/netcoreapp3.1/publish" v. ftp to my server.
In order to save a lot of time, it makes sense to copy only newer / different size files.
Not elegant at all, but this is the way how it works for me now.
Will be happy to hear, someone found a solution how to store the password for webdeploy on MacOS
I am trying to run the Xamarin.Android app from Microsoft Azure Guides.
According to the guide I am supposed to right-click on the Service project and Rebuild, after that on clicking Publish I get the Publish Target window but there is no target of Azure App Service. I only get Target of Azure Web Apps
Updating the Azure SDK was the solution for me. The following page has all the downloads, select your visual studio version to the left
https://azure.microsoft.com/en-us/downloads/
VS2015 Direct link: https://go.microsoft.com/fwlink/?LinkId=518003&clcid=0x409
I'm assuming the project to which you refer is the "QuickStart" server-side project that is downloaded and named yoursite-Runtime.zip. When unpacked, you get a folder yoursite_AppService and yoursite.sln in the file.
When you right-click and select Publish, you should see the following picture as the pop-up:
If this is not the case, then there is something at issue with your install of Visual Studio 2015 - perhaps an additional plugin or an older version of Azure SDK? Try updating the Azure SDK as a starting point.
When trying to publish a cloud service to Azure i keep getting this error: The extension ID MSVSAZ-ApprovedProducts-WAD11-8 is not found in the hosted service.
Is there a quick resolution to this that doesn't require me to restart visual studio each time this occurs?
As Khoi mentioned it has to do with Windows Azure Diagnostics. You can either disable the Azure Diagnostics from your project
or you need to add the Azure Diagnostics to your Azure subscription.
Here is a link how how to configure.
https://learn.microsoft.com/en-us/azure/vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines
To disable you would need to uncheck the Enable Diagnostics and not check it.
I have been using Visual Studio to deploy a Web Service to Azure; downloaded my publish profile to enable that and it was working fine for the past few weeks.
Today I tried to deploy an update and now all my deployments fail with the following:
17:25:03 - Preparing deployment for WindowsAzure1 - 25/03/2013 17:24:53 with Subscription ID 'xxx' using Service Management URL 'https://management.core.windows.net/'...
17:25:03 - Connecting...
17:25:04 - Object reference not set to an instance of an object.
17:25:04 - Deployment failed with a fatal error
I'm not sure what's failing here; is this saying it's unable to connect to the Service Management URL?
Last week I installed an SSL certificate on Azure and now I'm not seeing the option to download my publish settings. I know it used to be there but isn't now. Does having an SSL prevent me from somehow connecting to the management page?
Edit
Before leaving work I removed the certificate but when I then checked for the PublishProfile it was still not showing.
The PublishProfile is not available for any of the other users attached to the subscription - so I don't think it's related to my login.
Edit 2
A bit more drastic; I've now tried deleting my storage and service, to start from scratch. I created a new publishsettings file by removing the subscriptions already imported into Visual Studio and then following the link to "Sign in to download credentials". Next I created a new service and storage in Azure and tried to publish but the deployment still fails when connecting with
Object reference not set to an instance of an object
I have no idea what else I could try or what could be wrong, or where to look to find out.
I got the same error today. Why it wasn't working was because I hadn't uploaded the certificate in the managementportal prior to the publish.
After adding the certificate, everything worked just fine!
You can read more here: http://www.amido.co.uk/mark-omahoney/publishing-in-windows-azure-object-reference-not-set-to-an-instance-of-an-object/
The best way to solve above problem is to download the latest PublishSettings from Azure Management Portal and then use it with Visual Studio. This way your connection to Windows Azure Management Portal from local machine will be verified and validated. Once you have the basic connection working then you can publish your application to specific Windows Azure Service.
Also you can log into your Azure Management Portal and remove all old management certificates which are added in previous publishsettings download attempts.
The problem, in my case, was that my solution Cloud project had the thumbprint of the SSL certificate I'd uploaded in its ServiceDefinition.csdef and ServiceConfiguration.Cloud.cscfg. In my first edit I said that I'd removed the certificate from Azure, but hadn't then removed it from the project files; commenting them out allowed me to publish from Visual Studio again.
I'm not sure why this happened though, I had uploaded the certificate to Azure and was able to connect to my service on https in FireFox so the SSL was "working".
Web Deploy v3.6 BETA3 was released that fixes this issue. To resolve this error, you can download the Web Deploy beta and patch your VS2013 installation. http://azure.microsoft.com/blog/2014/08/11/web-deploy-3-6-beta-released/
Test Validate Connection once you installed the above Web Deploy. If it works, then fine else you can modify the proxy settings used by msbuild.exe (msbuild.exe.config) and check you can now publish from behind a proxy with Web Deploy.
Regards,
Logesh Shan
I think the certificate got corrupt. Deleting the solution .suo file and the .ccproj.user file in my Azure project did it for me.
I have gone through the Lab AdvancedWebAndWorkerRoles which you have provided in the latest training kit WAPTK. I followed the steps in Exercise 1:registering sites,Applications and Virtual directories .It is running fine in windows azure emulator(locally),but i cannot find any steps to host in the windows azure management portal.
Can any one suggest(steps) how to host the same application in the windows azure management portal?
We know how to deploy applications in windows azure portal.As i had mentioned in my question about the Exercise 1:registering sites,Applications and Virtual directories in the training kit WAPTK ,we want to create the similar application and host in the azure.The steps to host the Exercise 1 application in management portal is not mentioned in the training kit.We tried to host the application in windows azure portal but it is not working as the ServiceDefinition.csdef include some different configurations.We wanted to know the steps to host that application in management portal.
Under the Introduction to Windows Azure lab, look at Exercise 3: Publishing a Windows Azure Application. This shows how to publish via the portal. The basic steps:
Build your Windows Azure service in Visual Studio, but tell it not to publish. Just generate the package file and configuration file.
Create a new hosted service. This gets a name like myapp.cloudapp.net. You'll need to find a unique DNS prefix.
Select the generated package file and configuration file, from the portal, which results in your service being launched. This takes a few minutes, and you can watch its status via the portal.
You may also publish directly from Visual Studio. See this MSDN article for instructions on setting up Visual Studio correctly (which basically imports your publishing settings from the portal). Visual Studio can perform all of the steps without having you to actually do anything in the portal (aside from exporting your publish settings).