ID: 22403 User updated by: cesararnold at yahoo dot com dot br Reported By: cesararnold at yahoo dot com dot br Status: Bogus Bug Type: Sybase-ct (ctlib) related Operating System: * PHP Version: 4CVS, 5CVS Assigned To: thekid New Comment:
Thanks, this recommendation is obvious. I think that the question isn't find who is doing mistakes, and say "I'm right and YOU are not". I hope we are trying to solve a bug, and sometimes people do mistakes. If you have time to check, I received a message asking to try latest snapshot talking about php5, and I did not see that it was from php5. It was my fault. Anyway, we did a backup and nothing was lost. Now we are running the original version and we'll update over that. As soon as we update it, we'll keep you posted. Is that fine to you ? My question is: are there setting on php.ini-recommended that are necessary to the latest version or not ? Thanks. Previous Comments: ------------------------------------------------------------------------ [2004-01-29 16:53:43] [EMAIL PROTECTED] DO NOT mix different PHP versions with each other. And I didn't ask you to try PHP 5, I asked to try the latest _STABLE_ snapshot, which is still PHP 4. You're now trying to load wrong extensions from incompatible PHP version..please ask further support questions elsewhere. ------------------------------------------------------------------------ [2004-01-29 10:58:26] cesararnold at yahoo dot com dot br Hi, maybe there was a mistake after update to php4-win32-STABLE-latest.zip. After copy the new files over the php root directory, stop and restart the server the same error occured, as reported to you. But, after restart the hole server to make sure the installation was sucessfully, some php dlls were not loaded, indicating that maybe the update wasn't well done. So, this is the reason of the error, and the latest version wasn't fully applied. The original php version was restored, the web server stopped and the latest version applied. When the server is started some dlls does not start, like php_exif.dll, php_gd.dll, ... showing a message that it cannot be loaded. I didn't copy the php.ini-recommeded over php.ini. I'm analysing what changes I need to do on our php.ini to put it like recommended and add our particular settings. Done php.ini, I'll try to restart the web server and check if the dlls can be loaded. Can you please confirm if there are new setting on php.ini-recommneded that will affect the way as php works regarding this bug ? Thanks. ------------------------------------------------------------------------ [2004-01-29 07:48:09] cesararnold at yahoo dot com dot br Thanks, I didn't see that you sent php5 instead php4. Anyway, after restore a backup from original version before install php5 and update it to php4-win32-STABLE-latest.zip the same error happens, as reported yesterday. Including a "echo" command before run the query, it shows: Testing ...PHP has encountered an Access Violation at 01E736C9 Removing the "echo" the "HTTP 500 ..." page is shown. Step by step we can arrive at the destination. Thanks. ------------------------------------------------------------------------ [2004-01-28 15:06:04] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-STABLE-latest.zip ------------------------------------------------------------------------ [2004-01-28 12:15:47] cesararnold at yahoo dot com dot br Congratulations! It seems to be working now, but not for all cases. Instead of a php crash and the web server stopped, a "HTTP 500 - Internal server error" page appears and "The page cannot be displayed". That's fine. But if I put a "echo " command before the query like the following example, the php crashes. If the "echo" is removed, the "HTTP 500 ..." error appears. ... line 098) echo "Testing ..."; line 099) line 101) // select data line 102) $cmd_sql = "exec sp_procedure"; line 103) line 104) if (DB::isError($query = $db_conn->query($cmd_sql))) line 105) { line 106) // get the native backend error line 107) // and the last query line 108) exit($query->getMessage()); line 109) } ... I have two more questions to do about the last update: - on the last stable version downloaded exists a new folder called "ext", that seems to be similat to "extensions". Now we have 2 folders on php directory, with similar dlls. Is that correct ? - why it does not execute the "exit" command at line 108, because (in my oppinion) a error is occuring at the sql command ? is that error code returned or not ? It seems that you are almost arriving to solve the case. Anything alse we can do to help, please advise. Thanks for all your help. ------------------------------------------------------------------------ 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 http://bugs.php.net/22403 -- Edit this bug report at http://bugs.php.net/?id=22403&edit=1
