I had to reinstall a version of Visual Studio 2013 Update 4 on my machine.
I had v2.3 of the Azure toolset working with my cloud service just fine.
When I loaded the project again into Visual Studio, it asked me if I wanted to upgrade to v2.5 or download v2.3. I tried to download v2.3, but the link wouldn't work.
I then upgraded to v2.5 which blew my cloud service to bits when it tried to publish it.
I'm getting the following attached errors:
The first dialog is basically is asking me to upgrade to 2.5 or download 2.3.
The images are returning the three errors when the service tries to get published:
1.Starting role... Unhandled Exception: System.NullReferenceException
2.Role has encountered an error and has stopped. Unhandled Exception: System.NullReferenceException
3.'microsoft.windows.azure.diagnostics.directoryconfiguration' is obsolete: 'this api is deprecated.'
It worked fine with v2.3 and now with 2.5, it's getting the above errors.
Can someone please inform me how I can correct this issue so my cloud service will be published correctly?
Related
I updated and migrated my local project to start using ASP CORE 2.1.0 from 1.0. I followed the ASP CORE migration guideline from Microsoft here:
https://learn.microsoft.com/en-us/aspnet/core/migration/1x-to-2x/?view=aspnetcore-2.1
Then 2.0 to 2.1 here:
https://learn.microsoft.com/en-us/aspnet/core/migration/20_21?view=aspnetcore-2.1
And everything works just fine on my local machine.
After pushing the code, it builds and runs just fine. So no error occurred when running the website. But when I hit the website on my browser, Azure is throwing 500 internal error messages. I checked the logs, and this is what I find:
2018-08-01 07:05:25.682 +00:00 [Error] Microsoft.AspNetCore.Server.Kestrel:
Connection id "0HLFNDIE4UDCG", Request id "0HLFNDIE4UDCG:00000003": An
unhandled exception was thrown by the application.
System.InvalidOperationException: Cannot find compilation library location for package 'System.Data.SqlClient'
at Microsoft.Extensions.DependencyModel.CompilationLibrary.ResolveReferencePaths(ICompilationAssemblyResolver resolver, List`1 assemblies)
at Microsoft.Extensions.DependencyModel.CompilationLibrary.ResolveReferencePaths()
...
I tried adding System.Data.SqlClient to my local code using Nuget, and pushed to Azure, and still I get the same problem.
Can someone please explain what's happening here? And why Azure needs this package when it's not part of my project?
This is a reference path issue.
Check for System.Data.SqlClient in the references and verify the location form which the package is referred. It looks like the path is there in your local machine and not available after deployment.
I figured out what I could do.
I went into the azure console, and typed this in:
nuget install System.Data.SqlClient
And it added the package into the system. The error now stopped.
I am having a new issue when deploying Azure Cloud Services via Visual Studio 2015 SP1.
This is driving me up the wall and I am curious if anybody else has seen this? Basically, I can build just fine, I just can't package for or publish to a Cloud Service - the error is:
CloudServices232: The role MyProject.AsyncWorker is using an unsupported TargetFrameworkVersion v4.6.1.
This wasn't happen a few weeks ago, but now I can't publish it. Yes I am targeting .NET 4.6.1 - but that has been WORKING JUST FINE for a while now and I followed all the steps to run install.cmd and manually deploy it.
This appears to be a new build-time error (it used to be a warning).
I have an issue, I am trying to upgrade the MarsAgent (Azure agent) on a Windows 7 PC. When I try to update it I get the error:
"An unexpected error occurred during the installation. For more details check the setup error logs.(Error ID: 116)".
You then press OK on that error and I am then presented with
"Error starting the Microsoft Azure Recovery Services Agent Setup Wizard"
Can you please help!!!
I was also getting same error whet tried to installed MarsAgent on win2016 server. I tried many articles but no luck. When I selected installed with window updates it shown me error for window update service. so I checked Windows update service found it was in disabled state, hence I set startup type automatic and started service then tried. Issue resolved no error found.
I'm trying to publish my app to Azure which I have done several times before. For some reason I'm now getting the following error:
The Windows Azure SDK for .Net must be installed to enable publishing
to Windows Azure. LightSwitch will load a web page to begin
installation.
It loads a web page, downloads V11AzurePack_1_8_1.exe which in turn runs the Web Platform Installer 4.6 which in turn installs Windows Azure SDK Tools 1.8.1 for Visual Studio 2012. All of this succeeds. But going back and attempting to Publish results in the same error.
I noticed that there is a Windows Azure SDK for .Net (VS 2012) - 2.2 in the WPI. So I installed that manually, tried to publish, same result.
The SDK is clearly installed:
So why can't I publish to Azure? The only thing that looks like it might be a problem is that I have LightSwtich Azure Publishing 1.1 add-on for Visual Studio 2012 installed and I know there is a newer version of that available. But I can't find a direct download nor can I find a way to uninstall that package or force WPI to suggest an update.
Uninstalling everything Azure related (except the LightSwitch add-on as that seems to be unremovable and un-upgradeable), rebooting, and installing only the latest SDK produces the same problem.
After following a moderator's advice to repair Visual Studio on the forum, I was no longer able to open my project at all. I waited for a response but got none. So I decided to reinstall Visual Studio all together.
I followed this and this in order to remove as much of Visual Studio as possible and then reinstalled. I then installed Update 4 and was again able to open my project.
However, upon trying to publish, the same error was encountered.
I decided to upgrade my project to VS2013. That all seemed to go well. Wnet o Publish to Azure and it claimed that it succeeded. However going to Azure and launching the app's site brought up the previous version.
I deleted my Azure cloud service and started a new project in VS2013. I copied over one of my screens to have something to run. I then tried to publish to Azure. It again told me it succeeded but the site did not exist in the Azure Management portal. However, it did realize that I had created a new self-signed certificate so there was some type of communication there. Just not an actual Publish.
Then I did something really stupid. I uninstalled the Azure SDK and tried to reinstall it thinking that was the problem. Now I'm back to where I was before. An endless loop asking me to install the Azure SDK.
I wiped out all of my Azure services. Did a system restore to a month ago. Reinstalled the Azure SDK. This then allowed me to "Publish".
Not really.
Visual Studio claimed that the Publish Succeeded. The services were created and the certificate uploaded but nothing was deployed. I then did a manual deploy and the Production instance began to be deployed.
Everything seems to be running but I cannot access my app's site. I receive a 403 Forbidden error message. With or without HTTPS required. But this seems to be a different issue so I'm going to open another question on it.
Why these extreme measures were required is beyond me. This continual breaking of LightSwitch to Azure publishing is getting to be absurd though.
I installed the new Azure SDK from the Web Platform Installer.
Now when I try File > New Project > Cloud > Windows Azure Cloud Service > OK
Then I get this error message:
Error: this template attempted to load component assembly 'Microsoft.VisualStudio.CloudService.Wizard, Version=1.0.0.0 ...
I have tried everything I can think of including uninstall of the 1.8 SDK, uninstall of the 2.0 SDK and reninstall. Always I get this message. I cannot see anything about this on the internet. My install gave no error messages.
Also noticed that now in Server Explorer I only have Data Connections, Servers, Windows Azure Service Bus and WIndows Azure Web Sites. There's nothing for storage.
Does anyone have any ideas what may be wrong.
I've had the same problem with skd 2.0
Even trying repairing or installing missing features won't work.
After hours spent on repairing and reinstalling, the only solution I found was to uninstall BOTH Visual Studio and Azure sdk, and installing them again.
After the reinstallation it works fine, but I still have no clue why :P
I keep a development VM for each SDK that comes out. When I upgrade older projects to newer SDKs there are bugs, sometimes bugs without workarounds. I've learned the hard way that installing a new SDK is dangerous.
If you can, develop inside a VM and take occasional snapshots. Otherwise, you do end up reinstalling Visual Studio and installing the original SDK that you first created you project with. -Richard
I've seen this issue on multiple machines after upgrading to 2.7, 2.8, and/or 2.9. Reinstalling VS, VS Updates, and/or SDKs would sometimes help, but sometimes not. The last time no combination of installs worked.
I finally ran Visual Studio with logging enabled via Devenv /log, and according to the %AppData%\Microsoft\VisualStudio\{version#}\ActivityLog.xml file, there was an error merging the configuration file located at %LocalAppData%\Microsoft\VisualStudio\{version#}\devenv.exe.config I deleted that config file and restarted Visual Studio and the problem went away.
Uninstall Visual Studio using VisualStudioUninstaller did the trick for me.
Then I did a clean install of Visual Studio and Azure SDK, and everything worked just fine!