Hello.
Today is truly a glorious day. Yes today, some several weeks of struggle and strife have come to an end. After terrific hardship suffered at the hands of a terrible depot I can now say that I xxx xxxx have persevered. My computer is now in a state not unlike it was in at the beginning of these troubled times. I may be older. But I am also definitely wiser. Having had to rub bellies with the darkest of vermin I have learned much about thier habbits and idiosycracies. Today friends and loved ones, today my computer works again!
I will give detail about my trial and tribulations when I have recovered from the effort of perseverance.
Thursday, January 22, 2009
Tuesday, January 13, 2009
Freakin IIS Start Website
Ok, so here we go a real post!
I've been using the visual studio development server to run an app that I'm building using FubuMVC. For some reason I was getting some rather strange behavior and I remember that Chad had said that the vs dev server is a FPOS and that I should use IIS so I switched over only to receive this retarded message.
Unable to start debugging on the web server. The server does not support debugging of ASP.NET or ATL Server applications. Click Help for more information on how to enable debugging. You may also want to refer to the ASP.NET and ATL Server debugging
well after searching high and low and trying all sorts of BS I started digging in IIS (7) and found that the Default Web Site was not started and in fact bloody well wouldn't start. So back to the freakin google and I find that perhaps my port 80 is being used and that if go to a command prompt and type NETSTAT -ano I could see a list of all the ports being used. Sure enough port 80 is being used by a PID 1928. To see if that is truly the problem, I change the bindings in IIS7 (hyperlink on the right side of then now extremly cluttered iis screen) from port 80 to port 8080 and indeed that works.
So what the hell is PID 1928 well I don't know so I go to Task Manager and on the process tab I select view -> select columns and check PID. That ought to do it I think, but pid 1928 doesn't show up. Well it's back to the interweb for some more of the google and I find out about a program called Process Explorer This is essentially Task Manager on steroids and, well, frankly I like steroids. This thing is pretty cool and has way more colors that TM and it actually shows me my blasted PID. It turns out that I have Apache server running for some freakin reason. I kill the process and pow the Default Website starts right up!
So there you have it I have posted on something that might be helpful to someone if they can get through all the prose to the meat.
I've been using the visual studio development server to run an app that I'm building using FubuMVC. For some reason I was getting some rather strange behavior and I remember that Chad had said that the vs dev server is a FPOS and that I should use IIS so I switched over only to receive this retarded message.
Unable to start debugging on the web server. The server does not support debugging of ASP.NET or ATL Server applications. Click Help for more information on how to enable debugging. You may also want to refer to the ASP.NET and ATL Server debugging
well after searching high and low and trying all sorts of BS I started digging in IIS (7) and found that the Default Web Site was not started and in fact bloody well wouldn't start. So back to the freakin google and I find that perhaps my port 80 is being used and that if go to a command prompt and type NETSTAT -ano I could see a list of all the ports being used. Sure enough port 80 is being used by a PID 1928. To see if that is truly the problem, I change the bindings in IIS7 (hyperlink on the right side of then now extremly cluttered iis screen) from port 80 to port 8080 and indeed that works.
So what the hell is PID 1928 well I don't know so I go to Task Manager and on the process tab I select view -> select columns and check PID. That ought to do it I think, but pid 1928 doesn't show up. Well it's back to the interweb for some more of the google and I find out about a program called Process Explorer This is essentially Task Manager on steroids and, well, frankly I like steroids. This thing is pretty cool and has way more colors that TM and it actually shows me my blasted PID. It turns out that I have Apache server running for some freakin reason. I kill the process and pow the Default Website starts right up!
So there you have it I have posted on something that might be helpful to someone if they can get through all the prose to the meat.
Subscribe to:
Posts (Atom)