ID: 16411
User updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: MSSQL related
Operating System: Windows 2000
PHP Version: 4.1.2
New Comment:
Database connections are all transient.
In the original code, I did not close the connections because php would
do that at the end of script. But as I was in doubt, I later made a
close right before calling the function header() but the same problem
happened.
I also made another test: in the script I just opened and immediately
right after colsed it. The same bug happened.
When I removed that tiny chunk of code, every thing worked just fine.
Previous Comments:
[2002-12-02 19:57:52] [EMAIL PROTECTED]
Database connections are all transient.
In the original code, I did not close the connections because php would
do that at the end of script. But as I was in doubt, I later made a
close right before calling the function header() but the same problem
happened.
I also made another test: in the script I just opened and immediately
right after colsed it. The same bug happened.
When I removed that tiny chunk of code, every thing worked just fine.
[2002-11-30 20:36:38] [EMAIL PROTECTED]
What are you doing with your database connections? Are they persistant
(mssql_pconnect) or transient (mssql_connect)? Do you close your
connections explicitly (mssql_close) before the end of your script?
vielina, your connections will be closed each time as you are running
under the CGI.
[2002-11-21 03:29:36] [EMAIL PROTECTED]
I have this problem too.
[2002-06-20 15:19:45] [EMAIL PROTECTED]
Same problem, slightly different case...
win2000 running php.exe 4.2.1 (and mssql 2000)
seems to happen mostly during redrects like...
header(Method: GET);
header(Status: 302 Moved);
header(Location: . $ABSOLUTE_URL);
some claim they solved this problem by applying the workaround by
microsoft (Q160422).
others say they have fixed this by blanking out the doc_root in
php.ini
I still have this problem
[2002-06-02 22:14:18] [EMAIL PROTECTED]
I did that but it still did not work. I further tested another way: I
left every thing as it was, except that I did not open an MSSQL
connection. The script worked pretty well. When I changed it back, the
same type of bug happened. When looking at phpinfo, even with the
latest php version (4.2.1) I saw that in the MSSQL support section, the
MSSQL library version was 7.0. Is this a potential source of that bug?
Loi Le V.
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/16411
--
Edit this bug report at http://bugs.php.net/?id=16411edit=1
