Why does the asp.net website administration tool give timeout message (mysql db)? - mysql

i have an asp.net-mvc website and I am trying to use the asp.net website administration tool but when i click in visual studio 2010 to launch it, it brings up a browser that says:
An error was encountered. Please return to the previous page and try again.
i can't click back but when i click on "How do i use this tool", i get this error:
Tool Has Timed Out
As a security measure, the Web Site Administration Tool times out after a period of inactivity. Changes to machine.config or web.config may also result in the tool needing to be restarted. To continue configuring your web site, restart the tool.
when i run my website, i am able to connect to the database fine and i am also able to insert new users through the default Account/LogOn interface.
Any suggestions on how to debug why i can't launch the admin tool ?

The project's path shouldn't contain #% or spaces

Could you please try the following:
Close your browser completely. Whether you are using IE or Firefox to test your website, you should make sure all browser windows are closed.
Kill the asp.net development server. It is located in your taskbar
Or, if you are hosting your site in IIS, force an iisreset.
Now try to run the Web Site Administration Tool again.
If it still does not work yet, could you please provide which browser you are using, and which OS and host?

The project's path shouldn't contain #% or spaces
My Project path was D:\Programming\C#\Tests\MVCApplication\
and that is what caused the problem.

I was getting the exact same error message with VS2010 .NET 4.0 framework. I created my solution in a subfolder titled "C#". Renaming the subfolder to CSharp fixed my problem.
I hope this helps.

Related

VS Code 2017 "Localhost refused to connect" HTML file

This is a simple index.Html file, when i click on run i get the attached screen.
I have included the Json configuration.
The previous posts did not resolve my issue, and i did restart the machine as well as running VS Code as an admin. VS Code Error
installed Extensions
This happening because of your firewall setting restriction. please
Try Live Server Extension AND check for Firewall Settings.
Plain HTML/CSS can be opened as a file, no need to run them through a web server.
And if these procedures didn't work tell me about your browser.

Headless Chrome fails under IIS but works on command line

I am wrapping headless chrome using the excellent ChromeHtmlToPDF library. This we are using to dynamically render PDFs from a website. This works locally under IIS express, and also works on the server when recompiled as a console app, so the technology works. However running under IIS, chrome always exits immediately and a error of "one or more parameters are invalid", is returned.
You can fix this by passing Chrome a custom user profile directory:
chrome.exe --user-data-dir="C:\NewChromeProfile" ...
This directory will be created by the account under which Chrome is running, and therefore the account will have the permissions it needs.
After many many hours looking into this I finally solved it by running it under my own user, the restricted IIS user, then comparing the activity logs generated by the excellent microsoft process monitor.
I tracked it down to file permissions on one directory: C:\Windows\System32\config\systemprofile\AppData\Local\Google\Chrome\User Data
The app pool user needs write + modify permissions to this directory. It's up to you if you feel this is an acceptable security risk; however for us it is, for now.
This is where headless chrome stores it's crashpad directory. No amount of parameter fiddling seems to be able to dissuade it of this. That seems to be a bug.
Hope this helps someone else, I couldn't find anything on this anywhere.

How do I force Azure Apps to use latest html file?

I have a web application hosted on azure apps that I publish using visual studio. It is a flask app. One of the templates is called searchresult.html. I am making changes to this file that are made when I run locally. When I run it on the server though the changes are absent.
Using the azure console I can see that the changes are present in the file that is stored on the server, but the application continues to deliver the old html.
How can I force azure to see my updated file?
Things I have tried:
Deleting the file directly on the server and re-publishing it
Committing changes to git, even though I knew that would do nothing
Testing it locally (it works)
Restarting the application
Since you said you already check the file has been changed on the Kudu, so it supposed not an issue of deployment. You could disable caching in your browser.
such as in chrome browser, navigate to F11 window and select the Disable cache blanket.
or please try to access your website via incognito model.
In addition, I crashed into similar issue with you in other web app. My previous solution is that enable always on option on the portal and restart my app, it worked.
Just for your reference.Hope it helps you.

Why am I getting this ISAPI error on a cloned site?

I'm a corporate developer and was recently tasked with copying a live website that is already up. It's step one of a project and this is meant to be a testing copy. Project spec requires the site be an exact clone of how the site appears now. This is all being done on IIS 8.
I copied the folder and set it up as its own website, but the "_dev" version. I changed nothing at all in the web.config and even used KDIFF3 when I started having issues to ensure everything I'd copied was a binary copy (It's a Winforms site). Any time I attempt to navigate to the page, I get a 500 error. The original site, in the same box on the same IIS, is still fine.
Naturally, I enabled failed request logging and it turned out to be this:
ModuleName
IsapiModule
Notification
EXECUTE_REQUEST_HANDLER
HttpStatus
500
HttpReason
Internal Server Error
HttpSubStatus
0
ErrorCode
The specified module could not be found.
(0x8007007e)
ConfigExceptionInfo
I don't use IIS much, but I'm pretty sure the only reference either the working site or the problem site has which involves ISAPI is a reference to the .Net 2.0 aspnet_filter in System32 for the .Net 2.0 framework.
Since the sites have identical content, which is very simple content, I thought it was permissions. For 20 minutes or so I gave r/w/x for "Everyone" with inheritance to child objects enabled, essentially ensuring permissions could be ruled out on the folders or on web.config, and still had the same issues.
I'm sort of at the end of my rope here. I can't find anything more than the steps above as a fix, but I'm in the same boat, even after restarting IIS. Both sites are using the same Application Pool (a 2.0 one, Classic mode) and are simple WebForms. Does anyone know why I'm having this issue?
Update: I also tried it locally on my desktop instead of on the web server. I can connect flawlessly to it via Localhost. I then installed a second on my desktop just by copying the folder and adding a page to IIS. That worked as well. Copying the working local install to the server still gives me a site that doesn't work.
The answer was a strange one. The previous developer working on the site was familiar with the AJAX tools from earlier versions of Visual Studio and had installed .Net 1.1 on the box to ensure compatibility with his code. IIS was defaulting new sites to point to the .Net 1.1 DLLs, while running in a .Net 2.0 app pool. Changing all of these manually to point to the 2.0 DLLs fixed the problem.

Localhost not loading in any browser

I have asked a similar question before here I sort of fixed it but im still facing a similar issue. Every time I try to load localhost, port 8095, I receive this error message in Google Chrome:
Google Chrome's connection attempt to localhost was rejected. The
website may be down, or your network may not be properly configured.
If there is a way to fix it, please tell me,
If not, please could someone inform me how to reset IIS to its original settings. Or if I can reset Windows Features so I can re-install ISS from scratch.
My website uses ASP with a connection to a SQL Server database (2012). Basic HTML pages also don't load under the URL, localhost:8095/
The servers were stopped because 2 services within administrative tools had stopped. World Wide Web Publishing Service and Web Management Service