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

go to bug id or search bugs for

Bug #13253 COM() generates NULL pointer exception
Submitted: 2001-09-11 16:48 UTC Modified: 2001-09-14 16:40 UTC
From: will at okino dot com Assigned:
Status: Closed Package: COM related
PHP Version: 4.0.6 OS: Windows 2000
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
14 - 11 = ?
Subscribe to this entry?

 
 [2001-09-11 16:48 UTC] will at okino dot com 
I found that COM was giving NULL pointer exceptions for some programs and not others. I tried the following script:

<?
  $quota = new COM("Microsoft.DiskQuota.1");
  $wordpad = new COM("Wordpad.Document.1");
?>

and got:

Fatal error: NULL pointer exception in D:\Inetpub\polytranslive\comtest.php on line 3

I even found that sometimes one instance would work, and another wouldn't, both on the same COM server.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-09-14 16:40 UTC] phanto@php.net 
Wordpad.Document has no interfaces derived from IDispatch thus it can't be accessed through php. 

the error message doesn't say what it is supposed to say, but this is fixed in php 4.0.7. you will get

"C:\devel\developers handbook\test.php(3) : Warning - Unable to obtain IDispatch interface for CLSID {73FDDC80-AEA9-101A-98A7-00AA00374959}: Interface not supported"

now.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Apr 19 15:01:28 2024 UTC