I'm a starting dev and this site helped me a lot so far, thought somebody could maybe help with this. I have a SSD with 16kb sectors and couldn't install SQL Server 2022, ran the offered command solutions (did a bunch of other things in between, install and uninstall etc).
Now I find myself completely unable to even access SQL from shell (and also unable to uninstall express duplicates). Does anyone perhaps know what I could've messed up ? Tried to find solution on the website (and else) and couldn't find my specific problem.
Thanks in advance for any help.
EDIT : just realized the screens are in french, my bad. The shell screen states that <sqllocaldb> isn't recognized as a command name or function etc. First (white) screenshot is of my services displaying how I can't start SQL with an error code.
After upgrading to VS 16.10.0 (and then 16.10.1) Community Edition a React website no longer runs w/in Visual Studio/IIS Express. The exact same code was just deployed to an Azure app service and works correctly.
The home page is blank and the following error is displayed in the Chrome (Version 91.0.4472.77 (Official Build) (64-bit)) debugger console
"Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR"
The solution consists of:
C# class library (.NET Core 3.1)
C# Web API (.NET Core 3.1)
React website
I have tried the following:
Cleaned and rebuilt solution
Cleared browser cache
Uninstalled and re-installed Visual Studio
Upgraded Visual Studio from 16.10.0 to 16.10.1
Ran npm run build which ran with no errors
Additional Note: I was able to restore a virtual machine w/ Visual Studio 2019 v16.9.4 instead of v16.10.1. Then step by step I installed the latest Windows updates and the exact code base. The site runs correctly in v16.9.4. So the problem seems to be in Visual Studio v16.10.0/v16.10.1
Go to the VS Developer Community and up vote this problem
https://developercommunity.visualstudio.com/t/Failed-to-load-resource:-net::ERR_HTTP2_/1446262
This error was driving me nuts too. Windows 10 was updated 2 days ago and I also updated Visual Studio to version 16.10.1. After that, I got the errors, images, CSS not loading correctly.
As SpeedOfSpin mentioned in a comment in a previous post, uninstalling KB5003637 worked instantly for me, no more errors! Everything loads perfectly now.
It wasn't necessary to go back to an earlier version of Visual Studio, it seems it was Windows OS related.
#SpeedOfSpin: Thnx a lot! :)
UPDATE ON ISSUE 1
Today there was a new update KB5004476, I don't see the previous KB5003637 anymore here. KB5004476 is causing the same errors. When installed I get the exact same error "Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR", uninstalling solves it instantly again.
I have asked the Microsoft forum what is going on here:
https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/kb5003637-and-the-new-kb5004476-gives-error-failed/db2f2f73-7f5c-477a-b212-5f13c998a09a
UPDATE ON ISSUE 2
As they couldn't provide a solution in the first MS forum (previous link), the same question has been asked here:
https://learn.microsoft.com/en-us/answers/questions/440339/kb5003637-and-the-new-kb5004476-gives-error-34fail.html
Updating Visual Studio to version 16.10.2. doesn't solve the issue either.
UPDATE ON ISSUE 3
After some more testing, it seems it affects the browser Chrome only (As I only use Chrome, as most people do). In Firefox, Edge, and IE it seems I'm not having this issue. It was confusing as I tried so many things and the only solution I still have is uninstalling the KB5003637 or the new version KB5004476. So I guess something is wrong with Chrome after all. For now, I will keep the updates uninstalled, I don't feel like changing my preferred browser.
UPDATE ON ISSUE 4
It is indeed not a Chrome-only issue, sorry guys. Saw the same error in Edge this morning too. It took a long while to recreate the problem, while in Chrome I have it every single time. :(
UPDATE ON ISSUE 5
As asked in the first post here by ChrisP, go to the VS Developer Community if you experience this issue too, and please upvote this problem.
I asked the question there also, but still no solid solution at this point.
https://developercommunity.visualstudio.com/t/Failed-to-load-resource:-net::ERR_HTTP2_/1446262
UPDATE ON ISSUE 6
Two days ago after 1 single refresh (F5), when testing my web application, aside from the HTTP/2 errors, I also had the same blue screen like people are starting to mention. It showed the error "System Thread Exception not Handled" in file "HTTP.sys" and restarted, amazing!
Also, 2 new updates were installed KB5003690 and KB5003537, but nothing changed, I still have the annoying errors. Previous updates KB5003637 and KB5004476, where it started to go wrong, are gone here.
Uninstalling these updates as a workaround isn't the best solution for me, as they get reinstalled when wanting to update Windows 10 (No option anymore to exclude/hide the updates).
For me the easiest/quickest workaround at this point, to test locally with no “Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR” errors, no "System Thread Exception not Handled" BSoD! error and most important no stress anymore :), is disabling SSL in the debug settings of your project in Visual Studio. (Right-click Project, Properties, Debug, Web Server Settings below).
Hope this gets fixed quickly!
UPDATE ON ISSUE 7 (SOLVED!)
Microsoft finally released a fix that works for me, more information here (last post):
https://developercommunity.visualstudio.com/t/Failed-to-load-resource:-net::ERR_HTTP2_/1446262?viewtype=all
Installing the most recent update KB5004237 solves the problem in my case. No more "Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR" errors, no more “System Thread Exception not Handled” error so far too!
I tried everything including rolling back updates and a full reinstall of Windows. Finally, a Microsoft support rep posted a workaround for this that involves disabling HTTP2. This seems to have worked for me as a temporary solution. In summary:
Start the Windows Registry Editor
Navigate to the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters
Add 2 new REG_DWORD values, EnableHttp2Tls and EnableHttp2Cleartext,
to this registry key
Set both values to 0
Reboot the machine
The rep notes:
The registry values disable HTTP/2 on the machine. You can remove those values when the fix to https.sys is published.
We had the same issue on only the machines that had that KB5003637 installed. We uninstalled it and everything was fine. We decided to upgrade to .net 5 in the end which fixes the issue as it was fairly painless for our projects.
If you can't upgrade try disabling HTTP/2
serverOptions.ConfigureEndpointDefaults(lo => lo.Protocols = Microsoft.AspNetCore.Server.Kestrel.Core.HttpProtocols.Http1);
Mine looks like this for .net core 3.1
public static IHostBuilder CreateWebHostBuilder(string[] args) =>
Host.CreateDefaultBuilder(args)
.ConfigureWebHostDefaults(webBuilder =>
{
webBuilder.ConfigureKestrel(serverOptions =>
{
serverOptions.Limits.MaxRequestBodySize = int.MaxValue;
serverOptions.Limits.MinResponseDataRate = null;
serverOptions.ConfigureEndpointDefaults(lo => lo.Protocols = Microsoft.AspNetCore.Server.Kestrel.Core.HttpProtocols.Http1);
})
.UseStartup<Startup>();
});
}
Disable the SSL from the project properties it will automatically down to http/1 and then enable the javascript debugger for the browser
Hope this will help
In my case it was ASP.NET Core Identity that caused the trouble: I had too many roles (user claims) which were stored as session cookies in my browser and caused a "HTTP 400 Bad Request - Request header too long" error. This was showing as HTTP2 protocol error in Chrome and SSL certificate error in Firefox since I was using HTTPS redirection.
In my case it was actually a HTTP Error 400 - The size of the request headers is too long, but I kept getting this ERR_HTTP2_PROTOCOL_ERROR message instead.
In order to find out the real error message, I had to disable HTTP/2 in IIS(right click your site in IIS, open Edit Bindings, double click your HTTPS binding and check Disable HTTP/2).
After fixing the HTTP Error 400 I could enable HTTP/2 again and it worked correctly.
I found that disabling SSL (which I think results in IIS Express dropping down to HTTP 1.1) is a workaround.
this issue (on iis express) on only the OS that had that KB5003637 installed.
if you unable delete this update first upgrate windows 10 to last by
https://www.microsoft.com/en-ca/software-download/windows10
then you can delete kb5003637
(don't forget disable windows auto update)
I got this error creating a new blazor app vs2019/windows10 update to latest versions.
After looking at a prior working blazor project Startup.cs I fixed by commenting out //app.UseHttpsRedirection();
I think this maybe a new project template problem
In my case, upgrading the project to .Net core 5.0 (as #SpeedofSpin suggested) did not help - I had the same issue.
Disabling SSL (as #samejeep suggested) for application was demanding, because my projects uses IdentityServer4 and it just stopped authenticating after that - so I didn't continue that path.
But as a workaround I have changed all requests for css, js, and static files via non-SSL http:// requests.
So for example, instead of this
<link rel="stylesheet" href="~/css/site.css">
Which would use the current request's protocol https://, I've used absolute paths, e.g.:
<link rel="stylesheet" href="http://localhost/css/site.css">
Note, that I'm stating "http" (not "https") explicitly.
I did that for css styles and js scripts and that was enough for me.
I didn't have to do it for images though.
For me this is just a dirty workaround (I'll be waiting for MS to release a patch), but at least it allows me to keep doing my work.
Update:
I've found a better way to disable HTTP/2 via registry on my localhost and that solves the problem too.
I have not been using Azure Machine Learning service (preview) for too long. To my knowledge it only has been released since the last Microsoft Ignite conference. That's why I think I can not find my question on StackOverflow or any other forum for that matter.
It is as follows:
With help of the Azure Machine Learning service SDK in Python I created my experiment in a Jupyter Notebook locally.
I then configured it to run a Hyper Drive config,
The results came in one by one (as I had a total of 50 runs and 4 simultaneously). It took 7 hours to complete the Hyper Drive run in total.
The next day I went to portal.azure.com to view the results and that worked. I was able to see every run of the hyperdrive and could even compare results.
But then....
I have no clue to as what could have happened, but when I tried to navigate to the experiment again I got a blank white screen. When opening the dev console via F12 I got so see a lot of red errors. All from react. I have zero experience with react, but I am quiet sure that this is the error. React errors when viewing experiment
Hope someone can help. Thanks in advance.
Thanks for reporting this! It's a known issue and a fix is being rolled out.
I've been working on a mixed desktop-and-web based solution for quite some time now. My local development environment was using VS2013-Pro, a recent DNN version (7.3, I think), Webmatrix 3, IIS Express 8.0, and SQL Server 2014 running on Windows 7 on Parallels on my Mac. Everything is up-to-date, all SP's installed, etc.
I developed a couple of REST webservices and a DNN module, and it's all been humming along and working really--shockingly--amazingly(!) well, when very suddenly:
I hit the DNN site and Webmatrix crashes and I get an error that says "IIS Worker process has stopped." And hasn't worked since. The debugger gives me the message "Unhandled exception at 0x762CC42D (KernelBase.dll) in iisexpress.exe: 0xE0434352 (parameters: 0x80131530, 0x00000000, 0x00000000, 0x00000000, 0x72F90000)."
I did not change anything, this started in the middle of a coding session. It worked fine for months, and then it just didn't any more.
I researched a bit and found several suggestions, none worked (delete cache folder, uninstall/reinstall). I find another post that mentions that Webmatrix is a dead product now. I try just to set up same site in IIS (following DNN's own instructions and a couple of other very similar sets I found). Still can't make site load--even the front page.
I download a fresh DNN install package (7.4 now) and try from scratch. Now when I try to load the site I get Visual Studio's Just In Time Debugger telling me an unhandled Win32 exception in w3wp.exe [2648]. I try running the debugger but it doesn't actually give any information.
I feel like other than the Webmatrix/DNN installation I've always had a lot of trouble getting DNN running locally, even following the directions to the letter. I need it running locally because I work disconnected a lot.
Am I missing something big here? Is anyone else having trouble all of a sudden? I've spent the better part of 4 days unistalling, reinstalling, tinkering, and can come up with nothing.
-Tim
OK, so after uninstalling everything (down to the metal, everything to do with SQL server, IIS, Webmatrix, and the recent .net framework updates) and then reinstalling them, I've been up and running for a week or so now. I've disabled Windows update, I think it was something in there that got me in this position in the first place. Not a great long-term solution, but it'll do for now.
I had a Drupal website in drupal 6.x When i wanted to upgrade it to 7.x, the custom theme i was using was absolutely outdated, so i imported my Zen subtheme from another website. For doing that, i just copied the folders "zen" and "mytheme" from the other installation to this one. Then i selected "mytheme" as the current theme and changed some little things to adapt it.
The fact is now i'm experiencing the following problems:
I can't auto-update nothing. It downloads the files but then it stacks (and leaves the site in Maintenance Mode).
I can't run update.php. I can go on until i reach the "Run updates" step, which shows a blank screen. This is the main issue, i think, as it evidences -in my oppinion- a problem of communication between the site and the database.
In the Webform module i can't select "File" as a Field Type. This one is not that important, but it may be relevant for someone who knows more than me.
Edit:
Recently i migrated from a Shared to a VPS server. When i migrated, the subdomain in which i was experiencing the issue threw an incompatibility related to the lenght of the password of the database. I changed the password and it started to work again. This may help somebody for helping me. Thanks!