Could not start IIS.
mnasih
Posts: 4
am trying the system for the first time and am keep geting this below error.
i tried with the local admin and the domain admin , and none of them worked.
Could not start IIS.
RedGate.Profiler.Engine.Exceptions.CannotStartSessionException
at Â
i tried with the local admin and the domain admin , and none of them worked.
Could not start IIS.
RedGate.Profiler.Engine.Exceptions.CannotStartSessionException
at Â
Comments
Could you kindly check Event Viewer for any errors regarding the profiler or your IIS application? There will hopefully be more specifics there on what exactly is causing this "Timed out waiting for port 80" error.
Can I also please check--what operating system are you running on?
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?
there is no warnings or errors in IIS event viewer
the OS version is Windows server 2008 64-bit R2 ent. service pack 1
-If you look at the most recent log file or two (Help>Open folder), are there any errors in them?
-Does it make any difference if you profile on an unused port instead of the original port?
-Are you able to profile any other IIS sites running on your machine?
-Does your site have any bindings on the localhost/127.0.0.1 that you could try profiling instead of the one on 37.99.128.26? If not, could you kindly try setting up the site on a different port on localhost (no hostname) to see if profiling that works?
(Also, just a note: if your site is .NET 4.0+, a quick workaround is to start the application normally and then use the 'Attach to .NET 4.0+ Process' profiling option instead)
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?
-i used other ports and it is causing the same error.
-other sites have the same issue
-i binded it to localhost and with a port other than 80 and it is working fine.
what was the problem, is it a name resolution issue?
>> what was the problem, is it a name resolution issue?
I'm still not sure to be honest. I've tried to reproduce this (by having multiple sites running on a different host/same port) but haven't been able to get the profiler to timeout. Can I check--
- If you set up the site on 37.99.128.26 but on a different port does that still profile?
- Just to confirm--do you already have a site on localhost:80 and this fails to profile? If there isn't one already, could you kindly try setting up the site on localhost:80 to see if that works?
- How many sites do you have running on 37.99.128.26:80?
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?
One more question..
Do your bindings specify the IP address to 37.99.128.26 (instead of "All unassigned")? If not, could you please see if doing this helps?
Jessica Ramos | Product Support Engineer | Redgate Software
Have you visited our Help Center?