Unable to start a New Profiling Session

[Hetal]

Hi,

I am willing to profile a (ASP.NET Web Application [iis]) application 
following are the steps performed
1) Start New >> ASP.NET Web Application (IIS) >> http://localhost/ApplicationName/Default.aspx >> Reset IIS >>IE >> Sampling Profiler >> Profile Child Processes

A warning is displayed 
"To Profile IIS Sites running under Network Service or Local Service Identities, you may need to restart your machine once JustTrace is Installed"

Click Run

A new Browser is open

But In Just Traces Application there appears a popup stating "Waiting for response from the profiled application.."

And this stays there.

[Angel]

Hi Hetal,

Thank you for reporting that issue. We are not able to reproduce it by following your steps. Could you try to repair JustTrace installation? You can do this from Control Panel -> Add or Remove Programs -> Telerik JustTrace -> Repair. If you need further assistance feel free to contact us again.

Regards,
Angel
the Telerik team

[Hetal]

Hi Angel,

Repaired JustTrace, but same result .

Note : am using the standalone version and the issue is seen when i execute it using VS2010, Although I am able to Profile a New Blank WebSite.


Please let me know if you wish to have some more details.

[Angel]

Hello Hetal,

In order to understand your problem in details could you send us the latest 3 event logs for Event ID 1022. You can do this from Control Panel -> Administrative Tools -> Windows Logs -> Application and then copy-paste 3 latest event logs for event with id 1022. I attach a screenshot how the event log should looks like if the profiler is attached to the process successfully.

Regards,
Angel
the Telerik team

[Hetal]

Error
.NET Runtime version 4.0.30319.225 - Loading profiler failed during CoCreateInstance.  Profiler CLSID: '{8C29BC4E-1F57-461a-9B51-1200C32E6F1F}'.  HRESULT: 0x800700c1.  Process ID (decimal): 7932.  Message ID: [0x2504].

Information
.NET Runtime version 4.0.30319.225 - The profiler has requested that the CLR instance not load the profiler into this process.  Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'.  Process ID (decimal): 5684.  Message ID: [0x2516].

Error 
.NET Runtime version 4.0.30319.225 - Loading profiler failed during CoCreateInstance.  Profiler CLSID: '{8C29BC4E-1F57-461a-9B51-1200C32E6F1F}'.  HRESULT: 0x800700c1.  Process ID (decimal): 4688.  Message ID: [0x2504].

Information 
.NET Runtime version 4.0.30319.225 - The profiler has requested that the CLR instance not load the profiler into this process.  Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'.  Process ID (decimal): 6976.  Message ID: [0x2516].

[Angel]

Hi Hetal,

Could you run "C:\Program Files (x86)\Telerik\JustTrace\CleanRegistryKeys_x64.reg" and try again. If it does not help, send us the latest event logs again, please.

All the best,
Angel
the Telerik team

[Hetal]

Event code: 4005

Event message: Forms authentication failed for the request. Reason: The ticket supplied has expired.

Event time: 10/16/2012 2:08:28 PM

Event time (UTC): 10/16/2012 8:38:28 AM

Event ID: 3cd88d51e5cd4a3cad4973535520e26d

Event sequence: 2

Event occurrence: 1

Event detail code: 50202

.NET Runtime version 4.0.30319.225 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'. Process ID (decimal): 1908. Message ID: [0x2516].

Note : The site is working fine, in the newly opened IE Window.

[Angel]

Hello Hetal,

I do not understand do you still have that issue or now you are all set. If the issue is still existing please send out event logs for event id 1022 again.

Greetings,
Angel
the Telerik team

[Hetal]

I am still facing the same issue.

Following are the 1022 logs.

 

.NET Runtime version 4.0.30319.225 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'. Process ID (decimal): 1908. Message ID: [0x2516].

.NET Runtime version 4.0.30319.225 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'. Process ID (decimal): 3140. Message ID: [0x2516].

[Angel]

Hello Hetal,

