php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #17563 PHP has encountered an Access Violation at 77XXXXX
Submitted: 2002-06-02 04:14 UTC Modified: 2002-12-23 01:00 UTC
Votes:29
Avg. Score:4.4 ± 1.0
Reproduced:24 of 24 (100.0%)
Same Version:4 (16.7%)
Same OS:17 (70.8%)
From: stanley at in2nett dot com Assigned:
Status: No Feedback Package: MSSQL related
PHP Version: 4.2.1 OS: WIN2K
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2002-06-02 04:14 UTC] stanley at in2nett dot com
I'm using MSSQL
when I use the SQL statement as "SELECT * FROM xxxxxxxxxxxx"
I will recieve that error, badly, but if I replace the * with whatever field I need, I can avoid this error.

Not suppose to be like that, but well, I just found this way works.......

Stan.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-06-02 04:52 UTC] stanley at in2nett dot com
I'm using MSSQL
when I use the SQL statement as "SELECT * FROM xxxxxxxxxxxx"
I will recieve that error, badly, but if I replace the * with whatever
field I need, I can avoid this error.
(notice my table has over 25 fields, small table seems working fine)

Not suppose to be like that, but well, I just found this way
works.......

Stan.
 [2002-06-02 08:15 UTC] mfischer@php.net
Duplicate
 [2002-06-08 04:46 UTC] stanley at in2nett dot com
Ok, I found this error more specifically.
This error is actually from one of my database field, is "smallmoney" allow null. but I have no idea why it have this error, because there are exactly same datatype in the same table. I'll try to test more and see.
 [2002-06-08 04:54 UTC] stanley at in2nett dot com
GUYS!!!!!! Found it, as I said, there is one field have error, I remove that field and add another field that is exactly the same datatype and everything and the problem solved.

Try it out.
 [2002-06-08 05:05 UTC] mfischer@php.net
That's  a start (and probably not a duplicte). But we need more information. What vrsion of MSSQL ? And type was this field of ? Can you reproduce this by creating a second field exactly as the first which crashes, which crashes too ? Please be as detailed as possible about the database setup and the field in general (so someone with the appropriate environment can rebuild this scenery), thx.
 [2002-06-08 20:28 UTC] stanley at in2nett dot com
Server Version:  MSSQL Server 2000
Operating System: WIN2K Server

Database Details:
   The error field is smallmoney, allow null.

Error Solution:
   I've tried rename it with other field which is also 'smallmoney' and 'allow null', but problem does not solve this way. The only way to solve this problem is to remove that field and create another new field again.

Notice:
   Notice that the field works fine inside the MSSQL server's 'Query Analyzer', no error occur inside MSSQL server itself, but it produce error with the PHP engine.

How does the bug act like:
   This error might not hang the whole php engine in first few times you recieve the message "PHP has encountered an Access Violation at ########", but it will eventually hang when you load that page few more times.
 [2002-08-25 00:51 UTC] ali_ashrafzadeh at hotmail dot com
Hi

I Have this problem Too

I use an Odbc conennection on Win2000 prof and IIS ver 5
I try to fetch some data from my database by this lines :
      $query="Select username,name,family,Sex,pic,pic_type 
      ,about from [users]";   
      ...........
      ........... 
      $username = odbc_result($result, 1);
      $name     = odbc_result($result, 2);
      ............
this page is work probebly at first time but after some refreshing I recive "PHP has encountered an Access Violation at XXXXX" only at this page and other .php page is work probebly;
I install PHP on my computer in ISAPI mode
in my users table "Pic_type" and "about" allow null 
I rename these fieldes but not effect .
you say  I remove this field's and add them again  ?
is it effective?
I try it but not sure
thank's
 [2002-08-25 23:54 UTC] stanley at in2nett dot com
Yes, try that first, after recreate the data field, I have no problem afterwards. You can use the mssql.dll if you 
want~ I use that in all time, I don't like ODBC,
 [2002-11-30 20:39 UTC] mail-php dot net at kimihia dot org dot nz
Can you please be very specific about your table and column names. The ODBC driver doesn't handle odd names very well.

There's a big difference between:

SELECT * FROM froo

SELECT * FROM [FR oO]
 [2002-12-07 01:43 UTC] iliaa@php.net
Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip


 [2002-12-23 01:00 UTC] php-bugs at lists dot php dot net
No feedback was provided for this bug for over 2 weeks, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
 [2003-06-19 08:18 UTC] matsd at sssk dot se
Was this bug corrected?  

I installed PHP 4.3.2 on a Win2kServer running IIS5 but still get this error.  The application I'm working on uses MySQL 3.23.45; on the same machine an ASP/MSSQL application is also running.

regards,
        mats d.
 [2005-03-24 16:37 UTC] bugs dot php dot net at ghort dot wz dot cz
I first noticed this error with PHP5 running as ISAPI on IIS 5.1 on WinXP (SP1, now SP2). If configured as CGI, there is no prob. Before PHP5 I never noticed this error.

Ghort*
 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Fri Aug 23 14:01:27 2019 UTC