IIS Error after importing from IIS 7 to IIS 10 - iis-6

I have attempted to migrate sites from an old IIS 7 server onto a new IIS 10 server by using the following appcmd's:
Commands ran to export from IIS 7
appcmd list site /config /xml > "h:\temp\iis export\sites.xml"
appcmd list apppool /config /xml > "h:\temp\iis export\apppools.xml"
Commands ran to import to IIS 10
appcmd add apppool /in < "h:\temp\iis export\apppools.xml
appcmd add site /in < "h:\temp\iis export\sites.xml"
This ran without errors, and the new IIS 10 listed all of the old sites. The configuration files were also altered to reflect a change in file paths and local IPs which were updated without problems.
The problem is that whenever I select a site within IIS, and go to any of the properties (in the below example logging), it throws an error stating that it cannot find the file path for the web.config.
The file path is correct, but there appears to be a \\?\ prepended to the file path. I don't know if this is the reason why this error is occurring, nor how to correct this.
Any suggestions would be grateful! Thanks, Radderz

In this instance it turned out to be that he URL rewriting module for IIS was not installed.
Annoyingly the error message produced for if a configuration file contains an element that is not installed is simply that it cannot read the config file, rather than which tag was the cause.

Related

WAMP Server 3.0.0 cannot open apache conf file

I've re-installed WAMP in order to put it into a different directory. This was mainly so everything is automatically backed up.
Mysql starts ok, but apache fails with the following message from the event viewer:
The Apache service named reported the following error:
httpd.exe: Could not open configuration file bin/conf/httpd.conf: The system cannot find the path specified. .
This file is in the correct place (C:\googledrive\wamp64\bin\apache\apache2.4.17\conf) and there isn't any other stray httpd.conf files that it might be picking up on the path or anywhere.
Any ideas?
This turned out to be a permissions problem. It seems that the system account didn't have access to the directory containing the config file, but I guess must have had enough access to start up Apache and give that helpful (not) message!

IIS is not allowing to access a javascript file

i have a web application. while running in my system integration environment, i get an issue while accessing my javascript file or an image file in my particular folder.
When i tried putting the complete URL in the browser, it gave me a following exception -
HTTP Error 404.2 Not Found
The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the webserver.
I googled this exception and found that i need to allow ASP.NET 4.0, 2.0, etc in the IIS's ISAPI & CGi Restrictions.. however, they were already in allow mode.
What next should i lookup?
OK,, i got the answer
the HTTP Handler in the applicatin's web.config file was trying to execute via a aspnet_isapi.dll located in Framework64 folder of .NET Framework.. the target machine however is a 32 bit and i dont have this Framework64 folder on it..
i changed the path of the executable to point to the 32 bit's folder and it wrked :)

IIS6 Virtual directory not using assigned folder

I have an IIS 6 instance with a web site that has a few virtual directories. One of those was re-assigned to a new path but the webserver still serves from the old path.
I've restarted IIS. Is there some other setting that might cause IIS to hold on to the old reference?
I found a fix by editing the metabase.xml file to remove the old virtual directory entry:
Stop IIS
Edit metabase.xml
Start IIS

cannot see apache tomcat homepage

I installed apache tomcat and started the service by double clicking on apache-tomcat-8.0.9\bin\startup.bat file, the survice started successfully in 547ms, later I tried opening the homepage of tomacat by entering
localhost:8080 in my cleint
,all I could see is
HTTP Status 500 - java.lang.IllegalStateException: No output folder
with a message java.lang.IllegalStateException: No output folder.
If i don't mention the output folder, am I not supposed to see the homepage of tomcat ?
also I did stop the service by double clicking on
apache-tomcat-8.0.9\bin\startup.ba file, then I started the service using eclipse then tried opening in my client, then I got a 404 error.
I have no clue where am I going wrong, please give me some suggestions so that i can solve this, also what is the root folder of tomcat in order to put my project folder ?
You need to give appropriate rights to the subfolders of the Tomcat directory. In your case 'temp' and 'work', so the servercan store temporary files and precompiled Jsp.

IIS 6 localhost works but nothing else does

If I type localost in IE, it yields "It works!" but I can't seem to locate where exactly that page is picked from.
In c:\InetPub\wwwroot\ nothing exists that points "It works!" page.
I created a test folder inside wwwroot above. I put an aspx file there, it does not work (no file found), then i created a test.htm file, that can not be accessed through localhost/test/test.htm
Anyone knows what is wrong. I never ran IIS on this particular system. I have Windows XP Pro, and IIS6 is installed.
Please help.
I think it will answer it myself. There were two confusion first of all, IIS 5.1 was installed along with IIS 6 (there was a link in Administrative tools) and Apache server as well. Something was probably messing with it before I came. I uninstalled Apache, IIS 6 link (was not supposed to be there in the first place), and even IIS. Fresh installed fixed everything.
Also if you are running into problem like this, get familiar with IIS, how it works. It runs out of Virtual folders and you have to turn these virtual folders into Applications. It is tricky the way Microsoft do it.
In my case probably both the server were using the default port 80 (I am not sure though). I now have both servers intalled (IIS + Apache), with Apache using port 8080.
To test situation like this, do this: create a virtual folder in IIS 5.1, right click on it and turn that folder into application. Put an aspx file in the "actual" location that this virtual folder points to see and then open it in browser using localhost\virtualfolder\myaspx.file. Note that in many case IIS will not pick the default.aspx file automaticaly unless explicity given.