We have a laravel app (Version 5.5*) deployed in WIndows Server 2012 R2. But our development stack is LEMP. Same codebase works fine in development STACK but fails in WINDOWS SERVER.
Problem:
In our App, there is a REPORT DOWNLOAD queueable job which reads data from database table and generates an excel file using box/spout package(version 2.7) depending on user input date range (daily,weekly,monthly, etc) .
When running the queue:work command from cmd as administrator,
$writer->openToFile(‘path/to/file’) throws an error : failed to open stream : no such file or directory.
See this image for code snippet throwing error
Solutions I tried:
Setting right permissions(full control Read & write) for Storage folder of my project (For Users, IIS_IUSRS,IUSR)
Setting right permissions(full control Read & write) for C:windows\Temp folder (For Users, IIS_IUSRS,IUSR)
Created symlink for storage folder inside public
FYI:
OS: windows server 2012 r2
PHP: 7.2*
Laravel: 5.5.*
box/Spout package: 2.7.*
** AT LAST GOT THE SOLUTION AFTER GOING THROUGH ANSWERS OF OTHER QUESTIONS RELATED TO THIS PROBLEM **
You can follow the following procedure:
Go to IIS Manager
Select your desired project (For example: myexampledomain.com) listed under Sites
Go to Security tab and you'll see the users listed with their permissions on the folder.
Now, click Edit button to go to a new window and click Add. In the text box,type IIS AppPool\MyApplicationPoolName.In our example it should be IIS AppPool\myexampledomain.com.
Click Check Name and you'll see the test change with underline.
Click Ok. Add the appropriate permission(Modify,read,write) to the newly created user.
That's it!!!
Thanks to all for responding.
Problem:
I want to be able to debug my symfony2 project. I would like to be
able to set a break point in my code, run remote debugging and be
able to step through all the break points in my code as I interact
with my application.
Background information and current setup:
The IDE I am using is phpstorm.
Apache and mySql server are running on my vmware player.
Xdebug is installed on vmware player.
I currently connect to my project through my vmware players ip
(i.e 172.16.48.1/app_dev.php). At this point I interact with my
application normally and develop.
What I have done so far
I followed the tutorial but have not had any luck.
I really confused by most of the tutorial but followed it as best as I could. I do not think the bookmarklets were working correctly when following the instructions.
I also watched a webinar or two on remote debugging and it still was not completely clear to me what I need to do to step through my code.
Question:
Can someone provide a step by step tutorial of what I need to do to
setup remote debugging so that I can launch some remote debugging
session through phpstorm that will open my web application and as I
navigate through my web application my break points will be hit?
i've just finished setting up my local symfony2 app and phpstorm debugging with Chrome, here is what i've done:
1) config xdebug in php.ini on the server and restart web server (or php-fpm):
[xdebug]
zend_extension="**location to xdebug**/xdebug.so"
xdebug.remote_enable = 1
; use port 9009 because php-fpm uses 9000 by default
xdebug.remote_port = 9009
xdebug.idekey = PHPSTORM
2) install xdebug extension
https://chrome.google.com/webstore/detail/xdebug-helper/eadndfjplgieldjbigjakmdgkmoaaaoc
3) setup xdebug exteions. in chrome://extensions find Xdebug helper and click options. there select IDE key to PhpStorm. (this will essentially set xdebug.idekey to PHPSTORM for that particular session)
4) now the trickiest part, connecting from PhpStorm.
you have to setup PHP Remote Debug debug configuration.
in the toolbar, next to the debug button, you have drop down field with the first option Edit configuration. it opens Run/Debug Configurations.
there click the + button and add PHP Remote Debug.
specify your name, server and Ide key = PHPSTORM.
click Apply and Ok (i never know which one so i always click both, just in case)
now the dropdown in the toolbar will show your newly set remote server, run button (green arrow) will be disabled.
click Start Listen for PHP Debug Connection
click that green bug icon to start debugging
Debug view will open with 2 tabs: Debugger and Console (selected by default)
change the tab to Debugger and you will see: "Waiting for incoming connection with the ide key 'PHPSTORM'"
open your browser
navigate to your server url
activate Xdebug helper extension (clicking on that gray bug in the url bar) it will turn green
to check that everything is ok, open Chrome console, tab Resources -> Cookies -> your server. and verify that cookie XDEBUG_SESSION with value PHPSTORM was created (this is what actually activates xdebug remote debugging in php)
now refresh the page and quickly alt-tab back to PhpStorm (or arrange your windows so you can see PhpStorm while refreshing browser)
in your Debug view and Debugger console you will briefly see "Connected"
TADA!
create couple of break points in controller (dont use AppKernel.php or other symfony2 specific files as those get compiled and are not called, even in dev mode)
added 5.1.2015
official tutorial can be found here:
https://confluence.jetbrains.com/display/PhpStorm/Profiling+PHP+applications+with+PhpStorm+and+Xdebug
Everything worked, up to the point where I set a breakpoint. Since Symfony2 is a front controller, it doesn't know which corresponding file matches the breakpoint.
I tried to setup path mappings, but to no avail.
I need help setting up phpstorm (4.0) with XAMPP which is at the default location c:\xampp\htdocs. I create all my projects at c:\xampp\htdocs\projectname.
Here are the things I have already done:
Setup the PHP interpretator by going to settings and then PHP (main menu)
Go to PHP > Servers and then
To setup run configuration I have the done the following:
Now when I run using the above configuration it just takes me to localhost in my browser, instead of the file I am editing (http://localhost instead of localhost/myproject/myfile.php).
What am I missing? I read the help topics of phpstorm and googled a lot but still couldn't figure it out.
Turns out you don't need to set up run configuration. The answer lies in setting up the mapping in the deployment tab in settings.
(assuming that you are creating your projects in c:\xampp\htdocs)
To do that go to settings (Ctrl + Alt + S) and then choose deployment:
Under mappings tab, it should look like this:
And after that you can view the file in the browser through this menu:
Check the answer to this question. If you need to debug, the recommended way to do it is zero configuration debugging.
I cannot start my website from Visual Studio 2010 anymore.
For a few days I cannot start my project in a web browser using F5. When I open my web application directly by typing the same url 'http://localhost/Default.aspx' everthing works fine.
When I run the project (F5) a new webbrowser starts, but after a few seconds it is stuck and Visual Studio gives an error dialog:
Microsoft Visual Studio
Unable to start program 'http://localhost/Default.aspx'.
OK
When I run the project in release mode it gives an extra error:
Microsoft Visual Studio
The following module was built either with optimizations enabled or without debug information:
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\6552bec6\694bce32\assembly\dl3\8c9bd8d8\fb1d75cb_af26cc01\[name].Presentation.DLL
To debug this module, change its project build configuration to Debug mode. To suppress this message, disable the 'Warn if no user code on launch' debugger option.
OK
I have already repaired, removed and reinstalled Visual Studio 2010, I've tried using different browsers (including Chrome and Firefox), used different aspnet_regiis.exe options, etc. etc.
Nothing helps, and yeah now I'm stuck pulling hair out of my head ...
Anyone any idea how to solve this?
Does it work if you start it with [CTRL]+[F5] which runs without the debugger?
If so, then you have an issue with the debugger auto-attaching to the web server. I would check that debugging is enabled for your web project - a warning that usually crops up automatically from VS when it detects that a project is not built in Debug mode.
This is not as simple as switching the project configuration over to Release, because the DLL that the debugger is moaning about is one of the dynamically generated ones originated by Asp.Net itself.
Typically you should have, in your web.config:
<configuration>
<system.web>
<compilation debug="true" >
</compilation
<system.web>
<configuration>
(Along with any other stuff in <configuration> and <system.web> nodes).
There's also the possibility that Asp.Net debugging is not, for some reason, enabled.
Check out this msdn article on debugging asp.net applications in VS2010 for more information.
Note that if this is VS010 express, then you won't be able to debug - as confirmed by the aforementioned link; but since you way it used to work then I guess that's not your problem.
Update
Since that hasn't worked - you can try emptying the Temporary ASP.Net files folder. Easiest first is to do an iisreset. Then navigate to C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files and delete everything in it. I've had issues in the past where the Asp.Net binaries don't get refreshed and so when I'm debugging it moans that the files are out of date.
Change the View Browser to another browser. Run the view in browser or debug, then change back to original browser should work after that.
Had same problem, answer for me was to remove Avast Free AV. Everything worked for a year with avast free up until a week or so ago, uninstalling it fixed the problem.
I had this exact problem with Visual Studio 2008. The solution was to set the default web browser that VS uses to a real browser (e.g. IE) and not the "Internal Web Browser".
Right click on an ASPX file in your project and select "Browser With...". This lets you select the default browser to use when you select the "View in Browser" option and for when you debug/run the app (this is key).
Select your favourite browser (i.e "Internet Explorer") and click on "Set as Default". Do not pick "Internal Web Browser".
Debug away! Your app should come up in your browser now and debug as normal.
the solutions for me is to test with 127.0.0.1 in place of localhost. and all goes well for.
so the problem come from the host resolution name, to solve it please proceed like :
open cmd and then tape : %systemroot%\System32\drivers\etc\
open hosts file with notepad and the look for localhost ligne(you'll find 0.0.0.0 befor it )
change the 0.0.0.0 with 127.0.0.1 at all lignes with localhost .
I solved in this way:
Right click on a aspx page
Browse with set internal browser as default
Remove the previous default browser
Add %programfiles(x86)%\internet Explorer\iexplore.exe
Set this choice as default
For me I just did a Build /ReBuild on the project level and it started working!!!
I had the same problem. When I debug my code it says:
Unable to start program 'C:\homework.exe'. this system cannot find the file specified."
I'm using Microsoft Visual C++ 2010 Express but when I made a new project by the following steps:
Open C++:
Press new project
Press win32
Press win32 Console Application
Rename it
Click next
make sure: that the application type is console application
additional options: empty project*
Press Ctrl+Shift+A
In Visual C++/Code section press C++ File (.cpp)
rename it and press add
It works fine with for me now.
Please set your page name e.g Default.aspx revert to parent in IIS configuration
I'll share my experience with this same problem. This is not a solution, but someone may be able to figure out the problem from my particular experience.
I've been having this same problem for a few weeks now. (I don't know what changed on my system.) I do not run as local admin, because we are not allowed to have admin privileges on our PCs where I work.
Until today, I could expect F5 (Start Debugging) to start up a new local VS web server, open an IE window, and then issue an "unable to start program http://localhost:nnnn/Login.aspx" and "access is denied" error pop-up. If I closed the IE window, waited a few seconds, and then clicked F5 again, it usually started up my web app in debug mode just fine from that point on.
But today, that all changed. I did not change any configuration on my web app, which has been running fine, but I did add a couple of more classes to one of my subprojects. At this point, I could never get past the "unable to start program" message. I could run my app without debugging, but that was rather pointless. I even tried attaching to a running (non-debug) IE process, but that did not work.
Finally, I modified some of the properties in the WebAppName >Web >Servers screen. Specifically, I enabled "Specific port" for a specific HTTP port (which VS had been using all along), and I disabled "NTLM Authentication". I also enabled "ASP.NET" in the Debuggers section. Some of these I first clicked, then unclicked, then clicked again, saving in between each click.
This time, running with debug (F5) worked.
After running several times, I still usually get a "unable to start" error the first time after a recompile, but I can still usually get a debuggable running app to start after the second or third try. At least I'm back to where I was yesterday.
I suspect it has do with VS reloading its execution profile, and also probably something to do with permissions (since I cannot run as admin).
I'm using VS2012 with an ASP.net app that was written using VS2003... I've tried everything to get the IE page to open automatically when I select F5, or even Ctrl+F5... Haven't been able to get anything to work... However, I have stumbled upon a very poor work-around. When I select debug and I get the 'Unable to start program...' msgbox... I noticed that on the icon-tray I get a msg saying local-host has started
You'll notice a picture that the msgbox is pointing to:
Well, if you right click it, you get three options:
When you select the first: 'Open in Web Browser', it will open IE with the page your working with...
Like I said, it's a very poor work-around... but it works. This isn't an issue when I select debug using 'Chrome' or the page-inspector... But they have their own issues.
Try to turn on Bypass proxy for local addresses.
First you can go to your browser settings-> Change proxy Settings-> Connection-> Lan Setting and just check bypass proxy for local addresses.
If this solution don't work then also copy the following code check your web.config file for settings to bypass firewall:
<system.net>
<defaultProxy>
<proxy usesystemdefault="true" proxyaddress="http://proxy:port" bypassonlocal="false" />
</defaultProxy>
</system.net>
I easily resolved this problem by enabling script debugging in the browser.
When I ran into this problem (using IE 11) I noticed that iexplore was open about a hundred times in the task manager. After killing them all I was able to open my project just fine.
Since then, I have made a .bat file with this code:
taskkill /F /IM iexplore.exe /T
so now I just run the .bat when I get that error.
(alternatively you could run that code from the cmd)
I just ran into this problem in Visual Studio 2013. I had to enable Anonymous Authentication.
Click on the project node in solution explorer.
Hit F4 to show the properties window.
Change the Anonymous Authentication option to Enabled.
I have a number of machines, all of which have Visual Studio installed, where something (presumably visual studio) is overriding the proxy settings: setting up localhost and some random port for both HTTP and HTTPS. In the "Do not use proxy server" box, it puts <vsts-proxy-installed-indicator> which is presumably a tag so it know it's done it.
This occasionally prevents browsers from working on my desktop, and more recently, changed it on our build server which caused the code signing step (which connects to an external timestamp server) to fail all day until I finally found this proxy issue.
What is changing these settings? Why is it changing them? How do I turn it off?
Note, there is a serverfault question about this as well: What is inserting “vsts-proxy-installed-indicator”? but since this is a Visual Studio-specific question, I thought it might be better to ask here.
This happens because you've enabled "ASP.NET Client Proxy for IntelliTrace and Test Impact" in the Test Settings.
To disable - VS2010: Open the menu Test > Edit Test Settings > (select the current active test settings), select Data and Diagnostics and disable the mentioned setting.
To disable - VS2013: Double click on the enabled* .testsettings-file in the solutions explorer, select Data and Diagnostics and disable the mentioned setting.
*) You'll find which one is enabled (if any) under TEST> Test settings
Keep <vsts-proxy-installed-indicator> in the exception list along with the other proxy and exception settings. This will solve the issue.
It looks like running mstests (e.g., from the "Test List Editor" tab triggers this! Can someone reproduce?