I have a few Drupal sites (PHP) around on Windows shared hosting. I frequently run into IIS 7 errors when re-installing an entire site at which point I'm totally stuck. Then I have to open a support ticket with my hosting provider which takes a while to get resolved (a couple of hours) and the never tell me what they did to fix it. I'm looking for more resources or checklists to narrow things down and try to resolve the issues myself (and don't lose hours).
The errors most often contain these bits:
Module: FastCgiModule
Notification: ExecuteRequestHandler
Handler: PHP_via_FastCGI
There's also an error code but usually that's just 0 (0x00000000).
I only have access by FTP and and a web administration tool (WebSitePanel if it makes any difference). Most of the time uploading a testpage which dumps phpinfo() does work so I have more info available...
There is no way for you in WebsitePanel to get more information about an exact problem. Your web hosting provider may need to check server logs -> Application logs from their server and find out root cause of this problem.
Related
I have two servers, a test server running Windows 7... and a prod server running Windows Server 2008. (Yeah, it's unfortunate that they're different OS's.)
For months now, they've been running on PHP 5.4.1.4.
I decided to upgrade them to PHP 7. Everything went completely fine with the test box. But of course, it doesn't get much traffic.
On the prod / Windows Server 2008 box, it seems like, web apps would run for a minute or two and then show "500 error". I could refresh and sometimes they'd work again, sometime it'd take a few minutes.
Nothing is/was getting written to the NEW PHP error log (even though IIS's PHP Manager section showed that we were pointed to the correct INI and the correct log file).
The webserver failed request logs simply indicated that FastCGI was failing because of too many 500 errors.
I checked Event Viewer and I would see application crashes that would point to php_soap.dll.
Now, that file is THERE and it's the same size as the one I have over in non-prod.
Still, I thought perhaps it was because my scripts were getting 500 errors for a valid reason. So I investigated one of them. Confirmed that it was an exact match to a working one on the test box. Refreshed it...and it worked fine. Refreshed some more, 500 errors.
So, finally, I went into IIS Manager -> PHP Manager and disabled the SOAP extension.
I then STOPPED seeing the massive number of failed requests and I stopped seeing the 500 errors... for everything except the one script I have that makes SOAP calls.
I tried copying the dll from the test box over to the prod box. Enabled the extension again in PHP. The issue returned. So, I've pointed us back to the 5.4.1.4 config for now.
Any ideas on how I might figure out why this dll is causing issues and/or how to fix it?
Thanks!
-= Dave =-
I know this is old now but I had a similar problem and it turns out that the cached WDSL files are not binary compatible between versions of PHP.
By default in php.ini the SOAP module has caching enabled. In order to avoid a crash you'll either need to clear the current WDSL cache or change the cache location for the new PHP install.
Hope that helps...
I think I figured out a fix. I'm not sure why I'm only having to do this on the prod server, though: The directories that my scripts that make SOAP calls are in were set to allow both Anonymous Authentication and Windows Authentication. When I was manually testing things in my browser, it would accept me and run the script as Anonymous.
I suddenly realized a theory: my erroring script was being called by remote desktop gadgets...so it was probably defaulting too to executing anonymously. But I have another script with SOAP in it that's run by Scheduled Task (as a specific user). I had NOT seen that erroring!
So, I turned off Anonymous Authentication on the directory I was testing and reran my script from my browser. Sure, I had to log in, but it then worked! I checked my version of the Desktop Gadget that calls a SOAP script in that same directory...and it was now working too!
I think the key reason why I did not see this on the test machine is that we really don't have any Desktop Gadgets pointed to those proxy SOAP scripts over there. That, plus I had THOUGHT that my script that runs by Scheduled Task was failing on the prod machine, as I know I saw it throw 500 errors within the first few minutes after I activated PHP7 the first time....and that same Scheduled Task/script DOES run over on the test box.
Thanks!
I've been developing a Laravel 4 site on my work machine for over a year. Today I began receiving a The connection to localhost was interrupted error whenever I attempt to access the site. At the moment I'm just trying to find applicable log files that might tell me what's failing, and would appreciate suggestions from those more versed in tracking down this kind of failure. You'll see one possible cause below, but I still need to find some error logs to have any idea how to fix it. Here are some pertinent details:
I'm running Windows 7, IIS 7.5, PHP 5.5.1, and Laravel 4.1.23.
The application is accessed via https://localhost/ephy, and IIS is configured to deliver the ephy directory over SSL.
http://localhost/ephy correctly returns a 403 error indicating that the page must be accessed over SSL.
When copies of phpinfo.php (containing just a call to phpinfo() ) are placed in both the root directory and the ephy subdirectory, http://localhost/phpinfo.php executes, while https://localhost/ephy/phpinfo.php returns the connection reset error.
The application itself is executing successfully on the production server, so the PHP code is valid.
Yesterday I installed Office 2013, uninstalled Office 2010, uninstalled Office 2013, and then reinstalled Office 2013 (in that order). I also installed 2 GB of memory, because Outlook 2013 kept hanging.
The site was accessible as of 4pm yesterday, after all of that installation activity was already over.
I've made no changes to the application or the computer configuration since 4pm.
I've restarted the computer several times.
I've checked the files in C:\inetpub\logs\LogFiles , but they don't show any error messages.
So, I know PHP is running successfully and that the issue is specific to serving the application directory itself, but that's as far as I've been able to get. Recommendations on where to find (or how to generate) logs which would indicate what's happening, or any insights into the failure itself, would be appreciated.
Ok, after finally finding the magic combination of search terms on Google (ERR_CONNECTION_RESET localhost iis 7, for those who are curious, the first term being the error message from Chrome specifically), I was able to determine that this behavior can be caused by not having the self-signed security certificate correctly bound to the site in IIS. As I said, the site had been working successfully, but with the software updates I'd done something probably got borked (maybe adding the memory changed the computer's identity such that the certificate was no longer valid? I don't know).
So, I followed the instructions at http://weblogs.asp.net/scottgu/tip-trick-enabling-ssl-on-iis7-using-self-signed-certificates (with a bit of adjustment because apparently the binding has to be done at the default site level in IIS 7.5, rather than at the individual site level), whacking and replacing the existing certificate and SSL binding in the process. The site is now working again on my box.
So, in a nutshell: if you're running SSL on localhost under IIS and you get "connection to localhost was interrupted" messages, try redoing the certificate and binding.
Man, glad that's over...
I'm running a WIMP stack on Windows Server 2012 R2 Standard, and I have a strange issue with IIS: After working for a random period of time (usually from several hours to days), most requests start to give the following error page:
What is weird is that it works for a period of time. Changing the user access settings of web.config or restarting the website both work to resolve the issue temporarily, however it's a recurring problem.
I do realise that WIMP is not the most desirable stack (normally I'd opt for LNMP myself), however our website will be migrated to an ASP.NET app soon, and since we had to do a server upgrade beforehand, we opted into installing Windows on it to make the transition faster.
EDIT: After some testing, changing the NTFS permissions result in getting the same error until the website is restarted. Might have to do something with the issue?
Also, I'm running the website with a pre-selected user rather than pass-through, if that helps.
Recent projects (Shopware, xt:Commerce) contain ioncube-encoded files which force me to use the ioncube_loader extension. Loading this along with the ZendDebugger does work unless I try start debugging. Once the loader is included, debugging doesn't work anymore - even in non-encoded environment (for one Joomla).
System: Windows 7, Zend Studio 10.6, Zend Server CE, Zend Debugger, ioncubeLoader, PHP 5.3+
I already spend several days searching for a working solution (except using inline debug commands). If it means, setting up a unix environment, so be it. But there seem to be problems, too.
Windows Event Log shows an Application Error (1000):
Faulting application: php-cgi.exe, Version: 5.3.14.0
Faulting module: php5.dll, Version: 5.3.14.0
exception code: 0xc0000005
fault offset: 0x00084494
path to ZendServer php-cgi.exe and php5.dll respectively]
Instead of starting a debug session, a download dialog pops up, containg that HTML code
OK
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, admin#example.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additonally, the ZendEnabler.logs shows:
[timestamp] Error: Read data error - unable to get read result. Code 109.<br />
[timestamp] Error: Request for D:/Projects/Joomla3/index.php: Unable to get the response from PHP process
The joomla folder is mapped to a local virtual host http://joomla3.localhost environment and the subdomain added to the hosts file. No problem if i don't start debugging.
Any help is greatly appreciated ;-)
Just ideas
This could be something as stupid as a line ending incompatibility.
Could be a file* permission, php creating files as the wrong user or with wrong privileges.
Try running the system with elevated permissions? !!Caution, permission elevation is an awful solution.!!
Could be a Windows shell association, or content type dispatch issue.
Have you tried reaching out to IonCube's support? They appear to be a commercial product from the top google hit, they should offer support in some manner.
Try Virtualization? Setup a ubuntu or other virtualbox and test functionality in there?
Thats all that comes to mind looking at different parts of your problem. :\ Home something helps.
To resolve this behavior, correct the DNS address in the Internet Protocol (IP) properties:
Right-click My Network Places, and then click Properties.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Type the correct DNS address in the Preferred DNS server box.
Source:
http://support.microsoft.com/kb/261007
Recently my ISP switched our website to an IIS7.0 high availibility cluster. The website is running on PHP5.2.1 and I can only upload files (so no registry tweaks). I had tested the website before and everything seemed to be working, but now the checkout page fails with:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
As error messages go, this isn't very informative. I've tried:
ini_set('display_errors', 1);
ini_set('error_log', $file_php_can_write_to );
but both don't seem to do anything.
Anyone know how to get better debugging output?
Edit : Looks like we have a similar question in serverfault. Check it out
Turning off IIS7 custom errors will allow error responses from your application to be sent to remote clients without being censored by the IIS7’s custom errors module.
You can do this from the IIS7 Admin tool by running “Start>Run>inetmgr.exe”, selecting your website/application/virtual directory in the left-hand tree view, clicking on the “Error Pages” icon, clicking “Edit Feature Settings” action, and then selecting “Detailed Errors”
Source
It's very common when you change server you cannot load your apps. I have solved this problem running php.exe instead of loading your apps on the browser:
1) Run it using the Command line > C:\php\php.exe OR
2) Run Windows Explorer, look for it, and double click on c:\php\php.exe.
3) You are gonna see what DLL's are having conflicts and causing the 500 error.
4) Solve the conflicts finding the right DLL's for your windows version and you should be able to see your apps through the browser.
The best of the lucks.
IIS does this, it's really annoying and I could not find a fix, which is what caused me to switch to an Apache server for my local machine. Unfortunately, if you don't have control over your server, the best you can do is either test it locally on an apache set up or ask your host to allow the error messages.
I did some googling, thisthis looks like what you need. Wish that was around when I was trying to get IIS running.