Edit report at https://bugs.php.net/bug.php?id=42715&edit=1
ID: 42715 Updated by: ssuffic...@php.net Reported by: pradeep at value-one dot com Summary: Consistent Connection Failed to MSSQL 2000 server -Status: Assigned +Status: Closed Type: Bug Package: MSSQL related Operating System: Windows 2003 PHP Version: 5.1.5 Assigned To: fmk Block user comment: N Private report: N New Comment: Please try using this snapshot: http://snaps.php.net/php5.4-latest.tar.gz For Windows: http://windows.php.net/snapshots/ I think we can drop support for SQL Server 2000. It also looks like this was related to a server configuration error. Bug closed. Previous Comments: ------------------------------------------------------------------------ [2007-12-03 09:50:14] pradeep at value-one dot com Well Soulax I did following to resolve my issues. Hope all these will resolve your issue as well. 1. Synchronize your server time by any INTERNET time servers. Then restart your server so that time will synchronized between your database server and web server. 2. You need to patch your SQL Server 2000 with latest Service Packs at least SP4. 3. You may require Windows 2003 Service Pack 2 for IIS6 issues. 4. After above patching, restart your server. 5. You need to have Updated MSSQL Client Library which has not shipped with default PHP package. you can download this library from http://webzila.com/dll/1/ntwdblib.zip. Replace existing NTWDBLIB.DLL from your PHP folder with downloaded file. Hope doing all step will work. :-) ------------------------------------------------------------------------ [2007-11-30 21:39:44] soulax at email dot com Any updates on this? Im having the same exact symptom. (Web Server) OS: Windows 2003 PHP: 5.2.4 WEB SERVER: IIS6 trying to connect to a Windows 2003 box on the LAN running SQL SERVER 2000 via mssql. It works, then doesn't connect, then works, and so on and so forth. It used to work fine, perhaps some windows updates caused this? I know im using a mish mash of OS's and App's, but it's all i have available via my IT department. ------------------------------------------------------------------------ [2007-10-02 15:06:16] pradeep at value-one dot com Most ppl from community has told me that the debug builds are not a GOOD CHOICE for production applications (or say mission critical). May I know when this bug been resolved in stable version(s)? In addition, in my previous working I rolled back my all windows 2003 pactches (SP2 and Security Patches) then again SQL Server is able to communicate with PHP while I think all these patches are very essential for my server. What is the HACK? What I had missed or which service or patch creating this problem? I appreciate if someone could work on it. ------------------------------------------------------------------------ [2007-09-22 15:30:48] pradeep at value-one dot com Thanks Jani I had already implemented PHP 5.2.4 Snapshot of developer build dated 19 September, 5:00PM but I face the same problem. The problem still lying but when I move my database server from this machine to another machine (i.e. Install and restore my MSSQL 2000 databases to different machine) then all works fine with my previous PHP as well as suggested PHP debug build (latest snapshot). I am wondering what is the exact cause of problem? if this is PHP bug then why is it not repeating when both Web Server (IIS) and Database Server (MSSQL) are on different machine. One more question, Is this debug build affect my production application (critical for my enterprise) or Does any debug build have any security vulnerability? I am asking this because right now my application running with suggested Snapshot build. ------------------------------------------------------------------------ [2007-09-21 09:07:34] j...@php.net Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows (zip): http://snaps.php.net/win32/php5.2-win32-latest.zip For Windows (installer): http://snaps.php.net/win32/php5.2-win32-installer-latest.msi ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=42715 -- Edit this bug report at https://bugs.php.net/bug.php?id=42715&edit=1
