XP Pro, FP2000 server mess (Full Version)

All Forums >> [Web Development] >> Server Issues



Message

cornerpocket -> XP Pro, FP2000 server mess (10/7/2002 0:19:08)

Starting a new large web project after a long time away from using FP. I have found I am unable to create a new web. I keep getting the error no web found at port 80.

I didn' t have this problem with Win98s. Have I shot myself in the foot upgrading to XP? Everything else seems to work real well.

Is it possible to create disk based web, if so, how do I go about it?




Doug G -> RE: XP Pro, FP2000 server mess (10/7/2002 0:30:10)

I don' t know if this helps, XP Pro includes IIS 5.1 but it' s not installed by default.

Open Control Panel - add remove programs - add remove windows components and install IIS. Be logged in as admin when you do this. Then after the obligatory reboot you should have a perfectly good web server on your local computer.



cornerpocket -> RE: XP Pro, FP2000 server mess (10/9/2002 22:54:51)

Doug,
Followed the above instucts (system did not request reboot). I rebooted anyway. Opened FP2000. Tried to reate a new Web. Got error message.
>>Front Page has detected a web server conflict at Port 80 which has server for the FP personal web server but is running a MS IIS/5.1 server. FP requires that you install FP server extensions on this new server. Would you like to see how to do this? Two options OK or Cancel. If I click on OK Get another box saying it can' t find fpnetwrk.hlp. Asks if I' d like to try to find it and I can' t. This is where I get hung up. Can you get me past this point?

Reg



storm -> RE: XP Pro, FP2000 server mess (10/10/2002 6:14:09)

don' t install the extensions through fp. go to add/remove programs in control panel, select windows programs, select IIS, detail and if extensions are not checked go a head and cselect them then ok, ok, etc... to complete the wizard.



cornerpocket -> RE: XP Pro, FP2000 server mess (10/10/2002 6:50:38)

Storm,
IIS does not show up in the program listing at Control Panel\Add/Remove

Reg



Doug G -> RE: XP Pro, FP2000 server mess (10/10/2002 18:32:53)

Did you go to add-remove windows components?



cornerpocket -> RE: XP Pro, FP2000 server mess (10/10/2002 22:36:39)

Yes, I used Add/Remove Windows components.



Doug G -> RE: XP Pro, FP2000 server mess (10/10/2002 23:24:36)

Well, if you were able to install IIS from Add/Remove Windows Components, and now IIS is not listed there, something is very wrong and I don' t know what it might be.

You need to be logged in as administrator when you install/uninstall/configure IIS. The error you got about a port conflict on port 80 would indicate another web server was installed on your computer. If you installed any FP web server or another web server, uninstall them then see about IIS configuration.

On my XP Pro, NTFS disk system, the only thing I did was install the IIS components from the CP - Add/Remove Programs, and that was it. FP2000 server extensions are installed as long as you didn' t uncheck the server extensions option. I was able to immediately connect via Frontpage and create a web.





cornerpocket -> RE: XP Pro, FP2000 server mess (10/11/2002 7:37:18)


Doug,
Since installing XP Pro about 6 months ago, I have been unable to create a new web in FP. This conflict at port 80 message was always the result.

Would the PS from Windows 98 and FP98 have remained on the system when I installed XP? Could XP have installed IIS at this point?

When I recently installed IIS, there was no request to shut down, could that mean IIS was already there so it didn' t install again?

How would I go about uninstalling all servers and then reinstalling IIS?

Reg



Doug G -> RE: XP Pro, FP2000 server mess (10/12/2002 0:32:01)

Reg-

If you had PWS from FP98 running prior to upgrading, yes I think it could still be there. Is there a start menu option to uninstall it?

In XP Pro you can open the TaskManager to view what processes are running. Also in Administrative Tools - Services, go down the list & see if you have a Personal Web Server service. The XP IIS5.1 shows up in the services list at or near the end as " World Wide Web Publishing Service"

You can also telnet to your web server. On my XP Pro you can open a command prompt window (DOS window) and type in:

telnet localhost 80

After a couple returns (Enter Key) I got this: 
HTTP/1.1 400 Bad Request
Server: Microsoft-IIS/5.1
Date: Fri, 11 Oct 2002 04:15:07 GMT
Content-Type: text/html
Content-Length: 87

<html><head><title>Error</title></head><body>The parameter is incorrect. </body>
</html>

Connection to host lost.



storm -> RE: XP Pro, FP2000 server mess (10/12/2002 6:34:12)

Are you saying you did an upgrade from 98 to XP and not a clean install?



cornerpocket -> RE: XP Pro, FP2000 server mess (10/12/2002 7:23:07)

Yes, I did an upgrade and now I' m paying for it.



storm -> RE: XP Pro, FP2000 server mess (10/12/2002 9:41:13)

my opinion....your never going to get this to run right. you' ve had enough headaches the last few days, do yourself a favor and start over with a clean install. you' ll be glad you did.



cornerpocket -> RE: XP Pro, FP2000 server mess (10/12/2002 18:22:11)


At this point, how would I go about accomplishing a clean install. I have two drives C: and E: E contains the bulk of my apps and data, will I need to format a drive to do a clean install and if so, can I do it on C and leave E intact?

Reg



Doug G -> RE: XP Pro, FP2000 server mess (10/12/2002 20:55:24)

