Execution Profiler causes error after it is disabled.

[judyh]

Hi all,

I have a software package that we have been using the CVI Execution Profiler with.  I built the release version with profiling enabled in the build options which also added in the merge module into the build (see CVIProfilerMergeModule.jpg).  I got what I needed from the profile tool, but now I cannot seem to turn it off.

I have disabled it in the code and the build options for the project and I have removed all NI software from the target machine (including manually removing the cviauto.dll and runtime dlls from the windows/system32 folder).  And yet every time I install my new, profiler disabled, build, I get the error seen in ProfileError.jpg on start up.  How do I get rid of this?????

Thanks,

Judy

[Mohan · Accepted solution]

The error indicates that some code in your program is calling the profiler but the profiler is not installed. Make sure you rebuild your CVI program and all CVI DLLs you call with profiling disabled. To make sure you really rebuild everything, mark all source files for recompilation and then build. Or, delete the cvibuild directory and then build. If you have any instrument (.fp) files or .obj files or .lib files in your project, make sure that they also are recompiled - delete the .obj and .lib files and make sure CVI recompiles them from source. If you only relink the project without recompiling all the source files, then you may still have some object code that is callling the profiler.