Troubleshooting Server-Side Script Errors
Contents
- 1 Troubleshooting Server-Side Script Errors
- 1.1 Error 104 Could not reach the specified Web page
- 1.2 Error 110 E-mail template could not be found
- 1.3 Error 201 SMTP Server Error
- 1.4 Error 202 SMTP Server Error Invalid e-mail address
- 1.5 Error 302 PHP settings error
- 1.6 Error 400 Component not found
- 1.7 Error 500 Failed to create CSV file
- 1.8 Error 501 Fail to read from the CSV text file
- 1.9 Error 502 Fail to write to CSV text file
- 1.10 Error 520 Fail to open CSV text file
- 1.11 Error 600 XML error
- 1.12 Error 601 XML file cannot be opened
- 1.13 Error 620 XML file not found
- 1.14 Error 650 XML server object could not be created
- 1.15 Error 701 Upload Path cannot be found
- 1.16 Error 702 Upload Cannot create file
- 1.17 Error 800 POST parameter not passed
Troubleshooting Server-Side Script Errors
Many NetObjects Fusion's Custom Components require specific server-side configurations to function properly.
The following is a list of common server-side errors and their resolutions.
Error 104 Could not reach the specified Web page
Cause: A page required by a script is missing or cannot be accessed.
Resolution: Republish your site.
Error 110 E-mail template could not be found
Cause: The template file used for generating the e-mail message was not found. The file may not have been published on the server.
Resolution: Verify that the Publish Component check box was checked. In Publish view, select Publish > Publish Components and ensure that the correct Publish Component has been checked.
Error 201 SMTP Server Error
Cause: The SMTP server specified in the configuration file does not exist or does not respond.
Resolution: Verify the SMTP settings in the component editors or contact the system administrator.
Error 202 SMTP Server Error Invalid e-mail address
Cause: The To or From e-mail addresses used for the mail settings are not correct.
Resolution: Check the e-mail addresses in the To and From fields in the component settings dialogs and ensure that the syntax is valid e-mail address syntax, (e.g., joesmith@netobjects.com).
Error 302 PHP settings error
Cause: The directory specified by upload_tmp_dir entry in php.ini file does not physically exist or it is not possible to write in it.
Resolution: Contact the ISP provider or, if you have the appropriate access rights, verify if the directory pointed by the above entry exists or the write permissions are granted.
Error 400 Component not found
Cause: The component ID in the configuration XML was not found.
Resolution: Republish your site.
Error 500 Failed to create CSV file
Cause: This error occurs when the write permissions on the directory where the .csv file will be created are not granted.
Resolution: Check the publish destination and be sure that the write permissions are granted for the directory in which the .csv file will be created.
Error 501 Fail to read from the CSV text file
Cause: This error occurs when the read permissions on the directory where the .csv file resides are not granted.
Resolution: Check the publish destination and be sure that the read permissions are granted for the directory in which the .csv file resides.
Error 502 Fail to write to CSV text file
Cause: This error occurs when the write permissions on the directory where the .csv file will be created are not granted.
Resolution: Check the publish destination and be sure that the write permissions are granted for the directory in which the .csv file will be created.
Error 520 Fail to open CSV text file
Cause: This error occurs when the read permissions on the directory where the .csv file resides are not granted.
Resolution: Check the publish destination and be sure that the read permissions are granted for the directory in which the .csv file resides.
Error 600 XML error
Cause: Most likely this error is caused by a syntax error or bad XML formatting.
Resolution: Publish the site once again.
Error 601 XML file cannot be opened
Cause: This error occurs when the read permissions on the directory where the .xml file resides are not granted.
Resolution: Check the publish destination and be sure that the read permissions are granted for the directory in which the .xml file resides.
Error 620 XML file not found
Cause: The .xml configuration file was not found. Most likely, this error is caused by a publish issue.
Resolution: Publish the site once again.
Error 650 XML server object could not be created
Cause: The XML server object needed to parse the configuration files could not be created on the server side.
Resolution: Be sure that an XML parser object is installed on the server, or that Internet Explorer 6.0 or greater is installed.
Error 701 Upload Path cannot be found
Cause: The path for the uploaded files does not exist on the server.
Resolution: Verify if the destination for the uploaded files exists physically on the server. If not, create it and grant the write permissions on it.
Error 702 Upload Cannot create file
Cause: The destination directory exists but there are no write permissions on that directory.
Resolution: Verify if write permissions are granted on the upload files directory.
Error 800 POST parameter not passed
Cause: Missing an xml node in the component configuration file.
Resolution: Republish your site.