Doing a clean reinstall is not a step to be taken lightly. Generally it requires backing up everything, copying down some important system settings, reformat & reinstall, reinstall all your software, copy the data back from backups, reconfigure everything, redo all the online updates you' ve done, etc.

If it was me and everything else is working right, I' d probably spend a little more time researching the web server problem. Maybe someone else can jump in with some tips, I' m out of ideas.

Did you try the telnet thingy? The goal is to see if your local web server identifies itself as IIS 5.1 or as something else.



cornerpocket -> RE: XP Pro, FP2000 server mess (10/12/2002 21:16:45)

Telnet is not a process I am familair with



Doug G -> RE: XP Pro, FP2000 server mess (10/12/2002 23:07:24)

Open a Command Prompt window (an easy way is click start - run and enter " cmd" in the window (without the quotes)

You should get an old DOS-looking window.

At the windows prompt enter the bold stuff below (username will be your username, not " username" :

c:\Documents and Settings\username> telnet localhost 80

You should get a blank screen with a blinking cursor at the top left. Hit enter a couple three times and if there is a web server running on port 80 you should get an error message back like the one I posted above (which is from my Windows XP box).

Then if the telnet doesn' t close after this test, try ctrl-c a few times, or ctrl-] then enter " quit"

the ctrl-whatever means hold the ctrl key down on your keyboard, and while holding ctrl just do a normal type of the " c" or the " ]" key. Then let up on everything.

If you get something that looks different than what I posted in the earlier message, you probably have a different web server running (like your old PWS) which is why you are getting a conflict. If that' s the case, you need to uninstall the old server, then install IIS from your XP CD.

You must be logged in to XP as an Administrator user when doing all this stuff.






cornerpocket -> RE: XP Pro, FP2000 server mess (10/12/2002 23:38:58)

Appears I got the same thing:



HTTP/1.1 400 Bad Request
Server: Microsoft-IIS/5.1
Date: Sat, 12 Oct 2002 03:10:23 GMT
Content-Type: text/html
Content-Length: 87

<html><head><title>Error</title></head><body>The parameter is incorrect. </body>
</html>

Connection to host lost.

Couldn' t find a listing in Task Manager and I' m not sure where to find:

[font=" " ]
quote:

Also in Administrative Tools - Services, go down the list & see if you have a Personal Web Server service. The XP IIS5.1 shows up in the services list at or near the end as " World Wide Web Publishing Service"







bhiggs -> RE: XP Pro, FP2000 server mess (6/17/2004 17:28:01)

I had this problem, too. The problem has nothing to do with upgrading operating systems; it has to do with the fact that you had FrontPage Personal Web Server previously installed, and configured to use port 80, and then you installed IIS, also to use port 80.

I had exactly the same experience as you: the critical piece was the fpnetwrk.hlp file, which FrontPage couldn't find. However, I said I would try to find it, and it was there on my system. When I looked at that help file, it told me exactly what to do to fix the problem. It has a section entitled 'Resolving Web Server Conflicts on Port 80', and when I went to that section, here's what it said:

-------------------------------------------------------------------------------------------------

Resolving Web server conflicts on Port 80

A conflict on port 80 occurs when both the FrontPage Personal Web Server (PWS) and another Web server are configured to use port 80. Having two Web servers configured to use the same port number usually happens when you have the PWS configured for your computer, and then decide to install and configure a production Web server on Port 80.

1 Launch the Server Extensions Administrator. Locate the root web of the Web server configured on port 80.
2 In the console tree, right-click the root web from which you want to remove the server extensions.
3 Click Task on the shortcut menu, and then click Remove Server Extensions.
4 If you want to install the server extensions on port 80 of an IIS 4.0 or later Web server, locate the server in the console tree of the Internet Service Manager. Right-click the server, click Task on the shortcut menu, and then click Configure Server Extensions. If the Web server is not IIS 4.0 or later, locate your computer node in the Server Extensions Administrator, right-click the node, click New on the shortcut menu, and then click Web.

To use the content of your existing Personal Web Server, you must reconfigure it to run on a different port:

5 Open the FrontPage Personal Web Server configuration file, Httpd.cnf, which is located by default at C:\FrontPage Webs\Server\Conf\Httpd.cnf.
6 Change the line that reads "Port 80" to "Port 8080," then save the file. (Port 8080 is recommended because FrontPage will automatically start the Personal Web Server if it is running on this port.) If port 8080 is already in use, choose a different port number.
7 Launch the Server Extensions Administrator. Locate your computer's node, right-click it, click New on the shortcut menu, and then click Web.

8 Choose the FrontPage Personal Web Server from the list of available servers.

To open a web from your FrontPage Personal Web Server, append the port number to the server name. To copy the webs from your FrontPage Personal Web Server to your new Web server, use the FrontPage Publish Web command.

-------------------------------------------------------------------------------------------------

A couple of points that I discovered: The Server Extensions Administrator is found (in Windows 2000) in Control Panel -> Administrative Tools. It took me a little while to find the right context menu -- use the right hand panel to right click on. I reconfigured IIS to use FrontPage Server Extensions for IIS (not PWS).
Also, I found the name of the PWS configuration file to be httpd. (without a file type).

This managed to get me away from that annoying FrontPage message. Unfortunately, when I ask FrontPage to create a new web of the type Project into http://localhost/mydirectory, it goes into a perpetually busy state, with apparently no progress at all.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.140625