Activity overview
Latest activity by vistadb
None of our apps showed up in the dropdown in the wizard.
Looks like ANTS Profile can bind only to apps in 127.0.0.1. Ours are in 127.0.0.*, which are also legitimate local IP addresses. / comments
None of our apps showed up in the dropdown in the wizard.
Looks like ANTS Profile can bind only to apps in 127.0.0.1. Ours are in 127.0.0.*, which are also legitimate local IP addresses.
Cannot profile ASP.NET 2.0 on x64: wwwroot hard-coded?
When trying to do performance profiling on an ASP.NET 2.0 application (say, http://localhost/foo/bar.aspx), when IE appears, it just displays a 404 error for http://localhost:8013/foo/bar.aspx.
We ...
I tried creating an IIS6Port registry value as described and it had no effect, even after bouncing the ANTS Profiler service. I tried both a String and a DWORD registry value, for the value 80. ANTS Profiler still opened an IE instance with URL http://localhost:8013/.... / comments
I tried creating an IIS6Port registry value as described and it had no effect, even after bouncing the ANTS Profiler service. I tried both a String and a DWORD registry value, for the value 80. AN...
As I posted on April 21, we are having similar problems trying to profile 32-bit .NET code on our brand new 64-bit Win2003 Server boxes.
When I try to profile an ASP.NET application, I get the same error as the previous poster:
"Unable to get the private bytes memory limit for the W3WP process. The ASP.NET cache will be unable to limit its memory use, which may lead to a process restart. Error: 0x80070003"
but NOT the "CoCreate" error he reported.
When I try profiling a .NET desktop app, the profiler successfully starts up the app, but no profiling gets done. The ANTS Profiler window displays the message "Waiting for connection..." at the bottom of the window. The message remains until I click "Stop Profiling."
We have 20 paid licenses sitting idle. A cookbook-style method for making this work would be appreciated: we are software developers but not Windows admins. Thanks. / comments
As I posted on April 21, we are having similar problems trying to profile 32-bit .NET code on our brand new 64-bit Win2003 Server boxes.
When I try to profile an ASP.NET application, I get the same...
I am getting this problem too, trying to profile 32-bit ASP.NET code on my new x64 box, using Visual Studio 2005. Profiling completely fails: I get a 404 error on the localhost URL.
Windows Server 2003
Standard x64 Edition
Service Pack 1
AMD Athlon 64 X2 dual core processor 4200+, 2.2 GHz
4 GB RAM
Red Gate? / comments
I am getting this problem too, trying to profile 32-bit ASP.NET code on my new x64 box, using Visual Studio 2005. Profiling completely fails: I get a 404 error on the localhost URL.
Windows Server...