Proc_open Createprocess Failed Error Code - 267
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack createprocess failed code 267 the directory name is invalid Overflow the company Business Learn more about hiring developers or posting ads with us php proc_open Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community
Wkhtmltopdf
of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up PHP Warning: proc_open(): CreateProcess failed, error code - 267 up vote 1 down vote favorite 1 A proc_open call like the following is failing with the above error. mean in PHP?1PHP setlocale changed by other scripts under Windows?1PHP LDAP connection authenticates without DN information1Force restarting / alert CMD application if it stops working2Warning in Stanford Tagger.php Warning: proc_open(): CreateProcess failed, error code - 00PHP fatal errors with Wordpress 3.9.1 + store bought theme12NTLM Authentication - Get Windows login, domain and host in PHP1proc_open() fails to resolve localhost on Windows0PHP, yii framework gives error on update/insert, se
Sign in Pricing Blog Support Search GitHub This repository Watch 1,119 Star 13,171 Fork 5,087 symfony/symfony Code Issues 600 Pull requests 152 Projects 0 Pulse Graphs New issue Standalone Server: proc_open(): CreateProcess failed, error code - 267 #6496 Closed luigidt opened this Issue Dec 27, 2012 · 9 comments Projects None yet Labels Process Milestone No milestone Assignees No one assigned 5 participants luigidt commented Dec 27, 2012 Testing http://stackoverflow.com/questions/30296288/php-warning-proc-open-createprocess-failed-error-code-267 on windows XP, version 2.1.6. When running "php app\console server:run" it gives: [ErrorException] Warning: proc_open(): CreateProcess failed, error code - 267 in D:\Source\php\site1\vendor\symfony\symfony\src\Symfony\Component\Process\Process.php line 244 Changing the value of $this->cwd to an absolute path seems to fix the problem. (see http://php.net/proc_open cwd parameter) The class ServerRunCommand sets "docroot" parameter default value as "web/", maybe it https://github.com/symfony/symfony/issues/6496 should be null (so it gets the current dir). stloyd referenced this issue Jan 8, 2013 Merged [2.0][Process] In edge cases `getcwd()` can return `false` #6620 fabpot added a commit that referenced this issue Jan 10, 2013 fabpot mikehaertl/phpwkhtmltopdf Code Issues 3 Pull requests 1 Projects 0 Pulse Graphs New issue Warning: proc_open(): CreateProcess failed, error code - 2 #56 Closed Bilna75 opened this Issue Jul 8, 2014 · 13 comments Projects None yet Labels windows-only Milestone No milestone Assignees No one assigned 3 participants Bilna75 commented createprocess failed Jul 8, 2014 Hi, I'm currently trying to use your wkhtmltopdf but I cannot get passed a Warning call saying : Warning: proc_open() [function.proc-open]: CreateProcess failed, error code - 87 in Path/To/WkHtmlToPdf.php on line 325 I tried with a basic code given in the tutorial but it doesn't work. $pdf = proc_open createprocess failed new WkHtmlToPdf; $pdf->addPage('http://google.com'); $pdf->send(); The error code 87 stands for invalid parameter. Anyone can help me ? Thank you Owner mikehaertl commented Jul 8, 2014 Sorry, I don't use Windows, so I can't really help. Other Windows users seem to have no problem with the library. You will have to play around with proc_open() yourself to find out, what's wrong. I'd try to build a simple PHP script and use more and more complex shell commands with proc_open(). Hope this helps. mikehaertl added the windows-only label Jul 9, 2014 tivie commented Oct 24, 2014 There are a lot of issues with php proc_open on windows. See: https://bugs.php.net/bug.php?id=51800 https://bugs.php.net/bug.php?id=60120 https://bugs.php.net/bug.php?id=65650 One workaround is to run the command yourself using exec(). However, as far as I know, there's no way to get the command woithout actually running it. I've created a pull request that should address this issue. tivie referenced this issue Oct 24, 2