-
Posted to
Troubleshooting
by
Madness80
on
10-21-2009, 8:04 AM
What problem are you trying to solve?
-
Posted to
Troubleshooting
by
Madness80
on
10-20-2009, 4:08 PM
Tracestart.bat **********************
logman start Dave -pf c:\IIStrace\IISprovider.txt -ets -o c:\IIStrace\data\IIS.etl -max 13
pause
Tracestop.bat *******************
logman stop Dave -ets
TraceReport.bat ******************************
tracerpt c:\IIStrace\data\IIS.etl -o c:\IIStrace\reports\dumpfile.csv -summary ...
-
Posted to
Troubleshooting
by
Madness80
on
10-20-2009, 1:08 PM
I think the problem is that the request monitor only tells you what is running at the time that you enable the trace. Your hello world would execute in milliseconds either before or after the trace. That is why my code called out to sleep.exe. Just save my page as a ASP and not ASPX. It should run fine. While your browser is waiting for it ...
-
Posted to
Troubleshooting
by
Madness80
on
10-19-2009, 5:05 PM
I have a Whatsrunning.bat file that I use. Looks like this.
del c:\iistrace\data\WhatsRunning.etl
logman start WhatsRunning -p "IIS: Request Monitor" -ets -o c:\iistrace\data\WhatsRunning.etl -max 13
logman stop WhatsRunning -ets
tracerpt c:\iistrace\data\WhatsRunning.etl -o c:\iistrace\reports\WhatsRunning.csv /y
notepad ...
-
Posted to
Advanced Topics
by
Madness80
on
10-14-2009, 11:56 AM
Do you get any return code or exception?
Try using Process Monitor to trace the service. http://technet.microsoft.com/en-us/sysinternals/default.aspx
Look for "access denied" or "not found" conditions.
-
Posted to
Advanced Topics
by
Madness80
on
10-14-2009, 11:33 AM
Put a try ...catch around your code and write out the error to the application eventlog. I suspect that it can't find "luke-pc". You can also use Visual Studio and select Tools and then "Attach to a process". You should then be able to set a breakpoint and walk thru your code to look at error variables.
You could also try ...
-
Posted to
Advanced Topics
by
Madness80
on
10-14-2009, 10:58 AM
"not work".. what specifically does that mean? How do you know that it did not work? How is the service configured? Why do you want to run it as a service? Please provide details and I will try to help.
-
Posted to
Configuration & Scripting
by
Madness80
on
09-08-2009, 1:48 PM
Unfortunately this is one of those instances where I can't say with 100% certainty that it will fix your problem.
I would suggest a review of the folder permissions on your development/QA/production servers and insure that they are identical.
A review of the IIS config would also be good if you haven't done so already. Make sure ...
-
Posted to
Configuration & Scripting
by
Madness80
on
09-08-2009, 12:51 PM
Something doesn't sound right here. If you are using basic authentication, then your user would need to authenticate to IIS in order to execute logon.asp. So the user then enters a second ID and password to authenticate to the application?
I suggest removing the "deny write" and see if your problems go away.
-
Posted to
Configuration & Scripting
by
Madness80
on
09-04-2009, 11:48 AM
I think that just indicates that at one time it had the MS06-014 patch applied.
Do a windiff compare of C:\Program Files\Common Files\System\ on both servers and make sure you're using the same code base. You might also want to run a compact and repair on the MDB.
I'll bet that you have code (somewhere) that is not closing the ...