|
Giomanach -> RE: FPSE not working on IIS (3/17/2004 7:35:51)
|
Lets see if I can explain this in plain english: quote:
quote:
quote: FrontPage Run-Time Component Page You have submitted a form or followed a link to a page that requires a web server and the FrontPage Server Extensions to function properly. This form or other FrontPage component will work correctly if you publish this web to a web server that has the FrontPage Server Extensions installed. Click the <Back> arrow to return to the previous page. Generally means no FPSEs installed at all. It might also mean that they are corrupt quote:
I have installed both at the same time using the add/remove windows components in the control panel. MS recommendations for installing IIS and the like is like so: 1. Install your favourite WYSIWYG editor, and of course they recommend FP 2. Enable DNS Name Resolution (Can be found through Help And Support) 3. Run a full install of IIS from the Add/Remove Windows Components control panel It's all well and good doing it that way, but if you have other web server related software installed first, there is a chance that it will prevent IIS from running. E.G. You can't have Apache Web Server and IIS installed and running at the same time as they automatically listen on the same port. Option 1: Remove all other web server related software completely, then re-install IIS quote:
I have xitami installed but not running, and anyway IIS itself is running well Xitami???? Never heard of it. Is it running through the IIS snap-in or through the Services Console. ALso check in the process section of Windows Task Manager for inetinfo.exe and see if it's there. quote:
Yes i have the the IIS Snap-in In the Computer Management console. That's a good sign quote:
I haven't set up DNS Name Resolution on the PC. Recommended but not needed. I wouldn't enable it at the mo quote:
And i run the pages from http://localIP of the pc. Local IP??? it can be any of the following: http://127.0.0.1 (Localhost) http://192.168.XXX.XXX (For Workgroups) http://144.177.XXX.XXX (Not all domains, but generally) http://169.254.XXX.XXX (Automatic Private Address) They are just a select few. Make sure you enter http://localhost/ Option 2: Last Resort - Backup all info on the PC, and reformat it. Then install FP, then IIS. See if it works then HTH Dan
|
|
|
|