I am working in a php web site and my web server application is IIS on Windows Server 2003.
I added a web form that is needed to be saved and sent by email.
There are four files used to achieve that:-
file1.php - to get the user inputs
through the form insisde it. file2.php
- to recieve the form data then save it in database using odbc and send
some of them by email file3.js - to
validate form elements file4.css - to
change the design and style of the web
page
I faced a strange error message which has not any reference to specific option or setting that I can change to solve the problem.
what I get is as the following:-
HTTP 500 Internal Server Error
The website cannot display the page
HTTP 500
Most likely causes:
•The website is under maintenance.
•The website has a programming error.
What you can try:
Refresh the page.
Go back to the previous page.
More information
Since at the moment there isn't much details in your question, I suggest you can do this: 1) try to print a "hello" in your PHP file and see if it works first, and if it does, then try the first few lines of your program, and print out something and see if it works or not. In other words, reduce to the simplest and see if it works or not. Then build on it gradually.
read IIS log
find IIS log in http://portal.smartertools.com/KB/a154/where-are-my-iis-log-files-stored.aspx
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I am getting "500 Internal Server Error" when I used ajax call. What is causing this problem? How to resolve it?
debugging, fixing, and resolving a server error from an Ajax call is exactly the same process as any other request.
Check the web server error logs for any indications of what the error is
Introduce debug statements into the serverside code around where the error is occuring (and add a little bit to your ajax request to dump all the response as plain text)
It may also be useful to copy the URL and querystring used in the Ajax call and paste it into your browser to view any responses.
Firebug for Firefox is also a useful diagnostic tool for testing what is being sent as part of the Ajax call and what is being sent back as a response.
Use fiddler or firebug to look at your network request/response.
It looks like you may be using perl?
Try adding use CGI::Carp qw(fatalsToBrowser); on a new line after your path to perl declaration.
I was working on a customer's server and had problems executing PHP code. I checked on the CPannel the errors and it was just a permissions error.
The PHP files had to be set with non writable permissions for groups.
In my case setting the permissions to 644 got everything working.
If your server is running Windows, then look in the event log and see what server error occurred.
Look in the server log, which on Linux is normally in something like /var/log/apache2 or /var/log/httpd.
Download Firebug, intercept the ajax call and load it in the browser or look at its output. Make sure you server is set to report errors (look at php.ini for PHP settings, for example). Whatever is causing it is probably going to show up.
Make sure you don't actually throw the error 500 yourself in the code.
If you use PHP, then use a debugger, such as PHPEd or xdebug and step through the code. That's the way I debug my PHP and it's the best way, though takes some time to set up.
You created and fired off a request to a server with whatever you did in Ajax. So far, so good. The server tried to process your request but ran into an error condition. That's usually caused by some bug in the server code.
As John Saunders advises, you can usually get more information on the server-side problem by looking into its logs.
My step usually (in particular order):
open firebug and look up the particular ajax request from console. Then, see the parameter, header, and URL request. Examine each data to see what goes wrong. If it all seems OK
I will look at my server log (httpd-error.log on Apache) and check any particular error that came from that request.
Fix what is wrong based on all there checking.
I was also facing the same error today. It mostly occurs because of wrong folder/file name because name of folders and files when linking/ sending ajax requests is case-sensitive on actual servers (not in Server simulators e.g. WAMP/XAMPP). So, check your file path to which you are sending the request and the problem may get solved.
This is a very similar to the question posed at Use php and simPro API to list customers.
The response to that question suggests downloading examples from GitHub. I have downloaded the SimPro examples at GitHub and have them functioning on the commandline.
I want to be able to use a web page as an intermediary between my FileMaker Pro database and the SimPro API. I can pass data to a web page written in PHP. It can convert the data to JSON and form a call to SimPro receive a response and display the success or failure as a web page.
Presently I have my JSON data hardcoded so that I can test the process. When run from a web browser I don't get a result, though the code works perfectly well running from the command line.
I'm not sure what I need to do make the examples web compatible. Can someone push me in the right direction?
Would be more than happy to help - could you post a snippet of your code - minus the auth info of course - so that I can try to assist?
Do you have your code printing anything else to the browser first - so that you make sure the script is actually executing as it should from the web server side - and have you checked your web server logs for any errors?
In some cases I've seen this is usually due to PHP config (there are separate configs for CLI and CGI in most setups) and can mean whilst libraries are loaded in one environment they may not be available to the other. The web server also usually requires a reload if you have just loaded libraries for use within your script.
Hope that helps.
I have a PHP script that's called when submitting the order form (removed). The script does some basic verifications and uses an external API (sends a GET request with file_get_contents and stream_context_create) to register/update user info.
The problem is that sometimes it works right, but most of the times it reloads the page that called it. The page is hosted on my LAMP server (removed). If I host it locally, using the PHP build-in server, it does seem to work always.
I don't have a clue what can cause the webpage to reload instead of executing the echo statements.
The script worked right last Friday, but now it doesn't. Today I've updated PHP, but - as I expected - nothing has changed.
Obviously there isn't anything in the error_log.
There's probably a bug with the latest FastCGI handler. With any other handler (CGI, suPHP, DSO) the script works correctly.
I have a form that collects data and may take several hours to complete since it has an editor where users can add creative elements. If the form is submitted after an hour or so, the site redirects to a 404 Not Found, the URL was not found on this server. I tested this using a very simple form processing script that prints out POST data and still got the error. This seems to only happen on our linux server. I have a WAMP local server running the same script and the POST data sends through fine, no matter how long the form is idle for. Any clues as to what I can try change on the Apache config or PHP side. Thanks
Hello i am new baby in wordpress CMS.
I bought iPage Hosting for my website.
When i installed wordpress to my hosting , this error message is showing.
Server Response Empty
Your server responded with a blank page, which means your server is having difficulties processing PHP requests. If you are not familiar with this error (potentially a "500" Error), please contact your server admin or web host about possible resolutions.
How can i solve it?
"500" error indicate that it's Internal Server Error.
Cause of HTTP 500 Errors
The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.
Most of the time, "gone wrong" means an issue with the page or site's programming, nothing you have anything to do with.
How To Fix the 500 Internal Server Error
The 500 Internal Server Error is a server-side error, meaning the problem probably isn't with your computer or Internet connection but instead is a problem with the web site's server.
While not probable, it is possible that there's something wrong on your end and we'll look at some things you can try.
Reload the web page. You can do that by clicking the refresh/reload button, pressing F5, or trying the URL again from the address bar.
Even if the 500 Internal Server Error is a problem on the web server, the issue may only be temporary. Trying the page again will often be successful.
Clear your browser's cache. If there's a problem with the cached version of the page you're viewing, it could be causing HTTP 500 issues.
Note: Internal Server Errors are not often caused by caching issues but I have, on occasion, seen the error go away after clearing the cache. It's such an easy and harmless thing to try so don't skip it.
Delete your browser's cookies. Some 500 Internal Server Error issues can be corrected by deleting the cookies associated with the site you're getting the error on.
After removing the cookie(s), restart the browser and try again.
It's not very common, but some servers produce a 500 Internal Server Error when in reality the more appropriate message based on the cause of the problem is 504 Gateway Timeout.
Contact the website directly. Chances are good that the website administrators already know about the 500 error but if you suspect they don't, letting them know helps both you and them (and everyone else).
The best way to find contact information for a website is through a WHOIS search, using the domain name as your search term.
Normally, you need to go into your files and delete the .htaccess. A new one will automatically replace it and it will fix the issue. If you can't find the .htaccess or whichever server file your host is using, contact them to remove it. I hope that helps!
Sure, this is a temporary fix in the Visual Composer plugin itself. However the next update will address it from the Theme side and will not have to rely on Visual Composer adding a check for it.
Locate the following file on your server: /wp-content/plugins/js_composer/include/classes/core/class-wpb-map.php
Unzip and replace it with this file:
http://help.themeva.com/tmp/class-wpb-map.php.zip