I'm able to reproduce this issue with a test case using Apache 2.4, PHP 7.1.12 and Microsoft PHP Driver for SQL Server (php_sqlsrv_71_ts_x86.dll, version 4.3). remove WITH STATS = 1 from BACKUP DATABASE statement.execute sqlsrv_configure("WarningsReturnAsErrors", 0) to change the settings for error handling.But I can see this in php extension at the Wampserver:Īny ideas to what I did wrong or why it don't show up in phpinfo()? I even did restart on wampserver many times and run as an administrator. If I'm in phpinfo() I should see a 'sqlsrv' section in there, but I don't see one, so I guess I did something wrong here somewhere? I have php5ts.dll in my php5.6.16 folder, so I think I have thread safe which is why I am using ts.dll ones. I extracted the dll files to C:wampbinphpphp5.6.16ext.Įxtension_dir = "c:/wamp/bin/php/php5.6.16/ext/" I downloaded SQLSRV32.exe from microsoft. I will post all the information I have so far: TLDR: Close the ports! Think again if this is really what you want to do.After looking so many posts about this problem, I don't understand why it don't work because it should be working. You could also use some cheap VPS and set up SSL certificates for a test domain to encrypt your traffic over the public net.Īnd don't trust random people wanting to look at your webserver, they could just as well look for easy targets. If I were you I would either not forward a port and set up a local name for the server under which I could reach it, or at least set up the webserver on a different machine on the same LAN and port forward that - but not under windows, on linux or bsd. Not to even begin with the problems of exposing a windows machine to the public internet (even if it's for single ports). If configured wrongly, which could well be the case, it could leak out a lot of personal information to the internet, in your case mainly to automated port scanners/attackers. Port forwarding to your PC is almost always a bad idea.
0 kommentar(er)
