Webmail requires a network port to operate (default: port 80). If another web server is running and using this port, the Webmail port must be changed. To change the Webmail port, right-click the ISMail icon, select 'Open', access the 'Webmail' tab, enter a new value (e.g. 81), and click 'Apply'. Then, re-start Webmail. Note that Webmail must be accessed using this port (e.g. if the port is 81, use http://127.0.0.1:81/webmail/).

First, make sure that the permissions on the file are set properly for execute permission. By default, the permissions are 644 (rw-r--r--) and do not allow execution. You need to change the permissions, or the mode, on your cgi script to 755 (rwxr-xr-x). Some FTP programs allow you to change file permissions, if yours doesn't, then you can use the File Manager in your Control Panel to change the permissions.

This error is caused by a setting in your FTP client, that limits the amount of time your FTP client will wait for a server to respond. In order to fix this problem, increase the "server timeout" setting; a setting of 180 seconds should be enough time to connect to the archive.org servers. If you use SmartFTP, the "server timeout" setting can be found in Tools > Settings > Connections.

This is a common error found in a Web browser when you are attempting to run a Perl or CGI script that has problems. The three most common reasons for this error are the following: Your script permissions are set wrong. Try setting them to 777 or 755 temporarily while troubleshooting the error. Your script was uploaded in binary file format instead of ASCII. You must upload Perl and CGI scripts in ASCII format only. Your path to Perl (the "sha bang" )line is wrong.

This error is caused by a setting in your FTP client, that limits the amount of time your FTP client will wait for a server to respond. In order to fix this problem, increase the "server timeout" setting; a setting of 180 seconds should be enough time to connect to the archive.org servers. If you use SmartFTP, the "server timeout" setting can be found in Tools > Settings > Connections.

Internal Server Errors, where you have edited the program yourself, are most commonly caused by typos during editing. These typos result in the program not being valid Perl, and errors confusing the webserver. What you should initially do, is check every line you edited, to check that you have not left a set of quotes or brackets (of any variety) open.

Ensure that your hostname is set properly by your operating system. If you type 'hostname --fqdn' and get 'hostname: No address associated with name returned, then the hostname for your system is not properly configured for your fqdn. This is necessary for IMAP operation. For CentOS/RedHat/Fedora, this is configured by setting your FQDN in /etc/sysconfig/network under HOSTNAME=. This is usually caused when you accept the default of localhost.localdomain.

Under normal circumstances, the Apache access control modules will pass unrecognized user IDs on to the next access control module in line. Only if the user ID is recognized and the password is validated (or not) will it give the usual success or "authentication failed" messages.

There may be a number of reasons for receiving this message, most relating to an interruption in contact. Sometimes the connection may be re-established by holding down the "shift" key on the keyboard and clicking on your browser's "reload" or "refresh" button. If this does not solve the problem, clear the cache files and close and restart the browser.

The most common cause of this problem is the listening port you've selected in the config file is already in use by another process on the shell. Look for the line where you've set the port (e.g. listen 3333 all) in the config file, and try several different ports to see if it fixes the problem. If your shell provider specifies a port range to choose from, follow that.

Please contact Support "Here" . This is a security setting in 1 Click Spy Clean if you tamper with the clock this message will appear, for example, you use the wrong year, month 1 Click Spy Clean will automatically recognise this and will not allow you to open 1 Click Spy Clean until we provide you with instructions to reset the security on 1 Click Spy Clean along with a pin.. Back To Top

We need the name the order was placed under and the date of the order, or else the order ID number from your confirmation. Please let us know right away, as we want to be able to help you as soon as possible. If the rings are defective, of course, we'll be happy to refund your money or replace the rings. Your private information is used only by us, and only to allow us to serve you better. We do not have access to your credit card information.

You most likely installed or updated your copy of Norton Anti-Virus. This is a known problem with Norton Anti-Virus and Not Water Solutions. To correct the problem uninstall Norton Anti-Virus and install a different Anti-Virus program such as Avast or Nod32. For more information see Microsoft's TechNet answer.

There is a possibility that there is no web.config file for the project or there is no Execute permission for the project. If the web.config file is missing, add one to the directory that contains the ASP.NET application. You can copy one from the numerous samples applications available with the framework installation. On the other hand, if your project already has a Web.

You will get these warnings if your ccnet.config file contains invalid elements or attributes. Please double check the documentation that came with your installation (in the /doc folder). Please be aware that the documentation on the web site may reflect a more recent version of ccnet than what you have installed. If you are attempting to use a task or a property that has not been implemented in your server's version of ccnet then you will get this error.

I've been having some problem setting up Outlook / Eudora / Pegasus / Messenger. I've been having some problem setting up the SMTP server connection.

All sites are equipped with web based e-mail. You can access your webmail by going to http://yoursite.com/webmail and replace "yourdomain.com" with your own domain name.