Profile COM-Server(exe)

[GoogleCodeExporter]

Hello friends,

I am very new to this stuff. I install the latest msi start my VS2005 add the 
addin. Than I open my Project click "Enable Profiling" on the contextmenu I add 
micro-profiler_x64.lib under Additional dependencies in Linker/Input.
I compile my project very well, but after starting the service no gui open for 
the profiling. So what the point here? Do I forget something?

Yours,

Original issue reported on code.google.com by herak...@gmx.de on 28 Aug 2012 at 11:04

[GoogleCodeExporter]

My sytem is Windows 2008 R2 64 bit

Original comment by herak...@gmx.de on 28 Aug 2012 at 11:05

[GoogleCodeExporter]

Is your project 64 or 32-bit?
The most probable reason is that the service your are trying to profile has 
limited access rights particularly to COM server activation (which is required 
for the profiler's frontend to start). What identity do you use for your COM 
server's process? Can you temporary set it to the non-limited user? You can 
change this setting using dcomconfig (in Administrative Tools/Component 
Services snap-in).

thanks

Original comment by artem.ge...@gmail.com on 28 Aug 2012 at 11:22

[GoogleCodeExporter]

...and btw, you don't have to add micro-profiler*.lib to additional deps if 
using VS-integration - it does this automatically by adding 'initializer' cpp 
to your project.

Original comment by artem.ge...@gmail.com on 28 Aug 2012 at 11:25

[GoogleCodeExporter]

The project is 64 bit

Original comment by herak...@gmx.de on 28 Aug 2012 at 12:35

[GoogleCodeExporter]

There is a domain user as Identity

Original comment by herak...@gmx.de on 28 Aug 2012 at 12:47

[GoogleCodeExporter]

I cant change the identity, cause only the user has access to other modules.

Original comment by herak...@gmx.de on 28 Aug 2012 at 1:04

[GoogleCodeExporter]

Ok I make a normal application and it runs ok, but running the com server dont 
trigger the profier gui.

BTW which steps do I have to make for a QT4 project with visual studio compiler 
and jom.exe instead of nmake. DId you have experince with qt4/c++ projects?

Yours,

Original comment by herak...@gmx.de on 28 Aug 2012 at 2:14

[GoogleCodeExporter]

What is the non-limited user?

I think I have to give the right to the microProfiler. Isnt it?

Original comment by herak...@gmx.de on 29 Aug 2012 at 9:06

[GoogleCodeExporter]

It looks like re-installing (uninstall first) with option 'for all users' 
selected might help ('just for me' is a default option). The reason is that 
profiler's frontend is registered on a per-user basis which makes its 
registration missing for other users of the machine.
when reinstalling, please close all visual studio instances to prevent 
rebooting.

Original comment by artem.ge...@gmail.com on 29 Aug 2012 at 9:34

[GoogleCodeExporter]

...in addition to the reinstallation for 'everyone', the following 
modifications shall be done in order to profile process running under 
credentials of a user different from the interactive one (I just reproduced 
your situation):
1. In Component Services console (32 bit version - 
\Windows\SysWOW64\comexp.msc) find the profiler's frontend (named as 
"MicroProfiler Frontend Application") in DCOM Config;
2. In the tab 'Identitiy' select 'The Interactive User' to allow frontend to 
interact with desktop;
3. In the tab 'Security' for 'launch and activation' use 'customize' and add 
your domain user with options 'local launch' + 'local activation' allowed for 
this user;
4. In the same tab ('Security') for 'access' add that user with access 
allowance.

I just tested all this steps and it seems that they are working altogether :)

Original comment by artem.ge...@gmail.com on 29 Aug 2012 at 10:00

[GoogleCodeExporter]

Ok I do it like you explained it. Normal application there is no problem. But 
the Com server dont trigger the gui profiler!;o(

Original comment by herak...@gmx.de on 29 Aug 2012 at 10:07

[GoogleCodeExporter]

Great thanks. It works like a charm;o).

Original comment by herak...@gmx.de on 29 Aug 2012 at 10:59

[GoogleCodeExporter]

Great! I'll move this issue to FAQ.

Original comment by artem.ge...@gmail.com on 29 Aug 2012 at 11:27

• Changed state: Done
• Added labels: Type-Other
• Removed labels: Type-Defect