php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #25579 PHP has encountered an Access Violation
Submitted: 2003-09-17 15:28 UTC Modified: 2003-09-22 06:46 UTC
Votes:2
Avg. Score:4.0 ± 1.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: mfenton at learnkey dot com Assigned:
Status: No Feedback Package: IIS related
PHP Version: 4.3.3 OS: W2K3
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: mfenton at learnkey dot com
New email:
PHP Version: OS:

 

 [2003-09-17 15:28 UTC] mfenton at learnkey dot com 
Description:
------------
On our website we get "PHP has encountered an Access Violation" at a memory address, Yes this error is very limited in
saying what the problem is.  Our servers are running W2K3, IIS6.0, PHP
4.3.3 with MSSQL 2000 on W2K3.

Now I've read many people having this problem, some say to just reset
the service, well thats fine, but not when you run a business and you
have many users online at all times.

Others said that there might be a problem using the php4isapi.dll and
using php as cgi fixes there issue, also read that there might be a
problem with the ODBC dll to connect up to the MSSQL database.  There
isn't a fix for this (at least that I have read).  In most posts the
quick solution is to either upgrade to the newest version or there isn't
enough information.

We have recieved this error while in our Userend and our Backend.

This is a persistent problem for our website, this needs to be addressed
ASAP.  Any more information that will be helpful in determining the
solution to fix this problem I can provide upon request.  Thanks for the
help.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-09-17 18:49 UTC] wez@php.net 
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.


Please read the link above, and give us more information.
So far, your report is the equivalent of saying

"I have this really complex set of software, that links to some other complex software.  I also wrote some code that does some stuff, and we get an error every so often".

Until you can provide some clues, keep this report set to feedback, as it means we are waiting for your input.

May I remind you that there is no warranty for PHP and that we explicitly warn you that running PHP ISAPI in production under windows is not recommended in our documentation.
 [2003-09-22 06:46 UTC] sniper@php.net 
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
 [2004-07-23 11:36 UTC] floogman at floor-loogman dot nl 
I've experienced this bug on a similar platform (MySQL instead of MSSQL) while (due to) using sessions. When ending the session (through setcookie with expiration time zero) every next call to *any* PHP page gives a access violation error. The error stops showing when a cookie is set again (session_start).
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Apr 19 22:01:28 2024 UTC