Installing IIS
Ryan D
http://74.208.153.34/
You can test it yourself and see that it works. However,
http://74.208.110.240 still does not work although it is configured the same.
Both of these servers are Win 2003 OS.
I tried to determine the differences between these two configurations. Here
is what I checked:
Both seem to have same Default Website and WpfApplication1
properties/permissions.
Both have the C:\inetpub\wwwroot\WpfApplication file shared.
All of the same services are running on both servers.
The only difference I saw was that in IIS Manager, 34 has a folder called
"aspnet_client". When I tried to reproduce this on 240, I did not see option
to create a new folder, just a new virtual directory. So I did this for
aspnet_client, but the icon looks different on 240 than 34, and the icon
doesn't look like a folder.
I also checked ipconfig /all, and the settings were the same. What else do
I need to check to setup IIS Manager properly for hostin my app on 240?
David Wang
> I copied index.html file to the following server and URL:http://74.208.153.34/
>
>
> Both of these servers are Win 2003 OS.
>
> I tried to determine the differences between these two configurations. Here
> is what I checked:
> Both seem to have same Default Website and WpfApplication1
> properties/permissions.
> Both have the C:\inetpub\wwwroot\WpfApplication file shared.
> All of the same services are running on both servers.
> The only difference I saw was that in IIS Manager, 34 has a folder called
> "aspnet_client". When I tried to reproduce this on 240, I did not see option
> to create a new folder, just a new virtual directory. So I did this for
> aspnet_client, but the icon looks different on 240 than 34, and the icon
> doesn't look like a folder.
>
> I also checked ipconfig /all, and the settings were the same. What else do
> I need to check to setup IIS Manager properly for hostin my app on 240?
Please define what exactly is "not working".
You need to define and know the dependencies of your app, and
configure them.
If you do not have these things, then you have no way to replicate
settings nor determine when something is working, which means your
whole server cloning process is a lost cause.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Dan
"Ryan D" <Ry...@discussions.microsoft.com> wrote in message
news:A782503F-E42A-4374...@microsoft.com...
> I copied index.html file to the following server and URL:
> http://74.208.153.34/
>
> You can test it yourself and see that it works. However,
> http://74.208.110.240 still does not work although it is configured the
> same.
>
> Both of these servers are Win 2003 OS.
Do you have your router/firewall configured correctly to allow incoming
connections on port 80, and for them to be routed to your IIS server? Did
you add the exclusion to allow this in the Windows 2003 firewall too?
Are you using host headers? If so, did you set the IP address for the host
header on the second server?
> I tried to determine the differences between these two configurations.
> Here
> is what I checked:
> Both seem to have same Default Website and WpfApplication1
> properties/permissions.
> Both have the C:\inetpub\wwwroot\WpfApplication file shared.
> All of the same services are running on both servers.
> The only difference I saw was that in IIS Manager, 34 has a folder called
> "aspnet_client". When I tried to reproduce this on 240, I did not see
> option
> to create a new folder, just a new virtual directory. So I did this for
> aspnet_client, but the icon looks different on 240 than 34, and the icon
> doesn't look like a folder.
That's because the aspnet_client folder is a special folder that is created
when you install ASP.NET on your server. You can't just create the folder
manually and expect it to be the same.
> I also checked ipconfig /all, and the settings were the same. What else
> do
> I need to check to setup IIS Manager properly for hostin my app on 240?
Does IIS work from a browser on the server itself? If so, then it's not an
IIS problem - it's a router/firewall configuration issue.
--
Dan
Ryan D
I have my firewall turned off, so this shouldn't affect any of the ports.
I tried to browse to my web page from IIS, and it returned the following
error:
Cannot find server or DNS Error
Internet Explorer
So I followed all of the recommended steps and my server was in compliance.
I also did an ipconfig and got the following output:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : S15357071
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Peer-Peer
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter vznet0:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SWsoft Virtual Network Adapter
Physical Address. . . . . . . . . : 00-FF-77-0D-E2-C9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 74.208.110.240
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.66.50
DNS Servers . . . . . . . . . . . : 74.208.8.251
195.20.224.234
195.20.224.99
C:\Documents and Settings\Administrator>
What would you suggest I try next?
Ryan D
"David Wang" wrote:
> .
>
Dan
> Good questions, Dan!
>
> I have my firewall turned off, so this shouldn't affect any of the ports.
I hope you're not running a publicly accessible server on the internet with
no firewall whatsoever, you should have at least a perimeter firewall system
in place to keep the unwanted junk out.
> I tried to browse to my web page from IIS, and it returned the following
> error:
> Cannot find server or DNS Error
> Internet Explorer
I don't understand - what does "browse to my web page from IIS" mean? IIS
itself doesn't have a browser.
What you need to do is run a web browser (eg Internet Explorer) on the
server running IIS, and go to
If that works, then it's a networking issue, IIS is working fine.
If it doesn't work, then it's possibly IIS issue - are you sure the site is
running (press the > button in IIS manager to start it)? What host headers
do you have configured for the site?
Does anything appear in the Windows event logs (Application, System, and
Security) that are related to IIS? It could be a permissions problem that is
preventing the site from running.
> So I followed all of the recommended steps and my server was in
> compliance.
What are these "recommended steps"?
> I also did an ipconfig and got the following output:
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : S15357071
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Peer-Peer
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter vznet0:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : SWsoft Virtual Network Adapter
> Physical Address. . . . . . . . . : 00-FF-77-0D-E2-C9
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 74.208.110.240
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.66.50
> DNS Servers . . . . . . . . . . . : 74.208.8.251
> 195.20.224.234
> 195.20.224.99
>
> C:\Documents and Settings\Administrator>
>
>
> What would you suggest I try next?
I'm a bit concerned that you have a public routable IP address on your
server, but your gateway is a private non-routable address. While this isn't
normally an issue (for instance on my own connection here the upstream
router has a private non-routable address on the interface we are connected
to), this might suggest a problem with the network configuration as normally
you would have the public IP address on a router or firewall appliance, and
use NAT or port forwarding to route connections to your server (which itself
would have a private non-routable IP address, normally in a separate network
segment than your internal network).
Dan
Ryan D
"Dan" wrote:
>
> "Ryan D" <Ry...@discussions.microsoft.com> wrote in message
> news:F7984BC0-4187-4A3B...@microsoft.com...
> > Good questions, Dan!
> >
> > I have my firewall turned off, so this shouldn't affect any of the ports.
>
> I hope you're not running a publicly accessible server on the internet with
> no firewall whatsoever, you should have at least a perimeter firewall system
> in place to keep the unwanted junk out.
>
> > I tried to browse to my web page from IIS, and it returned the following
> > error:
> > Cannot find server or DNS Error
> > Internet Explorer
>
> I don't understand - what does "browse to my web page from IIS" mean? IIS
> itself doesn't have a browser.
>
Browse to web page means when I click on the Browse button from IIS Manager.
> What you need to do is run a web browser (eg Internet Explorer) on the
> server running IIS, and go to
>
> http://74.208.110.240
>
I went to this IP address from my web server and it said Page cannot be
displayed.
I think I found the problem. The problem seems to be my ISAPI filters.
Cause after doing a IIS Manager/Browse, I checked the Application log and
here is what I found:
"Could not load all ISAPI filters for site/service. Therefore startup
aborted.
EventID: 2268"
"ISAPI Filter 'C:\Program Files (x86)\Common Files\Microsoft Shared\Web
Server Extensions\50\bin\fpexedll.dll' could not be loaded due to a
configuration problem. The current configuration only supports loading images
built for a AMD64 processor architecture. The data field contains the error
number. To learn more about this issue, including how to troubleshooting this
kind of processor architecture mismatch error
EventID: 2274"
Then I removed the X86/Web Server Extensions directory. After rerunning the
Browse command the Application log returned this new EventID instead of 2274:
"The HTTP Filter DLL C:\Program Files (x86)\Common Files\Microsoft
Shared\Web Server Extensions\50\bin\fpexedll.dll failed to load. The data is
the error.
EventID: 2214"
So then I checked for x64 Web Server Extensions, but it doesn't look like
Microsoft Downloads include this for the Win Server 2003 OS, cause the only
x64 extensions I found were for XP OS. And these were x86-based. This is
the file I am referring to:
fpse02_x64_ENG.exe
Which file do I need to download to install extensions for my OS?
No, I do not have any host headers configured on this web site. And yes I
am sure the site is running cause I can clearly see that the > is on and
started.
> If that works, then it's a networking issue, IIS is working fine.
>
> If it doesn't work, then it's possibly IIS issue - are you sure the site is
> running (press the > button in IIS manager to start it)? What host headers
> do you have configured for the site?
>
> Does anything appear in the Windows event logs (Application, System, and
> Security) that are related to IIS? It could be a permissions problem that is
> preventing the site from running.
>
>
> > So I followed all of the recommended steps and my server was in
> > compliance.
>
> What are these "recommended steps"?
The recommended steps are based on a Microsoft Windows help item describing
how to setup a website with IIS.
I agree with u, but this is only temporary until I can fix this problem. I
want to eliminate anything that might be blocking this.
Dan
"Ryan D" <Ry...@discussions.microsoft.com> wrote in message
news:3014518A-EB36-41E3...@microsoft.com...
> Dan, see answers below please.
>
> I think I found the problem. The problem seems to be my ISAPI filters.
> Cause after doing a IIS Manager/Browse, I checked the Application log and
> here is what I found:
>
> "Could not load all ISAPI filters for site/service. Therefore startup
> aborted.
> EventID: 2268"
So the site isn't actually running then, because startup was aborted.
> "ISAPI Filter 'C:\Program Files (x86)\Common Files\Microsoft Shared\Web
> Server Extensions\50\bin\fpexedll.dll' could not be loaded due to a
> configuration problem. The current configuration only supports loading
> images
> built for a AMD64 processor architecture. The data field contains the
> error
> number. To learn more about this issue, including how to troubleshooting
> this
> kind of processor architecture mismatch error
> EventID: 2274"
IIS is telling you that you cannot load a 32-bit DLL because you are running
in 64-bit mode. You have to run the site in 32-bit emulation mode. See
http://support.microsoft.com/kb/891314 for more details.
> Then I removed the X86/Web Server Extensions directory. After rerunning
> the
> Browse command the Application log returned this new EventID instead of
> 2274:
>
> "The HTTP Filter DLL C:\Program Files (x86)\Common Files\Microsoft
> Shared\Web Server Extensions\50\bin\fpexedll.dll failed to load. The data
> is
> the error.
> EventID: 2214"
You can't just remove the directory - you still have metabase references for
them.
> So then I checked for x64 Web Server Extensions, but it doesn't look like
> Microsoft Downloads include this for the Win Server 2003 OS, cause the
> only
> x64 extensions I found were for XP OS. And these were x86-based. This is
> the file I am referring to:
> fpse02_x64_ENG.exe
http://support.microsoft.com/kb/891314
That URL above says they are for Windows 2003, as well as XP, and that
article also says you have to run IIS in 32-bit emulation mode for them to
work - they're actually 32-bit DLLs, not 64-bit.
> Which file do I need to download to install extensions for my OS?
You already have the right file, you just haven't read the installation
instructions fully.
--
Dan
Ryan D
Thanks so much! I set my server to 32-bit mode. However, now I'm getting a
different error in Application Log when I Browse from IIS:
"Could not load all ISAPI filters for site/service. Therefore startup
aborted.
Event: 2268
\RpcProxy\RpcProxy.dll failed to load. The data is the error.
Event: 2214"
So how do I fix this error? I googled this problem but trying solutions
others suggested did not help fix this. When I Browse from IIS, it also give
me error in browse window:
Service Unavailable
"Dan" wrote:The HTTP
Filter DLL C:\WINDOWS\System32
> See answers inline below.
>
>
> "Ryan D" <Ry...@discussions.microsoft.com> wrote in message
> news:3014518A-EB36-41E3...@microsoft.com...
> > Dan, see answers below please.
> >
>
> > I think I found the problem. The problem seems to be my ISAPI filters.
> > Cause after doing a IIS Manager/Browse, I checked the Application log and
> > here is what I found:
> >
> > "Could not load all ISAPI filters for site/service. Therefore startup
> > aborted.
> > EventID: 2268"
>
> So the site isn't actually running then, because startup was aborted.
I c what you are saying--the site must not be running. But currently there
is not a way to make it run by pressing the > button since this button is
already pressed.
Dan
the IIS config from a server with Exchange installed on it? The only
reference to that DLL I can find is in relation to Exchange and enabling RPC
over HTTP. My own 2003 IIS server does not have any reference to that DLL.
What you might be able to do is remove it from the Web Service Extensions
node in IIS manager. It's beginning to sound like your IIS config is a
mess - you might be better off restoring the metabase to it's original
settings, assuming that you took a backup of the metabase before you started
changing any settings (I'd recommend always taking a backup whenever you
change anything in the IIS configuration).
Dan
"Ryan D" <Ry...@discussions.microsoft.com> wrote in message
news:FD27A941-C482-4A12...@microsoft.com...
Ryan D
trouble viewing my WPF form, I can now see index.html from this web server!