oh.... windows..... >:( >:( >:( >:(
2019-04 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4493470) broke the forum.
Release Date:
April 9, 2019
Version:
OS Build 14393.2906
QuoteNot found: '/index.php'
But it's there..... right where it always was.
Other websites asp.net and html
running on the same server still work.
Bill Gates what did you do to my server?
I try running phpinfo.php and it says Not found >:(
Running IIS? What version of PHP?
Did you install PHP manually?
PHP: 7.1.26
Server version: Microsoft-IIS/10.0 (microsoft server 2016)
As far as I can tell, the server has stopped running php
- system variables still has c:\php is in the path
- pathext still has the .php
Even within the c:\php directory, I can't get any thing to happen.
I am new to php, so don't know what to do next.
here is something...
I type php /? and get
QuotePHP Warning: PHP Startup: Unable to load dynamic library 'ext\php_mysql.dll' - The specified module could not be found.
in Unknown on line 0
Could not open input file: /?
just looked in c:\php\ext and I see that I do not have php_mysql.dll
but I do have php_mysqli.dll in there.
So maybe windows update is not the problem and maybe it was something I did wrong that only showed up when I restarted the server?
Open up your php.ini and find the line php_mysql.dll and comment it out. That extension is no longer part of PHP 7.0
we are getting there, thanks for the help....
I commented out
but now I get this, so I must have made another mistake..... oh... and I can not find a backup of php.ini.... I feel so dumb...
PHP Parse error: syntax error, unexpected 'and' (T_LOGICAL_AND), expecting end of file in C:\php\php.ini on line 183
Attach your php.ini
I would also check your event viewer after your php.ini is fixed.
attached
Try
;D :D :) ;)
[/color]
THANK YOU VBgamer45 !
Just in case other people have read this far.....
Make backups, backups, more backups.
I had been making changes to php.ini based on recommendations I found on the internet. Well, I guess those recommendations were not dated, or I didn't notice. But it wasn't Bill Gates fault this time. It was me. I did something I shouldn't have and it did not come to light until today when the server had to get restarted for the Windows Server updates.