My laptop died and I had to set up everything afresh on a new one. Everything has gone smoothly till I tried to browse a website I had running on the old laptop. The home page loaded fine and database and everything connected. However, when I browsed to a page that required a login and would normally redirect me to the login page, the following error occurred:
HTTP Error 404.0 - Not Found The resource you are looking for has been
removed, had its name changed, or is temporarily unavailable.
Requested URL http://zbay_sys:80/jakarta/isapi_redirect.dll
Physical Path
C:\inetpub\wwwroot\zbay_sys\jakarta\isapi_redirect.dll
I was running CF9 on the old laptop, but thought I might as well upgrade to CF11 in the process.
So, I'm running ColdFusion 11 on IIS Windows 10.
I used Web Platform Installer to install ISAPI redirect module.
I only have a basic knowledge of IIS and ISAPI stuff and am struggling to debug this.
There is no Jakarta virtual directory. Should this have been created automatically?
Manually adding the jakarta virtual directory fixed the issue
Related
I am trying to become familiar with IIS using WIndows Server 2012R2. I started by trying to move the default Website from C:\inetpub\wwwroot to C:\sample. In the Website Advanced Settings I modified the Physical Path, restarted IIS and cleared the browser cache (Chrome). However, when I try to bring up the website again http://127.0.0.1/ I get this error:
HTTP Error 404.3 - Not Found
It worked fine before I moved the website location. Is there something else I need to do? Thanks for any guidance.
BACKGROUND
We are upgrading an umbraco 4.5.2 site running on Win2k8r2 / IIS7.5, SQL2k8r2 to umbraco 4.11.10. Given the number of steps required to perform the upgrade, we chose to do it offline and then replace production with the updated db and file system.
We did an offline upgrade to bring it up to 4.11.10 (4.5.2 -> 4.6.1 -> 4.7.2 -> 4.8.1 -> 4.9.1 -> 4.11.10). These upgrades affected the database and the filesystem.
The old system has 14 domains resolving to the 1 umbraco site. The domains are just aliases and per requirements are not set up with redirects from 13 of the domains to a master - instead, each domain serves the same content - just with a different host.
The 14 host headers are defined in IIS. They are also defined in umbraco under:
Content (folder)
EN (language folder)
Home (Hostnames are defined here)
Top Level 1 (also a child of EN)
Top Level 2 (also a child of EN)
PROBLEM
When we test under localhost (which is defined in IIS but not as a hostname in umbraco), the site renders content as expected. However, when we test with one of the hosts defined in IIS and in umbraco host names (after setting it up to resolve to 127.0.0.1 in hosts file), we are able to get to the home page but all other pages result in a 404.
The home page and preview pages render fine and the content editor and other backend admin features work fine. However, the "nice url" pages do not render and get 404 errors.
WHAT I'VE TRIED
I have deleted app_data\umbraco.config and republished the entire site.
Create a new website in IIS. Still get the 404 on pages other than site root.
Looked in umbracoLog table. Didn't see anything about 404s or anything that looked unusual in relation to before/after upgrade but I'm not an umbracoLog expert.
Is it necessary to do a clean install of 4.11.10 to install prerequisites that I may be missing? If so, what are these prerequisites and can they be installed independent of 4.11.10 install?
I'm at a loss as to what might be causing the issue. Any help would be appreciated.
A combination of items fixed the problem.
The main problem was having the hostnames defined in umbraco under the Home node. I removed the hostnames defined in umbraco at the Host node. Hostnames still exist in IIS.
In config\umbracoSettings.config
Set <useDomainPrefixes> to false
Set <addTrailingSlash> to false
In web.config set umbracoUseDirectoryUrls to true
Finally, fix a side-effect of removing the umbraco hostnames that causes requests for / to resolve to the EN node by adding the following to config\UrlRewriting.config
<add name="SiteRootHack"
virtualUrl="^~/$"
rewriteUrlParameter="ExcludeFromClientQueryString"
destinationUrl="~/home.aspx"
ignoreCase="true" />
There are several things you should check, but if you are getting Umbraco's 404 page and you can access the backoffice then that is a good sign at least!
The first thing to do is check Umbraco's logs at ~/app_data/logs/ to see what Umbraco is logging upon each request, if anything. Then check:
Have you installed MVC3 and 4 on the server?
Is the application running in a .Net 4 integrated app pool?
Have you applied "write" permissions to the correct folders?
Try removing any domain settings you have in the Umbraco backoffice, these are almost redundant if the site is a basic install.
If possible you should also create an Umbraco project from NuGet, this way everything you need with regards to DLLs dependencies are installed in the project. Also, there shouldn't be any need to upgrade in so many steps. It should be possible to upgrade from 4.5 to 4.7 then to 4.11 directly.
Finally, check the breaking changes in the Umbraco versions. For example, GetProperty("propertyName").Value returns a string in one version and then was changed to object in a latter version possibly 4.11, so this would obviously start causing NullReference exceptions which may be inadvertently be causing the 404's. It is unlikely you would be able to upgrade like this without having to make some code changes.
My client had to reinstall the whole server, so I redeployed my ASP.NET MVC app, but I can't browse it. I deployed successfully with the FTP and the website is in the proper local directory.
When I click the link (on the right panel of IIS) Browse crm on *:80, nothing happens. No error, no IE or Chrome opening, just nothing. I also tried to access the app by typing localhost or localhost/myapp (which should be the right path) directly in the web browser and I got
HTTP Error 404. The requested resource is not found
.
I did not install the IIS, but I did the configuration. Have I missed something?
Windows Server 2008 R2
All the roles previously activated have been activated
The MVC framework has been installed and SQL also.
Enabled the IIS tracing and it didn't trace anything
Make sure the application is running under the correct version of .NET. MVC applications targeting 4.0 running under a 2.0 application pool will return 404. Make sure the site binding is pointing at the correct directory of the application you just deployed. When all else fails, try putting a simple .html file into the site and accessing that through the browser. If that fails, it means that IIS is not set up to serve the site, so check bindings, application pools, and home directories.
I am trying to test using IIS as a load balancer for a Java application running on Tomcat. When I try to load the site in a browser after following the tutorial at this site, an IIS error page appears reading "HTTP Error 403.14 - Forbidden. The Web server is configured to not list the contents of this directory." I revisited every detail of the tutorial and haven't found any missteps.
The one big variation is that I'm using a Java application with Tomcat 5.5 bundled with it.
I simplified things by narrowing the workers down to the load balancer and one Tomcat instance/AJP worker.
I've consulted other tutorials and the Apache-provided documentation, which led me to move the isapi_redirect.dll, workers.properties, and uriworkermap.properties files into the Tomcat directories and move the isapi_redirect.properties settings into the registry (and adjust directory paths referenced in properties files and IIS to match). I continue to receive the 403.14 error. When I enable directory listing in IIS, the site loads a listing of the files in the bin directory.
The isapi_redirect log isn't being generated, so I believe the problem is in the IIS or isapi_redirect setup. What might I be missing that would lead to a 403.14 error?
I am using Windows Server 2008 R2, IIS 7.5, ISAPI_redirect 1.2.35, Tomcat 5.5.
I have copied parts of an old ASP website out into a new website. On my local machine where the code was cleaned up and tested the website works perfectly, however, on the Windows Server 2000 machine it needs to run on I am getting an error:
HTTP 403.1 Forbidden: Execute Access Forbidden
Internet Information Services
--------------------------------------------------------------------------------
Technical Information (for support personnel)
Background:
You have attempted to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed.
I have tried giving I_USR full control of the local web directory and selecting Scripts & Executables in IIS. All this has not changed anything.
In the end I tried doing an IIS re-install, but that has not solved the problem.
Any ideas where else I can look?
Check out this Support article and see if it helps with your problem.
While I do not say that your Windows 2000 server was upgraded from .Net 4, it smells like there is something not registered properly with ASP.