It seems that you have several profilers started. Could you try to run again the file which I attached and then try to run the standalone version. Please let me know if you still have this issue after that.

All the best,
Angel
the Telerik team

[Hetal]

The result is same, The Profiler didnt started.

Following is the Event Log

NET Runtime version 4.0.30319.225 - The profiler has requested that the CLR instance not load the profiler into this process. Profiler CLSID: '{301ec75b-ad5a-459c-a4c4-911c878fa196}'. Process ID (decimal): 6804. Message ID: [0x2516].

[Angel]

Hi Hetal,

I am glad to notify that today we are going to release new version of Just Trace as part of the company official release. The defect you faced with is fixed in it. You will also find our new and improved UI and UX as well as support of IIS Express and IIS8 which makes Just Trace great tool for memory and performance issues detection. Bunch of new features are on the road so stay tuned!

Greetings,
Angel
the Telerik team

[Rob Nickolaus]

I am experiencing the same issue. I am running IIS using a domain account for credentials. The JustTrace version I have installed is 2012.3 1017 and it gives me the same problem. It starts up the browser with the correct application and I am able to successfully navigate through the web app. However, the whole time JustTrace is sitting on the 'New Profiling Session' (where I launched the browser from via the 'Run' button) with a message of "Waiting for response from the profiled applicaiton..."

I am using 'Improve Performance', Profilee='ASP.NET web application (IIS)', browser is Internet Explorer, profiling type is 'Performance Profiler (Tracing), Filter .NET Framework internals is checked. I have tried the 'restart IIS' option and the 'Profile child processes' option.

[Angel]

Hello Rob,

Thank you for reporting this error. I am sorry for the trouble you have with JustTrace. Could you try to restart IIS manualy and try again? Please contact us if you still face that problem afterwards.

Kind regards,
Angel
the Telerik team

[Rob Nickolaus]

I found that starting JustTrace from within VS 2012 works fine and that will satisfy my needs for the forseeable future. If I have a need to use the stand-alone trace, I'll come back to this suggestion.

Thanks.

[Angel]

Hi Rob,

It is nice to hear that you had your work done. If you need assistance for the future, do not hesitate to contact us.

All the best,
Angel
the Telerik team

[Orest]

Hello,

We are running separate "JustTrace_2013.1.220_DEV" application on our production server in order to identify memory leaks and getting the same error:

Event Type:    Error
Event Source:    .NET Runtime
Event Category:    None
Event ID:    1022
Date:        2/22/2013
Time:        3:45:42 AM
User:        NT AUTHORITY\NETWORK SERVICE
Computer:    envi-ioscorp-co
Description:
.NET Runtime version 4.0.30319.269 - Loading profiler failed during CoCreateInstance.  Profiler CLSID: '{06051352-82a1-41db-ba4f-12d9d3df4767}'.  HRESULT: 0x80040111.  Process ID (decimal): 3604.  Message ID: [0x2504].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Our server configuration is Windows 2003 R2 Enterprise x64 Edition and IIS 6.0. We have tried to reinstall JustTrace and run the CleanRegistryKeys-x64 attached in the previous posts but still getting the error.
Please let me know if you need some more details.

Regards,
Orest.

[Martin]

Hello Orest,

The error you are getting is quite unusual. Can you please check if the default value of registry key HKEY_CLASSES_ROOT\CLSID\{06051352-82A1-41DB-BA4F-12D9D3DF4767}\InprocServer32 points to Telerik.JustTrace.CoreProfilers.dll as shown in the attached screenshot?

Can you also check if you can successfully profile the Demo.RayTracer example application?

Regards,
Martin
the Telerik team

[Orest]

Martin,

Thank you for the suggestion. I've checked registry and found that mentioned key points to the correct value(please see attachment).

Regards,
Orest

[Martin]

Hi Orest,

Since the configuration seems to be OK, can you try profiling the Demo.RayTracer application which ships with JustTrace? To do it click on the Demo.RayTracer button located in the lower-right part of the Start Page window, choose Memory profiler and hit run.

Greetings,
Martin
the Telerik team

