I had already published my site using the IIS Manager.
I successfully can access it with my PC but when my colleagues tried to access it, it says,
HTTP Runtime Error.
Is there something wrong in the config file? How come I can access it with no error? Can anyone help us with this?
http runtime error
Is not a lot to go by.
What do the windows event logs say?
What is the website, Asp.net or something else?
If it is asp.net, update this setting and post what error they see:
<?xml version="1.0"?>
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Related
I've created a new site within IIS and pointed to my local Documents directory
C:\Users\name\Documents
via
http://localhost:8080/
The error I'm getting is
HTTP Error 401.3 - Unauthorized
I've checked the properties of the Documents folder under Security. for IIS_IUSRS, Read & Execute, List folder contents and Read are checked.
Others like SYSTEM, myUsername, Administrators have more rights to this folder.
Not sure what I'm missing here, please advise.
Download Procmon from here and start tracing. Reproduce the issue and stop procmon.
Filter procmon trace for "access denied". It'll tell you what permissions are needed and for which folder.
Share a screenshot of procmon trace if you find it difficult to analyze and I will try and guide you.
"C:\Users\name\Documents" would typically be a terrible place to put a web site. It is essentially the same as "My Documents" which is a special Windows folder. And it would have a number of non-web site folders. Try using C:\Web (or something like that) and add IIS_IUSRS to that folder.
BUT, if you really want to use your My Documents as the root of a web site, you can create a web.config file in C:\Users\name\Documents with the following:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<authentication mode="None" />
</system.web>
</configuration>
I have to export a classic asp/asp.net 2.0 web site that uses also coldfusion 8, from Windows Server 2003 with IIS6 to Windows Server 2012 and IIS 8.
I got everything working except setting up coldfusion to work with IIS.
The pages using coldfusion have .cfm as an extension.
I tried to follow this link here but that did not work
http://www.adobe.com/devnet/coldfusion/articles/iis-configuration.html
When I try to add the handlers in IIS, I see a warning saying this site is in classic mode and I need to manage managed handlers directly in the config file.
I tried to add the handlers using appcmd like this:
appcmd set config /section:handlers /+[name='cfmHandler',path='*.cfm',verb='*',type='c:\coldfusion8\runtime\lib\wsconfig\jrun_iis6.dll',preCondition='integratedMode']
Then I added the Wildcard Script Map in IIS as per the link, this seems that it created and entry in the web.config of the site.
<system.webServer>
<handlers>
<add name="JWildCardHandler" path="*" verb="*" modules="IsapiModule" scriptProcessor="C:\ColdFusion8\runtime\lib\wsconfig\1\jrun_iis6_wildcard.dll" resourceType="File" requireAccess="None" preCondition="bitness32" />
</handlers>
</system.webServer>
When I try to browse to the web site, if the wildcard handler exists in the web.config, I get error 404 on any page, even the one that does not end with .cfm
I removed the wildcard and I now get the following error:
Handler "cfmHandler" has a bad module "ManagedPipelineHandler" in its module list
Most likely causes:
Managed handler is used; however, ASP.NET is not installed or is not installed completely.
There is a typographical error in the configuration for the handler module list.
During application initialization, either the application initialization feature has set skipManagedModules to true, or a rewrite rule is setting a URL that maps to a managed handler and is also setting SKIP_MANAGED_MODULES=1.
I tried to run the fix that some programmers mentioned in other questions, but did not help
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis -i
I tried to add the handler in the web.config instead of doing it through appcmd but I got the same error.
<add name="cfmHandler" path="*.cfm" verb="*" type="c:\coldfusion8\runtime\lib\wsconfig\jrun_iis6.dll" preCondition="classicMode" />
I have been trying to get this to work for the last 3 days without luck.
All I need get done is to make any page that ends with .cfm handled by the coldfusion server. It's obviously the web site is old .NET and probably classisMode. I could not find simple step by step instructions other than the link above which did not work for me.
Thank you in advance
My AngularJS makes RESTful API calls to my ApiController.
Everything works fine in localhost, but returns a boring and frustrating {"message":"An error has occurred."} when testing on IIS Server.
I have made sure these things are in place. There is a good post in here.
<system.webServer>
<httpErrors existingResponse="PassThrough" />
</system.webServer>
<system.web>
<customErrors mode="Off"/>
</system.web>
On the IIS7, I go to Error Pages >> Edit Feature Settings >> Error Responses is now Detailed errors.
How can we see the detailed exception? Have I missed something else?
I've implemented a sample app like the one here. It is a really basic app just to get things started. Everything works fine in IIS on my local machine, I've got it running on my IIS Express as well, but now come the tricky part. I do want to host this on AppHarbor, but I get 404 error. I've started a discussion on the support forum of AppHarbor, and they have taken a screen shot of the error when they run it.
It seems like it is something wrong with the routing since the StaticFile handler is used, but I'm just guessing. Does anyone have any suggestions?
Try and add
<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
</system.webServer>
to your web.config
I'm wondering how to remove the error messages IIS7 adds to the top of the page.
I have my own 500 and 404 error pages served.
Not needing the error pages I have deleted them, but I am still getting this on top of my page:
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable
Any ideas?
To prevent IIS7 hijacking your error pages, set existingResponse="PassThrough" in your httpErrors section in your web.config file. For example:
<configuration>
<system.webServer>
<httpErrors existingResponse="PassThrough" />
</system.webServer>
</configuration>
You can also go into IIS manager --> Error Pages then click on the right on "Edit feature settings..." And set the option to "Detailed errors" then it will be your application that process the error and not IIS.
Just for addtional information I'll share what helped me:
<system.webServer>
<httpErrors errorMode="DetailedLocalOnly">
</system.webServer>
In such setup I could see detailed errors when developing on my local machine, but they would not be shown to users when remote server is accessed from outside.
You could find more information regarding errorMode here.