|
| |
|
|
Giomanach
Posts: 6136 Joined: 11/19/2003 From: England Status: offline
|
FPSE Troubleshooting - 12/7/2004 7:48:27
This topic comes up a fair bit, so I may as well put the answers all in one place for you all. When using FP to build a web, you will no doubt use the FPSE components to acheive the final product, which is all well and good. Obviously this will require an FPSE enabled server. General Problems with FPSE, that can occur, are: 1) Loss Of Publishing Feature 2) FP Components Stop Functioning 3) Files Become Corrupt All of these will be down to the usage of FP, in conjunction with other things. Loss Of Publishing Feature There are many reasons for this to occur, main one being FTPing into the site to alter files. This will corrupt the FPSE on the server. You will notice that you have lost the ability to publish your web via FP when you receive the error message "The Target Web Does Not Appear To Have FrontPage Extensions", or something close to that. Other symptoms are: a) You can connect to the web via FP but not "upload" or "publish" files to the web, you can only view b) You are constantly told that you are using an incorrect UserName and Password c) FP reports publish has completed properly, but not files have been uploaded. How Do I Solve This Problem First of all, you must double check that the FPSE, are, infact no longer a stable installation. To do this, browse to http://www.dnswiz.com/fptype.htm and enter your web address in the following format: www.domain.com and then click on Check. This will give you one of three results: quote:
FrontPage Extensions: YES quote:
FrontPage Extensions: NO quote:
Server Type: This Server Does Not Disclose It's Identity If you receive the first one, then the problem is with your computer/copy of FP, if you receive the second or third one, do the following: Login to your Online Control Panel, and remove the FPSE from your account. Allow ten to twenty minutes for the process to complete, and then re-install them, again, allow ten to twenty minutes for the process to successfully complete. Then republish the web, in it's entirety. For Server Administrators: Windows: For Users on anything but Windows 2003 Server, re-install the FPSE via Add/Remove Programs, for those on Windows 2003 Server, First try removing them through Sharepoint Services, if that fails, then try Add/Remove Programs. *Nix Servers: Remove FPSE from the active functions on your server software, and manually remove the FPSE. Allow 5 minutes for the process to clear out the FPSE, and then install the FPSE manually That should solve scenario Number 1 FP Components Stop Working Most common ones to stop working are forms, and sometimes they don't work from the start. Forms created within FrontPage require FPE to function on the server. Therefore, again, you need an FPSE enabled server to work with. How Do I Solve This One? See troubleshooting Method for Scenario 1 Files Become Corrupt Usually due to using a combination of FTP and FP Publish on files containing FP Components. Pages you have created using FP components MUST be published for them to function. If you have published them, and they still appear to be corrupt, again, re-install the FPSE and re-publish the web. If all else fails on these, you have the options of changing hosts, after all there are literaly hundreds of them out there. You can also delete the web from your host server, and then republish to ensure that none of the problems hang around * - There are many web server programs for Unix/Linux servers, please refer to your documentation for instructions on how to do this, as I would be here all day giving instructions on how to do so Hope this is helpful to the users out there, if there are any questions, or corrections, post them
< Message edited by Spooky -- 12/13/2004 14:47:49 >
_____________________________
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts
|
|
|