When I run my Blazor WASM locally on IIS it works perfectly. But when I do it in a windows server 2012 R2 and I call it from my computer it gets stuck at "loading..." and I get a "500 (Internal Server Error)" for blazor.webassembly and blazor.boot.json
I cannot test it directly on the server since it has only internet explorer which is not compatible.
chrome developer tools printscreen
I have followed different tutorials, so I have already installed "URL rewrite" and the "Windows Hosting Bundle Installer".
Any idea what to try next? I have been searching in forums for two days now.
Related
I'm having troubles enabling remote debugging on sharepoint online. I have 2 machines, my local machine (Windows 8.1) and my development server(Windows Server 2008 R2). On my development server I first tried remote debugging using Visual Studio 2012 Update 4, as described here: http://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/#remotedebug.
When this didn't work I tried doing exactly the same thing on my local machine, which has Visual Studio 2013 (Ultimate) update 1 and the latest windows azure sdk (2.3). This worked perfectly. Thinking upgrading to visual studio 2013 would solve my problem I've installed 2013 (Premium) on my dev server, next to 2010 and 2012. After installing and updating everything for 2 hours however, I came to the conclusion that I received the same error as on VS 2012.
Googling came up with a few interesting causes for this bug: sitenames longer than 20 characters or sitenames containing hyphens. This is not the case. Then I verified port settings, the dev server has no active firewall but I wanted to exclude any possibilities. And low and behold, both telnetting from my local machine as my dev server to ports 4016 and 4018 of my azurewebsites.net url worked.
Are there any other solutions for this bug? Since debugging locally is not an option (sharepoint provider hosted app for project online) this is very inconvenient.
Thanks,
UPDATE: Deploying the site as a cloud service works, and so does remote debugging them. However, we would like to stay with azure web sites for now..
I know this is a duplicate of Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023; but none of the solutions there or on twitter were of any use.
Check out Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023
I think this has to do with blocked ports 4016 and 4018
I have an IIS installed on my machine. When I try to run my asp file, it gives me Active Server Pages error 'ASP 0221' The specified 'page aspcompat="true" ' option is unknown or invalid.
I run the same app from visual studio 2005 and it works fine. I don't know why it is not running from IIS. I have to deploy this up in a remote server and run it from local.I have allowed active server pages to run on the IIS on web service extensions.
Other ASP websites seems to run fine except this website I am working now. I don't why it is complaining about this directive.
The reason is some old ODBC connection will not work if I remove this asp directive 'page aspcompat="true"
Please Help..
Thanks
I'm using visual studio 2012 and i have a windows form app. the iis express server is configured by default with visual studio 2012.
I have to publish my windows form app. For that, i have create a storege object on azure platform.
But when i try to publish the project using clickonce i have that issue :
Error 83 The Web server does not appear to have FrontPage Server Extensions installed. If FrontPage Server Extensions are installed, this error can occur because the _vti_bin virtual directory is not marked as executable. To correct this problem, run Internet Information Services Manager, select the Web server that has the problem, and then use the Check Server Extensions command.
Screen shot :
https://docs.google.com/file/d/0B-aV0dsLT4CaemZuQV93Ymt4UVE/edit?usp=sharing
I had no issue during the creation of my storage object on azure, and the URL is good !
I have installed de FrontPage Server Extension several times and normally it's good.
i really need to publish my project, if someone can help me ...
Thanks for help.
You are trying to do HTTP publish to a server that doesn't have FPSE installed. FPSE was no longer available after Server 2008 (I'm guessing here, I just know it's not available for newer versions of Windows Server).
Instead of doing HTTP, use FTP. So you FTP the files to the web server, and use an HTTP link for the customer to access them.
For example, your publishing file location might be
ftp://myserver.com/myfolder/
and your installation URL would be something like
http://myserver/thefolder/
I am running the OpenIDRelyingPartyWebForms sample from the DotNetOpenAuth release.
I have VS 10, IIS 7.5, Windows 7.
When I run the project using the development server, it works fine and I navigate to the OpenId login page. It works with both F5 and Ctrl F5,
When I add the project as an application inside IIS 7.5, I get the "No OpenID endpoint found" error.
Any ideas?
Where are the VS development server settings stored so I can compare them?
Is the IIS 7.5 server the same as your dev box or is it a different box? Usually firewalls are to blame for this.
Perhaps the best way to diagnose it is to enable verbose logging and see if DNOA tells you more about why it is failing.
Ive programmed an Xbap Application and published it to Windows XP computer without any problem. Now I want to publish the Xbap application to a Computer running Windows Server 2003. I do'nt get any failure when I´m publish the application, but when I try to browse the application I got failure and I cant browse the application.
When i try to run http://localhost/MyApp/setup.exe, It says that the file could not be found...
I there someting else I have to do when publish to a Windows Server 2003 Computer compared to Windows XP
Its seems like the problem here was the MIME Types in IIS. By register the followign MIME Types in IIS solved my problem:
.manifest application/manifest
.xaml application/xaml+xml
.application application/x-ms-application
.xbap application/x-ms-xbap
.deploy application/octet-stream
.xps application/vnd.ms-xpsdocument
For more information how to do this, see:
http://msdn.microsoft.com/en-us/library/ms752346.aspx#content_expiration
List item