Currently Viewing Posts Tagged “500 error”

PHP – Parse error: syntax error, unexpected end of file

FastCGI sent in stderr: “PHP message: PHP Parse error: syntax error, unexpected end of file in /your_path/yourscript.php on line 308” while reading response header

This is the error when I check the php log file. Because I met the blank page with 500 internal error, which is loaded OK on the other server.

The real reason is I use (<? ?> ) and (<?php ?>) in mix. So I faced with this parse error when running the script on different systems:

Parse error: syntax error, unexpected $end in X on line Y

where X is the file path and Y the line number, usually the last line of the file. But the shotform may not there.

To avoid this error, refrain yourself from using the short form and stick to ( <?php ?>), despite the extra 3 characters. This will make your code universally accessible and it is essential if your developing for beyond your own personal use. If you insist in using the short form (<? ?> ), and you get this error, you can enable the short form option in the php.ini file.

short_open_tag=On

Keep in mind though, that the short form is supposed to be deprecated in PHP 6. If this goes through you will have to go back and change all your source files.

 

In the furture, I wil keep using long form of it only.

Classic ASP program with Access database on Windows server 2008

Got error 800a0cb3 from the Web log file at Windows Server 2008. It is IIS7. The Web application is made by ASP. Actually classic ASP, not ASP.Net.

And also with Access database.  The page is try to add new record into the Access database file. But the browser return 500 internal error. The detail error code in log file is 800a0cb3 with the description: Recordset does not support updating. This may be a limitation of the provider or of the selected locktype.

I did a lot of research and found it is a right issue.

Continue reading “Classic ASP program with Access database on Windows server 2008”

Solution of Dreamhost memory limitation

The previous post I wrote explain why 500 internal error happen when MovableType publishing.
At the last, I promise that I will tell you how to solve this problem without upgrading your sharing host to VPS.
KEY point: The 120MB memory limit is per user.
If you know that, the answer is simple.
In one Dreamhost account, you can create many, many users. So
Create a new user for Movabletype powered blog.

Continue reading “Solution of Dreamhost memory limitation”

  • Archives