Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
4998 Discussions

VTune command line Error 0x40000028 (Reporter error)

Roman_H
Beginner
1,004 Views

Hello,

 

after upgrading from 2022.1 to the current 2022.4.1 I cannot use the command line anymore.
It is executing the VTune hotspot analysis but stops at generating the report.

This is a typical output:

 

vtune: Collection stopped.
vtune: Using result path `c:\Users\rhimmes.INFORM\vtune\r002hs'
vtune: Executing actions 19 % Resolving information for `ucrtbase.dll'
vtune: Executing actions 19 % Resolving information for `KERNELBASE.dll'
vtune: Finalization may slow down when loading files from the symbol server specified in the project properties.
vtune: Executing actions 75 % Generating a report
Error: Unexpected report template location
vtune: Executing actions 100 % done
vtune: Error: 0x40000028 (Reporter error)

 


I have already tried uninstalling and reinstalling vtune again.

What else can I do?

 

 

3 Replies
AthiraM_Intel
Moderator
971 Views

Hi,


Thank you for posting in Intel Communities.


Could you please share the OS and hardware details?


Also share the analysis type and the command you used.



Thanks


0 Kudos
Roman_H
Beginner
950 Views

Hi,

 

thank you for your reply:

* The OS is Windows Server 2022
* The error is aready being displayed after collecting the data via
vtune -collect hotspots <myexecutable.exe>
and also if you try to create *any* report afterwards.

BUT I could solve the issue by changing the path variable from:

 

set PATH=C:\Program Files (x86)\Intel\oneAPI\vtune\latest\bin64;%PATH%

to
set PATH=c:\Program Files (x86)\Intel\oneAPI\vtune\2022.4.1\bin64;%PATH%

So it seems that the Symlink does not work on Windows Sever 2022 with the command line

For me, the issue is solved, I can live with this workaround.

Thank you again.

 

AthiraM_Intel
Moderator
921 Views

Hi,


Glad to know that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.



Thanks


Reply