[Orest]

Hello Martin,

While running RayTrace application we have the same issue. Please see attachment.

Also we found the next errors in the Event Viewer:

Event Type:    Error
Event Source:    .NET Runtime
Event Category:    None
Event ID:    1022
Date:        2/26/2013
Time:        2:03:32 AM
User:        NT AUTHORITY\NETWORK SERVICE
Computer:   
Description:
.NET Runtime version 4.0.30319.269 - Loading profiler failed.  COR_ENABLE_PROFILING was set properly, but COR_PROFILER was not.  COR_PROFILER must be set to the CLSID of the profiler to load.  Process ID (decimal): 1552.  Message ID: [0x2500].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and

Event Type:    Error
Event Source:    .NET Runtime
Event Category:    None
Event ID:    1022
Date:        2/26/2013
Time:        2:06:51 AM
User:       
Computer:   
Description:
.NET Runtime version 4.0.30319.269 - Loading profiler failed during CoCreateInstance.  Profiler CLSID: '{06051352-82a1-41db-ba4f-12d9d3df4767}'.  HRESULT: 0x80040111.  Process ID (decimal): 3688.  Message ID: [0x2504].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Regards,
Orest.

[Todor]

Hi Orest,

 I've prepared a small project to test the loading of our profilers. Please find the attached zip archive, which contains the 64 bit and the 32 bit versions. To run it, start elevated Command Prompt (cmd.exe) and start the two executables. They will write their diagnostic output to the console. You can copy-paste it and send it to me for further inspection.

Kind regards,
Todor
the Telerik team

[Orest]

Hi Todor,

In view that starting from yesterday the new version of the tool is available we just removed the old version (2013.1 220) and installed the new one (2013.1 228). After this tool works fine. But still, we have few related questions:

1. In the event log we found the next errors:

Event Type:    Error
Event Source:    Perflib
Event Category:    None
Event ID:    1017
Description:
Performance counter data collection from the "DTSPipeline" service has been disabled due to one or more errors generated by the performance counter library for that service. The error(s) that forced this action have been written to the application event log. The error(s) should be corrected before the performance counters for this service are enabled again.

Event Type:    Error
Event Source:    Perflib
Event Category:    None
Event ID:    1017
Description:
Performance counter data collection from the "ASP.NET_2.0.50727" service has been disabled due to one or more errors generated by the performance counter library for that service. The error(s) that forced this action have been written to the application event log. The error(s) should be corrected before the performance counters for this service are enabled again.

Event Type:    Error
Event Source:    Perflib
Event Category:    None
Event ID:    1021
Description:
Windows cannot open the 32-bit extensible counter DLL ASP.NET_2.0.50727 in a 64-bit environment. Contact the file vendor to obtain a 64-bit version. Alternatively, you can open the 32-bit extensible counter DLL by using the 32-bit version of Performance Monitor. To use this tool, open the Windows folder, open the Syswow64 folder, and then start Perfmon.exe.

Could these errors be connected with JustTrace tool? They appear after new version installation.

2. As we described before we would like to use JustTrace tool on our production server to identify memory leaks. After tool has been successfully started we noticed that not all information is displayed on the memory usage graph. Windows task manager shows that IIS worker process consumes much more memory than shows JustTrace tool (please see attachment). How it could be?

Regards,
Orest.

[Todor]

Hi Orest,

1. JustTrace loads a small data-gathering module in the profiled managed process (in your case, w3wp.exe). This module does not interact with Windows Performance Counters in any way. 
I suggest that you check Windows Application Event Log for other messages that can reveal the root cause of these events.

2. Our UI shows only the CLR-managed memory. Task Manager does not know about managed memory and shows total consumed memory of the process instead. This includes the unmanaged heap, stacks and much more. This explains the discrepancies between the two tools.

All the best,
Todor
the Telerik team

[Orest]

Hi Todor,

Thank you for the information. For now it look like the new version of the tool works fine. We'll let you know in case we discover other errors.

Regards,
Orest.