Comments
Sort by recent activity
I'm facing the same issue. I have a customized version of identity server set up on one site, running in .NET Core, accessed via one URL (https://auth-dev2.narrpr.com, which we run in IIS and leverage the hosts file to set up the DNS name), and I have other sites on the same server that call into the identity server end-points. I'd like to profile the identity server website. I have been able to profile the identity server website (at least the start up portion of the application, by launching as a .NET Core Application, specifying the assembly, indicating it is a web application, starting the web application in chrome, and specifying the launch URL of https://auth-dev2.narrpr.com), but when I run the other websites (on the same server) that interact with the identity server (by making calls into https://auth-dev2.narrpr.com), none of their calls are being profiled. The calls are succeeding, but I suspect that they are bypassing the profiled identity server app, and are calling directly into the one configured in IIS. How do I get ANTS Performance Profiler to profile the version actually being hosted in IIS and that the other apps are calling? (Note that even on the profiled website, on the one started by ANTS, while it profiles the app startup, links and things I click on in the website that should be tracked aren't causing any profiling to occur... After startup, there is no profiling activity). / comments
I'm facing the same issue. I have a customized version of identity server set up on one site, running in .NET Core, accessed via one URL (https://auth-dev2.narrpr.com, which we run in IIS and leve...
I was also experiencing this issue, but followed the instructions in the KB article (KB300956) exactly -- very painful to go thru the registry and remove all the keys under each of the services, as I have TONS of services. At the end of the process, after rerunning lodctr /R, it fixed it. Note also that when I compared the perfc009.dat file to the original from my Windows installation disk, they were quite different, and the first part of the file was all zeros (using binary compare). Also, perfh009.dat had been empty (file length 0). It was also a pain to find these files from the Windows installation disk. The folder mentioned in the KB article didn't exist on my drive -- instead there was an "install.wim". I was able to use 7z (zip program) to open this compressed file, then navigate down to the \windows\system32" folder, and get at these files. / comments
I was also experiencing this issue, but followed the instructions in the KB article (KB300956) exactly -- very painful to go thru the registry and remove all the keys under each of the services, as...