Showing posts with label Fatal Error. Show all posts
Showing posts with label Fatal Error. Show all posts

Fatal error: require_once() [function.require]: Failed opening required ‘clsdataaccess.php’

Friday, July 29, 2011

Fatal error: require_once() [function.require]: Failed opening required ‘clsdataaccess.php’

(include_path=’.:/usr/local/lib/php-5.2.12/lib/php’) in /hermes/path/web135/somebuketno/accountname/class/clsprojects.php on

line 3 Reason:

The script at line 3 of the file ‘clsprojects.php’ is trying to call the file ‘clsdataaccess.php’, but there is no file in the directory.

Fix : If you see the error “failed to open stream: No such file or directory”, then the particular file in the account is missing or it is uploaded to the incorrect directory. You can fix this issue by moving the file to the correct location or uploading it to the proper location. If the file is uploaded to a different directory, you can also correct this issue by correcting the path in the PHP file.

Fatal error: Allowed memory size of 31457280 bytes exhausted (tried to allocate 13404 bytes)

Sunday, February 6, 2011

 If you are getting following error: Fatal error: Allowed memory size of 31457280 bytes exhausted (tried to allocate 13404 bytes). Then you need to increase upload maximum limit in php.ini file.

ex: upload_max_filesize = 4M

Note:  Here you can upload the maximum size of of the file upto 4MB.(Increase Here). Click here to learn make the changes in php.ini file.

Fatal error: Allowed memory size of X bytes exhausted

Tuesday, February 1, 2011

You can  resolve the issue by increasing PHP’s memory limit in .php file. To increase PHP’s memory limit up to 32MB, please make the changes in php.ini file.
eg: memory_limit = 32M to your server’s main php.ini file.

This link will help to iPage customer to edit the php.ini fil: http://www.ipage.com/knowledgebase/beta/article.bml?ArticleID=1290

Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent

This is the common error, you can see when you will start working with sessions in PHP. 
*The below are some cases which may solve above error .
Write ob_start() before session_start() statement. As ob_start() turn on output buffering means no output sent to script and it stores the output in internal buffer and make sure that nothing gets sent to the browser before session_start() statement. This happens in case there is a white space or some characters before session_start() or even before
*Also, you can solve this by using UTF-8 encoding WITHOUT BOM (Byte Order Mark). “Don’t save your UTF-8 files with BOM as it creates issues”.
 

Most Reading

Sidebar One

+1-800-574-0902 +44-20-7993-2673 (ID: 173296)