As the developers of Open Journal Systems, Open Conference Systems, Open Harvester Systems, and Open Monograph Press, the PKP team are experts in helping journal managers and conference organizers make the most of their online publishing projects. PKP Publishing Services offers support for:

As a customer of PKP Publishing Services, you will not only receive direct, personalized support from the PKP Development Team, but will be contributing to the ongoing development of the PKP applications. All funds raised by PKP Publishing Services go directly toward enhancing our free, open source software. For more information, please contact us.

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

Those files are generated automatically and it's rare that bad things happen to them. Can you post the contents of one of the smaller ones that is having a problem? What version of PHP are you running?

Thanks Jason.You are absolutely right, these are generated files & I too don't any possibility of all of anything going wrong there. System was running fine & all of sudden problem happened.I suspect some settings are changed by hosting company but not sure what? Here are the php version details.

We are using Native version of php. Looking for earliest possible help, our production system is at halt.

jainshailu:With an effort to do a clean install of OJS 2.4.2 on a different subdirectory on the same shared server as our current journal is hosted, I get the same error. Please share the information if you have resolved this error. Our server uses 5.3.17 and MySQL 5.x.x