Bug #38719 [Fbk->NoF]: COM Error during accessing function VirtualMachines
| From: | php-bugs at lists dot php dot net | Date: | Sun, 16 Feb 2020 04:22:05 +0000 |
| Subject: | Bug #38719 [Fbk->NoF]: COM Error during accessing function VirtualMachines | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-225588@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=38719&edit=1
ID: 38719
Updated by: php-bugs@lists.php.net
Reported by: techscorpio at lxlabs dot com
Summary: COM Error during accessing function VirtualMachines
-Status: Feedback
+Status: No Feedback
Type: Bug
Package: COM related
Operating System: Windows 2003 r2
PHP Version: 5.1.6
Assigned To: cmb
Private report: N
New Comment:
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 "Re-Opened". Thank you.
Previous Comments:
------------------------------------------------------------------------
[2020-02-06 17:54:36] cmb@php.net
First, a com_exception with the message "Source: Unknown
Description: Unknown" is thrown when a dispatch exception occurs,
but the automation server does neither provide a source nor a
description. That means this is a rather generic error message,
which does not tell anything about the root cause. Likely, the
different commenters here have different issues.
Regarding the OP: Microsoft Virtual Server had its last release in
2007, so I assume this issue is obsolete. Am I wrong?
> the script runs ok when i start it from a command window.
> but it gives me this error when i try to run it from a php page:
This hints at some environmental issues (maybe insufficient
permissions).
Regarding the imagegrabwindow() example from the docs: while I
don't get any error or exception, I get a completely black image.
A quick look at the implementation of imagegrabwindow() shows that
the error handling should be improved.
And I think the error handling of this particular com_exception
should also be improved, but that is tracked in bug #51904.
------------------------------------------------------------------------
[2011-08-10 08:22:26] pe dot dolenc at gmail dot com
Hello guys,
I've had similar problems trying to start application in the background, but
always getting the Source: Unknown error.
For me the cause was, that backslashes weren't escaped, so please double check
your code.
------------------------------------------------------------------------
[2009-05-27 02:26:15] jstel at 126 dot com
i get same error .
the error code is
Fatal error: Uncaught exception 'com_exception' with message
'<b>Source:</b> Unknown<br/><b>Description:</b> Unknown' in
D:\xampp\htdocs\snap\snap.php:4 Stack trace: #0 D:\xampp\htdocs\snap\snap.php(4): unknown() #1
{main} thrown in D:\xampp\htdocs\snap\snap.php on line 4
my source code is from demo of
http://cn.php.net/manual/en/function.imagegrabwindow.php
<?php
$browser = new COM("InternetExplorer.Application");
$handle = $browser->HWND;
$browser->Visible = true;
$browser->Navigate("http://www.libgd.org");
/* Still working? */
while ($browser->Busy) {
com_message_pump(4000);
}
$im = imagegrabwindow($handle, 0);
$browser->Quit();
imagepng($im, "iesnap.png");
imagedestroy($im);
?>
------------------------------------------------------------------------
[2008-10-04 23:05:16] pykker at gmail dot com
I tried on Windows Vista SP1, PHP 5.2.1 and getting the same error.
Are there any news about this?
------------------------------------------------------------------------
[2007-06-20 02:55:00] jim_1234au at yahoo dot com dot au
Has there any progress, or workaround with this problem ?
I've just tried it with Apache/2.2.4 (Win32) PHP/5.2.3 on a Windows 2003R2 server. The same was
orrucing with PHP v5.2.2.
Jim.....
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=38719
--
Edit this bug report at https://bugs.php.net/bug.php?id=38719&edit=1