Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 13 years ago.
Improve this question
I have a problem accessing an intranet website with IE8. I can access the site through Firefox or any other browser, except IE. IE will prompt for a username and password but never accepts the credentials and just shows a 401 message, "You are not authorized to view this page"
The website is configured as follows:
Windows Server 2003
IIS Directory Security > Authentication Methods > "Integrated Windows authentication" only
Any ideas?
Sounds like an IE security setting. I'd check two things in options:
In the Advanced tab, in the security section, is Enable Integrated Windows Authentication checked?
In the Security tab, does the site come up under the Local Intranet zone? If not, add it. Also, make sure the User Authentication item under custom settings is set to one of the Automatic Logon options (checking Automatic Logon with current user name and password should make the browser automatically log into the site).
A good place to start when troubleshooting 401 errors in IIS is this Microsoft guide
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
Closed 8 years ago.
Improve this question
My .asp page is in the folder named "MyWeb", and "MyWeb" folder is under wwwroot folder which is under inetpub. I also added MIME types in IIS Manager for .asp as application/asp, and for .aspx as application/aspx I tried it a long but still it is not working. When I go to open that .asp file it is asking for download in IE browser and displaying a blank page in Mozilla Firefox. Please can any body tell me how to solve this issue?
ANSWER=
Issue solved I just changed the setting in IIS Manager set Enable Parent Paths to true and Send Errors To Browser to true and it happened. Localhost Home Page of IIS was displayed and my asp scripts are also running.
It possible that you haven't got Classic ASP support installed in IIS. To do this in Windows 7 follow the steps below;
How to enable Classic ASP support on IIS for Windows 7
Installing Classic ASP support
Goto Control Panel -> Programs and Features
Select from the left navigation bar
From the Windows Features dialog expand Internet Information Services -> World Wide Web Services -> Application Development Features and tick the option ASP this will also tick ISAPI Extensions if not already ticked (see image).
Configuring IIS Web for Classic ASP
Open Administrative Tools -> Internet Information Services (IIS) Manager and select the website you wish to configure.
In Features View under the IIS section select Handler Mappings check the existing mappings list that appears for a handler that points to *.asp if one doesn't exist select Add Script Map from the right hand navigation bar.
Fill in the options as per the below image
IMPORTANT If using 64-bit and want to enable 32-bit support you may wish to use the 32 bit equivalent ISAPI DLL. See Dee's answer to How to enable ASP classic in IIS7.5
Select the Request Restrictions button to open Request Restrictions dialog. The three images below detail the values that should be configured if not already set.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I get this error
The website declined to show this webpage
on my webserver when visiting
http://localhost/exampledomain.com/
I enabled failed request tracing rules for ASP, ASP.NET, ISAPI Extention and WWW Server for 403 status codes but no log files are created at C:\inetpub\logs\FailedReqLogFiles
Is this a firewall issue or something?
Your question lack a lot of information. But a quick search on Google reveals a lot of links with a possible
solutions.
https://forums.iis.net/t/1214595.aspx?403+The+website+declined+to+show+this+webpage
https://forums.asp.net/t/1640590.aspx?Web+Hosting+in+IIS+Error+HPPT+403+Forbidden+The+website+declined+to+show+this+webpage
https://social.technet.microsoft.com/Forums/Azure/en-US/9f18f483-3e3f-4591-b028-9f8c4e1efb10/website-declined-to-show-this-webpage?forum=sharepointadminlegacy
https://www.experts-exchange.com/questions/24446761/The-website-declined-to-show-this-webpage-IIS6-Web-Service.html
https://rehmangul.wordpress.com/2009/04/09/error-the-website-declined-to-show-this-web-pagethe-website-requires-you-to-log-in/
http://www.kb.blackbaud.com/articles/Article/48462
Or a list with links found on StackOverflow alone, which could have some useful information.
IIS7 403 - Access Denied
Why do i get this error: "The website declined to show this webpage"
IIS 7.5 - 403 Forbidden
IIS 7.0 Deployment issue
SQL Server Reporting Services - http 403 forbidden - website declined to show this webpage
But the most common causes for this error seem to be the issues mentioned below. Most links mention one or more of these as a possible solution.
Incorrect framework version
Early exception in your Application_Start
Incorrect MVC version installed
Permission error on files/folders or AppPool
Framework not correctly registered > run aspnet_regiis -ir
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
Hi All,
Actually I have a web application build using classic asp and vb script, along with MS-Access 2003 hosted on IIS 6.0. It is running fine.
Now I have shifted it to on IIS 7.0 and database MS-Access 2003 to 2010.
The Login Page is running fine, and also it's easily get login when I try to login. But after login when I try to access some others pages through click a button, it shows error 500 Internal Server Error.
I have given security this application to the everyone level but still it is showing error.
I am using database through DSN. I can not say that there is any DSN configuration error or mistake I did, because login page is working fine which gets user id and password from my database.
What type of issue might be there?
solved. Now I have given my Intepub\mailroot\pickup forder to appropriate permission.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
We have just started to use Windows Server 2008 R2 and IIS7.5 and I'm trying to move some existing sites across from our Windows 2003 box. I can get the sites running ok but am getting 401 errors for all the CSS / Images in the sites. Granting Everyone read access will solve this - but I'm not very happy doing this.
I've read that IIS7.5 makes use of a magical new 'account' and each Application Pool has its own account.
So far I have
Created a new folder in wwwroot for my website (kbank)
Copied the files in from another machine
In IIS7 created a new website (not virtual directory), this created a new Application Pool with the same name as my website. This is an Integrated Pipeline pool
In Process Model / Identity this is using ApplicationPoolIdentity and Load User Profile is set to True
Granted IIS AppPool\kbank read access to the root of the folder
Can anyone tell me how best to set up my websites.
2008 R2 IIS 7.5
Just as an FYI. After rebuilding servers and spending endless hours troubleshooting a 401.3 error after changing the AppPool identity to a domain account, we came to find out that a GPO was killing IIS. Make sure you test with a server in the "Computer" container and that no GPO's are changing restricted groups outside of Administrators.
In our case, NT Authority\Authenticated Users was removed from the local USERS group and it broke IIS complete.
Maybe you are just missing a small step. When you granted the account read access, did you check that it replaced settings in all subdirectories. Also it may require an IIS reset after changing the access rights.
I would check what is the exact status code of the 401 error IIS 7 Status Code
Once you know the exact error code, it will be easy for to troubleshoot the exact issue is.
I would also run Process Monitor and see if there are any "ACCESS DENIED" using the Filter.
Regards,
Vivek.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 14 years ago.
Improve this question
I have an .asmx in a folder in my application and I keep getting a 401 trying to access it.
I have double and triple checked the setting including the directory security settings. It allows anonymous. I turned off Windows Authentication.
If I delete the application and the folder its in, then redeploy it under the same application name it magically reapplies the old settings.
If I deploy the exact same application to a different folder on the server and create another application under a new name and set up the directory security setting again it works!!!
How do I get IIS to forget the setting under the original application name?
After deleting the first application in IIS and its associated files on the disk, try restarting IIS (or your server if possible). Then come back and recreate the whole setup.
Eventually I got it working again. By deploying to a different folder and recreating the virtual folder / application to it.
I am not sure how that makes a difference but at least things are working again.
I ran into a similar situation with asp.net pages. I had Anonymous on and Integrated off for a virtual directory, but one page was the opposite. Everything worked fine until I went to the one special page, then my post backs stopped working and I couldn't log out of the site until I deployed to a new virtual directory.
My eventual solution was to enable anonymous and integrated for the entire site and just turn off anonymous on that one page.