|
What should I do if NetObjects Fusion crashes?
Crashes? Not NetObjects Fusion? Well, occasionally all software crashes, even ours. We don't like to make a habit of it, but when it does happen, there are things you can do.First--you can protect yourself in
advance by saving your work often. You can do this by pressing Control-S, or choosing File/Save. Even if the the program crashes, the work you've done before you saved will be saved. There are a number of
reasons that a file could crash. Usually the problem is related to a conflict on the system between shared resources, such as memory, disk space or library files. In some cases, under Windows 95, damaged registry
entries can also cause a problem. If you experience or have experienced random crashes while running NetObjects Fusion, try reinstalling the software. If this does not seem to solve the problem, also make sure that
NetObjects Fusion is the only program running under the operating system, and test to make sure that it functions correctly under these circumstances. If the crash seems to be associated with a particular
set of instructions you give the program, it is possible that there is a specific bug related to the actions you are performing. You can search our on-line knowledgebase for known issues. Our online knowledgebase can be
accessed from
http://www.netobjects.com/support/html/knowledgebase.html Additionally, you can review our list of known issues at: http://www.netobjects.com/support/html/nf4knownissues.html There are also several common actions which can result in a crash if there is a problem with the site file. These are listed below:
- Crash during compaction
- Crash when opening file
- Crash when accessing a page
- Crash during preview or publish
- Crash while importing a site during the recovery procedure
- If you get a crash on compaction of the site, you should immediately revert to your last saved backup. The compaction routine is designed to check your site file for errors. If one is found, this is an
indication that some occurrence during the last session was not written correctly to the database, either because of resource conflicts or internal errors.
If you get crashes opening a file, or when attempting to go to a page or preview or publish a certain page, it is usually because that page which is trying to be accessed contains incorrect or damaged information
which the program is unable to resolve. In this case either immediately revert to a previously saved backup from before the crash, and/or perform the recovery procedure on the problem file following the instructions
outlined in the document recover.txt located in the NetObjects Fusion 4.0 directory on your hard drive. If you get a crash during the recovery procedure, there are two possible scenarios. One is that the crash
occurred immediately. If this is the case, the file is most likely damaged such that the import routine does not recognize it as a valid file. Try recovering from previously saved backups if this type of crash occurs.
If the crash occurs during the latter part of the import, at around 85% when the file is saving, this file may usually be recovered by opening the newly created file and running through the recovery procedure a second
time. Anytime the file crashes it is wise to revert to a backup from before the crash occurred to prevent any problems which might have resulted from the crash. What do I do if I receive the Out of Memory Error? The Out of Memory Error indicates that
NetObjects Fusion does not have enough resources to complete the task you have asked of it. You should be prompted to quit the program and retry your action. If you do get this error you might want to try shutting down
other concurrently running applications, or check to see that you have enough available memory or free disk space on your machine. Relaunch NetObjects Fusion and try your action again. If you are once again prompted
with the out of memory error, or the program crashes, refer to What Do I Do if NetObjects Fusion Crashes? If you get this error when you are migrating a site file forward from a previous version, or importing a site
file during recovery, this can also indicate that there is a problem in the site file itself. In the former case, try running through the recovery procedure using the previous version before bringing the site forward
into version 4.0. If the problem persists, try shutting down all concurrently running applications and reboot the machine. What do I do if I receive the
error This File Contains an Instability? The full text of this error is as follows:This file contains an instability. If
this file was created in an older version of NetObjects Fusion, it is likely that the instability was introduced by that version. Please use recover.txt, located in your /NetObjects Fusion folder, to learn an alternate
method of opening this file. While the text of the error message indicates a possible cause in a previous version of NetObjects Fusion, this error can occur under some conditions (usually after a crash) in the
current version as well. Usually the error comes up as a result of a crash and will show up when you open the site. If you see this error message, revert to the backup from before your last save, or perform the recovery
procedure as indicated in the error text. Sometimes this error will again be shown when the import phase of the recovery procedure is completed. This indicates that there is still a problem with the file. In this case
you should perform the recovery procedure again, on the file you just imported. In other words, if the original file was file A, and you imported it into new file B, import file B into new file C. This should eliminate
the error. What do I do if I receive the error Damaged Objects Have Been Found and Deleted? There are two dialogs which contain this message. These are:
- Damaged objects have been found in the layout and have been deleted.
- Damaged objects have been found on the page and have been deleted.
If either one of these messages is displayed when accessing a page, this indicates that NetObjects Fusion has detected that one or more objects in that page or layout were incorrectly committed to the database during
the last save. When it detects this, it eliminates the incorrect data from the page. You may notice that an item on the page is now missing or not displaying correct information. If you receive this error repeatedly,
it may indicate a more serious problem with the way that the database is being committed to disk. At this point it is a good idea to run through the recovery procedure outlined in the recover.txt document located in the
NetObjects Fusion 4.0 directory on your hard drive. What should I do if I get the Not Enough Disk Space error? This error is a generic one which means that a write failed to disk. Typically this indicates that there is not enough disk space on the hard drive specified.
However, it can also indicate that a drive is write-protected, that there is an error on disk, or that some other program or system routine is preventing NetObjects Fusion from writing to disk. This is known to be a
conflict with some virus programs. If you are running a virus protection program, try turning this off to see if you still get the error. What do I
do if I receive a Remote Transfer Error? The Remote Transfer Results dialog box is shown any time an error is encountered during the transfer
of files during publish. Examine the results returned in the edit area to determine where the error may be occurring.NetObjects Fusion 4.0 has a number of issue related to this dialog box. The most common
error is when the Remote Transfer Results returns TCP/IP errors similar to the following: "the file C:\index.html could not be
sent because of a TCP/IP Error (PORT failed) server response: 426 Data Connection: Connection reset by peer." Check the following things to attempt to eliminate the errors:1) Turn on PASV mode FTP. Some servers
require a PASV mode connection and refuse active connections. To turn on PASV mode, select your Location Properties in the Publish view and on your remote settings click the Advanced tab. Check on the Connect passive
(PASV) FTP mode checkbox and try republishing 2) Close NetObjects Fusion and other currently running programs, relaunch your site, and try republishing. Sometimes these errors can be resource related. Closing
NetObjects Fusion as well as the other programs can free up resources which may be needed for publishing. Additionally, rebooting the system and trying a publish with no other programs running but NetObjects Fusion and
any software required to establish a connection to the server, may help if the situation might be low resources at the time of publish. 3) Since this error can result from timeouts from the server, if the server has
high traffic or is performing slowly at the time of publish such that the server reports timeouts to the NetObjects Fusion connection. If this might be the case a republish at a different time when the server is not as
busy may give better results. 4) It is also possible that this error results from the inability to find files locally which the publish view thinks are supposed to be transferred to the server, but which are either
not available or not actually in use by the site file. This can be the result of damage to the site file, and seems to be more common with site files which have been migrated from previous versions of NetObjects Fusion.
You should always check the destination server or directory to verify that all files were sent. If they have been sent and the site works correctly, then the reported errors were false. If not, the following procedure
may help in reducing errors:
- Delete all Unused File Assets from the Assets view. This command is available in the Assets menu when in Assets view
- Clear all Customizations in Publish view. This option is available in the Setup -> Directory Structure dialog in Publish view
- Run the site through the recovery procedure. This procedure is outlined in the file recover.txt located in your NetObjects Fusion 4.0 directory.
- If none of these work to eliminate the errors you may also publish your site locally by configuring your server locations to a local directory on your hard drive or LAN. You may then use any third party FTP
client to upload the contents of that directory when the local publish is complete.
What should I do if NetObjects Fusion won't publish? Sometimes if you've worked
in NetObjects Fusion for a long time and try to publish, it will publish a few pages, then stop. If this happens, close Fusion, wait for the file to be compressed, restart Windows. Reopen your NOD file and try to
publish first thing. Often this will correct the problem.If NetObjects Fusion refuses to publish a page, this can sometimes mean there is an internal error on that page and it needs to be deleted. Make a new page. Go
to the problem page. Select all the objects in the layout individually, by holding down the shift key and clicking. Do not choose "select all" as this sometimes can copy the problem." Choose COPY. Go to the new page.
Click in the layout. Choose Paste. Point any internal links to this new page. Delete the old page. Publish. |
