during the installation of VTune client 3.0 on a Fedora Core 4 IA32 system we ran into a problem: vtl dies with "Error 0x80040154: Unable to create the VTShell object. Make sure the Shell library is properly installed and registered."
A similar problem has been reported for an earlier version of VTune: "problems invoking vtl" [intel.com]
As it is a DCOM related problem, I ran
for i in /opt/intel/vtune/shared/bin/*.tlb ; do regsvr $i ; done
but that did not help.
bash$ sermon checkntd
returns "Ntd is currently not running. Reason = -1" however
says "Ntd is currently running. Pid = 2199"
Is it indeed a EntireX DCOM related problem?
Message Edited by dmitri.chubarov on 04-19-200611:49 AM
I suggest you try VTUNE 8.0 for Linux immediately! And see if the problem goes away, differs, or stays the same.
You can download an evaluation copy from
IF you chose to try this, you must uninstall VTune 3.0 first, if possible.
no quick resolution there. After uninstalling 3.0 and installing 8.0 (ohne compiling the kernel drivers -- another story altogether on the 2.6.16 kernel) have exactly the same problem.
However during the installation of intel-vtune-core-8.0p-245.x32.rpm I get a number of "Failed to load library" messages injected into the vtune_install.log. Possible reason: the rpm binary is a dynamic executable, that depends on libgcc_s.so.1. On my system it ensures that the right version of the library will be loaded, thus breaking the scripts inside the package that depend on a different setting of LD_LIBRARY_PATH. One solution to this problem would've be for the postinstall and preinstall scripts to set up the environment before running commands.
I have found another thread here, where such messages were mentioned: "After installing,i can't run /opt/intel/vtune/bin/vtl!help me".
Back on 3.0 after running regsvr on _all_ shared objects in /opt/intel/vtune/shared/bin got somewhere: the error message from vtl is now
Error 0x80004005: The Reporter Add-in is not available. Make sure that the Shell is properly installed and registered.
I have heard reports of VTune running on Fedora Core 4, so this problem could be dependent on the specific hacks used to make the installation process working.
Message Edited by dmitri.chubarov on 04-20-200601:33 AM
Message Edited by dmitri.chubarov on 04-20-200601:41 AM
As was mentioned earlier in this thread the problem with unregistered Shell component is due to the conflicting shared objects requirements of the rpm binary (gcc 4) and of the EntireX DCOM programs called by the rpm scripts (gcc 3).
In order to install VTune we had to make sure that each program gets the correct shared objects.
The --scripts query option in rpm is also helpful.
Can anybody explain what is the significance of the number 13 in relation to processes running under user `sag'?