ASP is not working, however the button next to this resource on the Domain Web Service page is set to ON.
Solution: Check if the *.asp files are not included into SSI section. It’s a common mistake. If you set the *.asp files to be launched via SSI library, set ASP to OFF, delete the *.asp extension from SSI list and then set ASP to ON again.
ASP sites with Access Databases Errors
ASP sites with Access Databases do not load the database after user replaces database file.
Solution: Application Pool in which the website is running needs to be recycled.
Failed to Add New Resource Over the Hard Credit
“Failed to add new resource over the hard credit” message when trying to create a new resource.
Solution: This means you have reached your Credit Limit. For example, you’ve used all your money on your balance if you pay by check, or your credit card expired/was broken and failed to be charged. In this case you’ll still be able to run your hosting account (with recurrent and extra usage payment accrued), but you won’t be able to create any new resource (neither paid nor free).
Failure to Decompress Files
The online file browser shows the zips as compressed files and offers to decompress them, but fails to do it.
Solution: WebShell can decompress only those files that are located inside the /usr/local/bin directory. If it’s not there, just create a link.
FrontPage Errors
When trying to connect to FrontPage I receive an error.
Solution: Try switching it off and back on.
FTP Account Errors
When trying to connect to an account using FTP, the system doesn’t respond for some time and then logs out with an error.
Solution: Use FTP active mode (disable passive). It is in your computer’s FTP configuration.
Unable to View Log Files
This is a known issue in the current version of HSphere. This occurs when trasfer logs are turned on, but error logs are not. The issue has been resolved in the upcoming release of HSphere (2.3RC4)
Solution: Turn on your error logs.
Webalizer Errors
When trying to connect to Webalizer I receive an error.
Solution: One possible reason can be that you are approaching your disk quota. Webalizer needs at least 2 MB unused disk space to function properly.
