i wrote a ASPX Webapplication and generally it works great. BUT since a few days i figured out one big annoying problem with the IIS 8.5!
You can log in and browse through all sites and subsites without any problem. But after a time (about 6 mins) or when i click on the CheckBoxList on the mainsite "Report" - here CheckBoxList Click - i get the Error:
"403 Forbidden - you don't have the permission to access the
/Report.aspx"
On the IIS i've tested so many security configurations and nothing worked fine. The Funny thing is - sometimes i have no problem with the Webapp for 1-2 weeks and than it started all again with the 403 Forbidden Error. Meanwhile i haven't changed anything.
Application Pool is everything fine. Folder permissions and Website permissions with the IIS_USR is configured with full access. Timeout is set on 30 mins.
I'm sorry i can't give you a link to test what i wrote because of company internal security.
Do you need any other Infos? Code elements? Settings from the IIS? Screenshots?
Hope you know what i'm looking for and thank you for any help!
I still didn't find the problem so i put the whole Website on a different Server and it works perfectly over there.
At the end i think it was/is a problem with the https certificate! So i changed the system from winserver 2012 and IIS 8.5 to winserver 2008 r2 with IIS 7 (if they cue in the same cert and we have the prob again i'll know it for sure).
I hope i have the chance to figure out what the problem on the old server was!
Thanks for every answer!
Related
I created a Windows Server 2008 virtual box with IIS7. I have two websites configured, one is my actual development site and the second is a test site to help troubleshoot this issue.
Website 1 (WS1) - the root of this website is on a drive which is mapped to my development machine (Mac Book Pro). The mapping seems to be working and I can access all files fine (W:\www\dev.frogquest.com).
Website 2 (WS2) - is a very simple website with one ColdFusion page just to prove that everything works. It's root is a local directory on the C:\ drive of the VB (C:\sites\localtestsite.com).
I've added host file entries for both sites (127.0.0.1 ...)
WS1 - Throws a Server error when I try to access it...
HTTP Error 500.19 - Internal Server error
The requested page cannot be accessed because the related configuration data for the page is invalid
Here's what I've tried so far...
Uninstalled both .NET 4.5 and URL Rewrite 2, rebooted, reinstalled .NET 4.5, rebooted, reinstalled URL Rewrite 2 Module… retried… FAIL! I took these actions because of information I found here...
HTTP Error 500.19 on IIS7 "Malformed XML" in web.config
Per the same article as above, I tried deleting the web.config file. Strangely, this had no impact, even after restarting the website, restarting the virtual box instance, etc... which I've done frequently btw just to rule that out.
I tried adding IIS_IUSRS to the WS1 directory, but because it's a mapped drive I didn't get a "Security" tab. So, this was fruitless. This was per this article...
IIS 7.0 Error - 500.19 Internal Server Error
I tried playing with the AppPool security, changing it from "pass-through authentication" to connecting as the administrator of the machine. When I clicked "Test Settings" I did get different results, but they didn't have any material affect in the actual server response. I have screenshots of the test setting results.
I copied the contents of WS1 into WS2 and this works! So, it has something to do with the fact that it's a mapped drive and very likely a permissioning issue in my opinion.
I am now out of ideas and in need of competent help and fresh ways of thinking about this!
UPDATE: Adding a screenshot of the actual error for more info...
IIS does not support any type of mapped drive,
https://support.microsoft.com/en-us/kb/257174
You will have to use the recommended workarounds, such as UNC paths.
I have created an site on Umbraco 7.1.6 it was working perfect in Visual studio 2012; when I deployed it to my hosting space I found a problem that it redirects me to login screen again and again just after some seconds. I have set keep user login to true and increased timeout but no improvement.
When I searched for that problem I found some links:
https://github.com/umbraco/Umbraco-CMS/compare/release-7.1.6...7.2.0
http://issues.umbraco.org/issue/U4-3845
https://github.com/Umbraco/Umbraco-CMS/commit/c936aaa51753862914591b753f7f2d7be7749cf7
First link provide me file but I do not know how to updated my current site.
In console I am getting an error.
GET http://example.com/umbraco/backoffice/UmbracoApi/Authentication/GetRemainingTimeoutSeconds 401 (Unauthorized) angular.min.js:106(anonymous function) angular.min.js:106o angular.min.js:102g angular.min.js:100i angular.min.js:79i angular.min.js:79(anonymous function) angular.min.js:80e.$eval angular.min.js:92e.$digest angular.min.js:90e.$apply angular.min.js:92safeApply umbraco.services.js:58(anonymous function) umbraco.services.js:6773(anonymous function) angular.min.js:108e angular.min.js:31(anonymous function)
I just experienced the exact same symptoms. A site ran just fine locally, using IIS Express, worked fine when deployed to Azure WebSites, but when I ran on a Windows Shared Hosting environment, the back office session would timeout somewhere between a couple seconds and a couple minutes.
I'd get a pop-up authentication window often but not always on the GetRemainingTimeoutSeconds url.
I filed a ticket, and the provider was able to replicate the issue. They said the site was running in full trust.
After enabling 32 bit application support - the issue is resolved.
Thanks to everyone, especially to #Morten Oc who commented.
It's properly something on the hosting. Have you tried other Umbraco installations on hosterpk? Also, try to set the login time (in webconfig) to 0.
I found out a solution that it was due to hosting environment (permissions), I deployed on client's hosting and it works perfectly.
Additionally if you do not have full trust hosting then it would not be able to maintain its session, you would have to configure session to managed in database.
For more info how to configure please refer to this post:
https://www.saotn.org/configure-sqlserver-sessionstate-for-umbraco/
I have tried all of the solution out there and have resolved nothing. It's a MVC 4 site on IIS 7 that I'm tryuing to get set up. Local browsing of the site won't display detail error information. Does anyone have any other suggestions?
So far I have done...
Checked MachineConfig for for .net 4 both 32 and 64 bit. It was not there so it shouldn't interfere.
Set customErrors mode="Off" in all config files.
Changed settings for DefaultErrorPages in the Site Settings to always display details.
Conducted an IISReset
Enabled failed request logging. Nothing was logged.
Checked the site error logs.=. Nothing indicated an error.
Checked Windows Logs. No errors logged under the IIS section.
Checked that the App Pool was running under .Net 4 and that it was set to integrated mode.
Turned off friendly errors in the setting for the browser
PS this is a production web server running Windows 2008R2 and IIS 7.0
I found the problem. One of the system admins had cloned the original production site intending for it to be used for the production beta, which was what I was setting up. Of course there was no communication as to what was needed to be kept in the copied site. Well it turns out there was a web.config in the original code that was doing a redirect to another location. Thus none of the new site configs were even being accessed. I removed all of the old code and it started working.
I have deployed an ASP.NET web forms application to IIS7 and getting status code 404 intermittently. By this I mean the site will work for say 10 mins, and then I will get status code 404 for 20 mins...
I have one other ASP.NET web forms app running as a separate website on the server, and is running with no problem. (Both are using the same application pool)
I have searched and seen a few people have had similar symptoms but their solutions have not worked for me. For example this guy was having a similar problem, I have tried their suggestions but no luck.
Diagnosing 404 errors on IIS 7 and ASP.NET MVC
Any suggestions would be much appreciated.
Problem turned out to be a DNS issue, there were two DNS records set for the subdomain. Hence the intermittent problem. There was a 50/50 chance which ip it got and cached.
I have a dev and prod Windows 2008 R2 servers with IIS7 and siteminder, which as far as I can tell are setup the same. Issue being the production websites work but the development ones do not.
Issue being that when I navigate to any dev website, it says "the page cannot be displayed because an internal server error has occured." I do not get a challenge in dev (which I believe is the cause of the issue), but I do in prod. This goes for classic ASP pages or ASP.NET pages.
Some findings :-
- IIS has Windows authentication enabled and all others disabled
- Windows Authentication Provider is Negotiate (tried Negotiate:Kerberos, same result)
- WindowsAuthentication and WindowsAuthenticationModule (Native) are both present in Modules
- WindowsAuthentication is installed under Server Manager -> IIS -> Roles
- Upon receipt of the above error message, IIS logs shows the access with error 401 2 5
All the solutions I found online either do not have the right setup as I do above, or suggests I disable Windows authentication and enable Anonymous Authentication. If I do so, all works fine but the only issue being my websites require Windows authentication to identify the user. I'm at my wit's end and am just short of reinstalling something in hope it works. Any possibilities or log files that I have overlooked?
After screwing around a bit I finally solved my problem ... hope this helps someone.
I realized in fact ASP pages were working but ASP.NET pages were not working
When I had turned on Anonymous Authentication, the ASP.NET pages were now giving 500 0 or 500 19 errors in IIS logs, instead of 401 2 5 with Windows Authentication
I tried to launch a ASP.NET page from within the localhost and got then 500 error with a more detailed error saying I should use relative path in httpErrors under web.config (??)
At this point I realized I had earlier changed the 403 error to a custom file at the default website level, then changed it back. Despite changing it back to it's previous value, What this ended up doing was adding a "remove" then an "add" tag, both for 403.htm, under httpErrors in the wwwroot/web.config. After I deleted the entire httpErrors segment, my websites started working again.
Reverting back to Windows Authentication at this point also worked.
So some take aways is to test websites locally first and keep in mind the existing of the wwwroot/web.config giving near untraceable errors ...