I have a Windows 7 virtual machine that has ColdFusion 9 installed for development and testing. I need ColdFusion 10 and 11 as well for other projects.
ColdFusion 9 is running perfectly, but when I spin up ColdFusion 10 or 11 and try to use WSCONFIG to configure a site in IIS, I get the following list of sites:
https://www.dropbox.com/s/v7mdgha536shk9t/Screenshot%202015-05-21%2023.29.14.png?dl=0
In reality each site in IIS has a separate name and when I delete a the site that each one is named after, in this case "cfadmin", all of the remaining sites show up in WSCONFIG as another one of the site names.
I have never had this problem before. Can anyone point me in the right direction?
Update:
As suggested in the comments, here are the results when I launched a command prompt as Administrator and ran the suggested command:
C:\Users>%windir%\system32\inetsrv\appcmd list sites SITE "cfadmin"
(id:3,bindings:,state:Unknown) SITE "mccalmon"
(id:1,bindings:http/:80:,state:Unknown) SITE "Virtus"
(id:5,bindings:,state:Unknown) SITE "EMSA"
(id:9,bindings:,state:Unknown) SITE "Classic"
(id:10,bindings:,state:Unknown) SITE "Test"
(id:2,bindings:http/:80:local.test.com,state:Unknown)
All of your site "state" are "Unknown". The problem seems to be with your sites only. If appcmd is not able to identify the correct state, then, ColdFusion will definitely not be able to recognize the same. The sites state would be unknown, if the IIS Server is stopped/shut down.
For e.g, my server shows the below information with the "%windir%\system32\inetsrv\appcmd list sites" command.
SITE "Default Web Site" (id:1,bindings:http/*:80:,state:Started)
SITE "CF9" (id:2,bindings:http/*:81:,state:Started)
SITE "CF10" (id:3,bindings:http/*:82:,state:Stoped)
SITE "CF11" (id:3,bindings:http/*:83:,state:Started)
You can try IISRESET in command prompt to restart IIS. Then, launch the Web Server Config tool as administrator and create the connector.
Related
I have Microsoft Windows server 2008 R2 and have the IIS 7 running.
I have coded a web application on a seperate laptop and would like to publish it now on my server (serves as AD, DNS, File Server, IIS) that runs locally and has no external access. We will be using the application internally only.
I have followed the steps to install a website on IIS, however, it does not work. Below are the steps I have done.
Created a folder hierarchy and pasted the code files there. (check below image. The code files are inside wwwroot)
Create a new website from the IIS Manager as the below image.
The wwwroot folder has SYSTEM permission and it inherits the permissions from the parent. (Does it need to have other permissions?!?)
Whenever I visit the website, I get an error that the page is not found.
UPDATE
Upon #Ravi A's answer below, I have tried his steps as the below image, but the username is not found and the error persists.
Any ideas what is wrong?
windows iis website
You need to add a binding in your DNS i.e. ping mysite.local should resolve to the server IP, in your case since it's a intranet it should resolve to 192.168.1.253.
See here on how to do it. You need access to DNS Manager.
Also since you are not clear on DNS mapping leave the hostname empty and use machine name or IP to browse the site.
In Windows 10 IIS and Xampp use the same port (80), I've learned. I know how to change port in Xampp, but I'd prefere to stop IIS while using Xampp. On my old computer with Windows 10 I went to task manager > services and stopped World Wide Web Services by rightclicking. On my new computer with Windows 10, I can't seem to find World wide web services on that spot. Can it be named something else, according to language (swedish - though before on the old computer it was named as mentioned)? Any other way (in simple steps, please - beginner!) to stop IIS using the port, without disabling the IIS alltogether? (might want to learn how to use it later on)
Thanks in advance!
Port 80 is used by default with many web servers (here IIS and Apache which is bundled inside XAMPP).
The default web site created with IIS uses port 80. If you don't want to use this default web site (absolutely no harm and no data loss!), you can delete it by running the following command in inetsrv directory (path would generally be C:\Windows\System32\inetsrv).
appcmd delete site "Default Web Site"
Or you can change the port for the default web site in IIS, with:
appcmd set site /site.name: "Default Web Site" /+bindings.protocol='http',bindingInformation='*:8000:']
appcmd set site /site.name: "Default Web Site" /-bindings.protocol='http',bindingInformation='*:80:']
(8000) is for instance, use any high number you like.
Server: Windows Server 2008 R2 Standard SP 1 - 64bit
IIS: 7.5
3 websites hosted from these locations:
D:\WebApplications\TestAccessManager
D:\WebApplications\dg
D:\WebApplications\TestVM
All Application Pools are up and running, and have been restarted.
All Sites are up and running, and have been restarted. (a total of 7 sites, just don't need to list everything).
The "default website" points to \TestVM and has no DNS name, it is only accessed by IP address.
The second site test.accessmanager.com, and the third site test.dg.com.
6 of the 7 sites are inaccessible. The one that can be accessed, the default website, is accessed by IP.
Now, how this all started.
Yesterday a user account was setup for me to access this server.
Another developer wanted to put a secondary site as a sub-site within default website, so the files were all dropped into a child folder: TestVM\subsite\. However, because the subsite has a web.config, I then created a Virtual Directory and pointed it to that sub folder. We then started having even more issues, so I right clicked on the Virtual Directory and hit "Remove".
Next, we were told that both dg and accessmanager were down. So I removed the \subsite\ folder completely to eliminate that from the equation... but to no avail.
Now, the kicker to all of this... is that the user account I had been given, apparently didn't have admin privileges... which would explain why certain folders would prompt "You don't currently have permission to access this folder. Click Continue to permanently get access to this folder".
One of our guys here says that without full authority, certain registry keys could have gotten messed up while working in IIS, and that he's seen it happen in the past, and never successfully had it fixed without just recreating all the virtual sites and "starting from scratch" in IIS.
Thoughts? Need more info? Anything?
I am trying for the past couple of days to configure IIS 7.5 and coldfusion to run on my local machine but I hit a wall.
I have two sites that I am trying to create a run locally but 1 of them is working and the other one does not.
My coldfusion admin is working and I was able to set up my settings (db connections and stuff).
Under IIS management I am creating a site, assign it to the correct folder on my machine set the path as "local.site1.com" and everything runs as it should.
When I am trying to do the same thing for Site2, I'm getting a message from Chrome saying "Oops! Google Chrome could not find local.site2.com"
Any recommendations will be greatly appreciated.
add local.site2.com to your hostfile
Are both sites pointing to the same codebase if so that is difficult to achieve with IIS7 and 7.5?
I've accidentally deleted the default website in IIS; It no longer shows up in the tree of IIS manager and browsing "localhost" returns a 404 error.
I've re-installed IIS, but the default website still doesn't exist... Is it possible to recreate the default website so I can create my folder inside?
Other answers are basically right, thanks to them I was able to restore my default web site, they're just missing some more or less important details.
This was the complete process to restore the Default Web Site in my case (IIS 7 on Windows 7 64bit):
open IIS Manager
right click Sites node under your machine in the Connections tree on the left side and click Add Website
enter "Default Web Site" as a Site name
set Application pool back to DefaultAppPool!
set Physical path to %SystemDrive%\inetpub\wwwroot
leave Binding and everything else as is
Possible issues:
If the newly created web site cannot be started with the following message:
Internet Information Services (IIS) Manager - The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
...it's possible that port 80 is already assigned to another application (Skype in my case :). You can change the binding port to e.g. 8080 by right clicking Default Web Site and selecting Edit Bindings... and Edit.... See Error 0x80070020 when you try to start a Web site in IIS 7.0 for details. Or you can just close the application sitting on the port 80, of course.
Some applications require Default Web Site to have the ID 1. In my case, it got ID 1 after recreation automatically. If it's not your case, see Re-create “default Website” in IIS after accidentally deleting. It's different for IIS 6 and 7.
Note: I had to recreate the Default Web Site, because I wasn't able to even open a project configured to run under IIS in Visual Studio. I had a solution with a couple of projects inside. One of the projects failed to load with the following error message:
The Web Application Project is configured to use IIS. The Web server 'http://localhost:8080/' could not be found.
After I have recreated the Default Web Site in IIS Manager, I was able to reload and open that specific project.
Did the same thing. Wasn't able to recreate Default Web Site directly - it kept complaining that the file already existed...
I fixed as follows:
Create a new web site called something else, eg. "Default", pointing to "C:\inetpub\wwwroot"
It should be created with ID 1 (at least mine was)
Rename the web site to "Default Web Site"
I suppose you want to publish and access your applications/websites from LAN; probably as virtual directories under the default website.The steps could vary depending on your IIS version, but basically it comes down to these steps:
Restore your "Default Website" Website :
create a new website
set "Default Website" as its name
In the Binding section (bottom panel), enter your local IP address in the "IP Address" edit.
Keep the "Host" edit empty
that's it: now whenever you type your local ip address in your browser, you will get the website you just added.
Now if you want to access any of your other webapplications/websites from LAN, just add a virtual application under your default website pointing to the directory containing your published application/website. Now you can type : http://yourLocalIPAddress/theNameOfYourApplication to access it from your LAN.
You can try to restore your previous state by doing the following:
Go to IIS Manager
Right-click on your Local Computer.
Point to All Tasks
Point to Backup/Restore Configuration
Select the configuration you want to restore
Wait untill configuration applies
Check out this answer on SuperUser:
In short: Reinstall both IIS and WAS.
In details -
Step 1
Go to "Add remove programs"
"Turn windows features on or off"
Remove both IIS and WAS (Windows Process Activation Service)
Restart the PC
Step 2
Go to "Add remove programs"
"Turn windows features on or off"
Turn on both IIS and WAS (Windows Process Activation Service)
Note: Reinstalling IIS alone won't help. You have to reinstall both IIS and WAS
This approach fixed the problem for me.
Follow these Steps
Restore your "Default Website" Website :
create a new website
set "Default Website" as its name
In the Binding section (bottom panel), enter your local IP address in the "IP Address" edit.
Keep the "Host" edit empty
I deleted the C:\inetpub folder and reinstalled IIS which recreated the default website and settings.