I am running a PHP site that uses Ajax and jQuery as well. The site will run fine for quite some time, and suddently my pages (and ajax-retrieved sub-pages) comes back with the message
PHP has encountered an Access Violation at 77FCAFF8
It seems that rebooting the server corrects the issue. Running PHP Version 5.1.6 (Windows NT 5.0 build 2195). I did a some searching on here and some other sites, and there seems to be no fix..
URL REMOVED
UPDATE:
I think I'm on to something.. will get back to you.
UPDATE
After reviewing the IIS setup, i noticed there was no Handler Mapping setup for the website. This, of course begs the question - how did it ever work in the first place, when it was originally setup this way!? I added the handler mapping and it seems to be Okay so far.
UPDATE
The problem popped its heads out again this morning after 36 hours without encounering it. Back to the drawing board.
UPDATE
We ended up just moving the site to a secondary web server where we were able to upgrade PHP without an issue.
This is a PHP issue somewhere. You could spend some time narrowing down which function you're using that is causing the problem. I would instead upgrade to a newer version of PHP. If still no luck, try a slightly older version. There have been significant changes with version 5.3.2.
After some research I think this may be the solution (Taken from http://bugs.php.net/bug.php?id=28929 ):
[2010-06-11 15:12 UTC] in2ishun at yahoo dot com
***************** SOLUTION!!!!
I realize this issue is AGES old, but it still manages to be the top hit on Google searches as of now (6/2010).
I fixed my own instance of seeing this error. W2k3, IIS6, PHP 5.2.6, MySQL 5.1.
The problem is in the pathing. When I used the MSI installer for MySQL without doing an "advanced" installation (where I could manage the install details), it added a path to the system environment that contained spaces. Even after changing the path environment to use the Windows short-name location of the mysql bin directory, it still didn't work.
The solution was for me to reinstall mysql and set the default installation path to just off the root (e.g. C:\mysql). Once I did that the error went away and my app started working.
There are a number of sites with a variety of potential solutions to this issue and several of them mentioned paths and the "libmysql.dll" file (in the "bin" directory of your mysql installation).
If this helps you solve your problem, consider leaving a comment here so others can see that it works.
Related
I experienced strange behaviour of wordpress. Whenever I want to publish a post or page it says "Missed schedule". But I have no intention to schedule. I want to publish something directly.
Some times later (I assume when wp-cron runs) the pages gets published. But this bahaviour is immense problem for me developing the page, as the customizer crashes and is not able to update changes. Usually a "immediately" published post should be published, well, immediately. Never had this issue before on other systems. I do not need the scheduling function at all, but now I am forced to schedule anything?
Setup:
CentOS 7, PHP 7.4, Apache 2.4, MySQL (Fresh Setup of the LAMP Server) Als tried PHP 7.3/MariaDB.
Installation of latest wordpress 5.5.1 without any issues (but also tests with older versions caused the problem)
Check of Servertime vs. Wordpress timezone - everything fine here
Standard Theme adter installation, no plugins active!
Checked the rights for apache user, everything fine (755/644)
Checked the "run wp cron" plugins, but thats not solving the issue.
I assume there is some problem with wp-cron or the db but most probably my server setup is missing some dependency/configuration? (But I tried different Tutorials for installation, so must be something very basic...)
Somehow it seems like nobody every experienced this issue, as I googled for hours... Hopefully sombody with more backend experience can explain whats happening here and how to fix it.
Here is a picutre of how the workflow looks like
If you are publishing without schedule Wordpress will publish it unless something prevents it from happening.
There is a known issue where if you use localhost server may have issues with Gutenberg so for test purpose try https://wordpress.org/plugins/classic-editor/ and see if its fixing it for you. If it does its probably a problem with your server settings preventing the rest api to work or issue with wp-cron.php.
Same problem here with all installations of WP in a VPS.
No useful info on google.
Somebody has find a workarround: change Centos+plesk to Ubuntu+Plesk. This seems to work fine.
I have finally found a solution to the problem. Changing the system is not a useful option for me.
In this forum they explain the problem: here
And it brings us an explanation in the plesk forums: here
It is basically a problem in CentOS7, the UTC file is not valid and this causes problems in publishing changes in WordPress.
The problem is solved by replacing that file "/usr/share/zoneinfo/UTC" with a correct copy (I have taken it from another server with CentOS6).
And everything works correctly.
You don't even need to reboot.
I've got a CakePHP 1.2-based web site (I know.. too ancient) that I need to upgrade only to whatever is the oldest Cake to support PHP 7.1 (I think roughly Cake 2.8, from what I've seen so far), because my host is upgrading PHP to 7.1 across the board. This site only needs to live maybe 1 more year before we totally replace it, but we don't have time to do that before the host upgrades PHP at end of year.
I am trying to get the web site as-is running in a vagrant VM, so I can go through the upgrade steps there, carefully, and understand exactly what I need to do. My problem now is that I can't get the site to display. More concretely, when I try to load the site with nginx in vagrant, I get nothing but a blank screen with a few PHP warnings (strict standards to the effect of Non-static method Configure::read() should not be called statically), but nothing obviously broken. There's basically nothing in the PHP log, and nothing in the Nginx log. Again, this is the site as currently running (successfully) in production, which means my vagrant PHP is 5.6.38 (the actual production PHP is 5.6.25). Running with php-fpm.
Cake's own logs are only reporting the following, which arises inside a controller method function disableCache(), which is trying to insert headers to prevent the browser from caching the request:
2018-10-22 15:18:57 Warning: Warning (2): Cannot modify header information - headers already sent by (output started at /usr/share/nginx/html/www.mydomain.com/cake/libs/object.php:63) in [CORE/cake/libs/controller/controller.php, line 844]
I have inserted an early return in that method just to stop these warnings.
In PHP, I've got these settings:
error_reporting(E_ALL^E_DEPRECATED);
ini_set('display_errors', 1);
ini_set('error_log', '/var/log/php_errors.log');
In Cake 1.2's app/config/core.php, I've got:
Configure::write('debug', 3);
Database is local MySQL in vagrant, with settings in app/config/database.yml.
Can someone suggest where I should go next in debugging this?
From my own experience, PHP 7.1 and CakePHP 1.2 can work together. You simply need to upgrade your source code to make it compatible with PHP 7.1 but you can continue to have your system in CakePHP 1.2 without having to upgrade CakePHP. Of course, if you can use a newer or the latest version of CakePHP that would be perfect but think of it as a separate project and not something you must do now only because your host is upgrading PHP to 7.1 across the board.
If you can get your Cake project upgraded to 1.3.21 (the last 1.x release), you may be able to use this: https://github.com/littleant/cakephp-1.3.21 instead of upgrading to Cake 2.x. Might buy you a little time!
So I have a Portable Webserver program called USBWebserver,
because the original program still uses php 5.3 (I believe) I went on an adventure to upgrade it so that not only me but the rest of my class can use it.
I upgraded the Apache server build to 2.4.27
I upgraded the PHP binary to 7.1.9
The thing is... Everything functions but one thing:
For some reason MBString (Yes, just MBString) will not start up with a variable path anymore. If I set a manual path it functions it just no longer does this with a variable one.
Before people say:"Then why don't you just make it a manual path and be done with it." because it needs to stay portable and usable "out of the box" so to say.
I am quite stuck on how to fix this issue. If any info is needed, please ask and I will edit this post with the info. (Like if you need php.ini)
After a lot more messing about with it I finally found out what fixed this issue. I'll post it here so that others who might try to do this won't have this hurdle to combat.
extension_dir's path at first was "php\ext" as php.exe wasn't liking that I changed it to ext, which php.exe liked but apache...not so much.
After a long while I changed the path to extension_dir = ".\php\ext" and as if the gate of heaven opened... it functioned. Fully and completely without even one error.
So now I have a modified USBWebserver running:
PHP 7.1.9
Apache 2.4.27
PHPMyAdmin 4.0.4.2
MySQL 5.6.13
Fully portable, fully fuctional. I hope this little tid bit of info helps someone else some day and if some people want the program, ask and I will make a download link and edit it into my original post any this answer.
Have you been updating usbwebserver to newer version?
It seems that the officiel development has stopped.
I have tried to update php to version 8, but then the apache server won't start, and there is noting in the log file - its just empty.
Thanks
Jorgensen
I am trying to install PHP on my IIS web server running version 7.0. I downloaded the php-7.1.8 Non Thread Safe for Windows 64. I then procceded to follow the steps found here: https://www.howtogeek.com/50432/how-to-install-php-on-iis-7-for-windows-server-2008/.
I had no issues with the install but when it came to the last step of creating the test PHP page and launching, instead of getting the results, i'm being asked to Open or save the file??
I've also tried putting this into a live website and accessing it outside the web server. When I try this I receive a 500 - Internal Server Error.
I had tried this about a year or two ago and got frustrated, so I gave up and have retried today but experiencing about the same result. Don't know what other information would help, but i'm willing to provide what's necessary. Thank you for any help.
After continuing research I ended up using the Windows Installer version (https://www.microsoft.com/web/platform/phponwindows.aspx) and then went back through the configuration steps of the php.ini file.
I'm trying to figure something out:
I am using Ubuntu server 11.10 virtualized on Win7 (I don't think that matters but more info is better than less) to work on a Drupal 6 website I inherited and need to make significant changes to.
I want to set up a development copy of this Drupal website on my Ubuntu server so I can work without worrying about torching the production website.
I successfully got the production files downloaded and onto my machine, I got the production MySQL database exported and imported into the dev MySQL server, and I set up a symbolic link from the directory /home/myname/thewebsite.com to /var/www/thewebsite.com so I can easily access it.
When I got the website they didn't know the admin password so I dug around online and reset it in the dev db using phpmyadmin and finally log in.
When logging in and poking around the site there are lots of errors, which when googled lead me to believe that PHP 5.3 is causing them and that there are some modules in use that only work with PHP 5.2
After looking around a lot online and on stackoverflow there seems to be no easy way to install PHP 5.2 on Ubuntu Server 11.10. With no packages for 5.2 available through apt-get or aptitude what should/can I do?
1) Install 5.2 from source - how do I get it to interface with MySQL and Apache2? Also, I've never installed anything significant from source. Is there a walkthrough?
2) Replace the repositories with old ones? Will this work on 11.10? The newest instructions I found were for 10.04
3) Use already built PHP 5.2 packages for Ubuntu? Couldn't find these
4) Pay someone who knows more to do it for me? (Just kidding, this isn't really an option...)
Cheers and thanks for your help!
PHP dropped support for 5.2 in August 2011; operating system providers such as Ubuntu will not supply a version that is out of support, so you absolutely won't get an official copy of PHP 5.2 on the current version of Ubuntu (or any other OS).
If you're running an older version of Ubuntu (eg 10.04), you might be able to do it; it would still be a downgrade, because PHP 5.3 has been the default version for quite a long time now.
If you're on a newer version of Ubuntu, ie 11.10 as you state, it is going to be a problem for you.
The Drupal developers dropped the ball badly on this one. I guess it was because Drupal 7 tool so long to finish; they were expecting D7 to be out much sooner, and so they never bothered fixing up D6 to work with PHP5.3. As it turned out, this was a big mistake, because in fact D7 still wasn't officially released when PHP dropped support for 5.2.
But even so, they should have fixed it, because they're still officially supporting Drupal 6, so they need it to work with the current version of PHP. This is definitely Drupal's problem, not PHP's, Ubuntu's or yours.
But you still need to deal with it.
I found this question over on AskUbuntu.com, which gives an answer applicable to 11.04. It isn't quite 11.10 you were asking for, but it it a lot more recent than the best you'd found, so it might be helpful.
Alternatively, you could research exactly what it is about Drupal6 and your specific modules that doesn't work in PHP5.3. The language differences between 5.2 and 5.3 that can break things are not big, so I would expect any code changes required to be fairly small. You might find you can fix the code yourself. And maybe even submit the changes to the community -- Drupal is open source, after all.
Another tack you could take is to consider whether this saga represents an opportunity for you to move the site to Drupal 7?
This may or may not be feasible, depending on the modules you're using, etc, but if it is possible, it will solve the problem, because D7 is of course fully compatible with PHP5.3.
And just to cheer you up, I'll close by mentioning that PHP are on the verge of releasing PHP 5.4. Hopefully the Drupal devs will be more on the ball this time.