Execution Profiler: unexpected fatal error

[Johannes_T]

Hello Hosmer! What build version of Windows 10 are you using?

[Hosmer]

I'm on Win 10 version 1809 (Build 17763.864).

[Wolfgang]

It does work for me on Win 10 build 18362

[Hosmer]

NI needs to step up to the plate and fix this issue -- or at least provide some meaningful explanation/workaround.

Does this mean that the profiler can ONLY be installed on SOME versions of Windows 10 ?  What about system deployment (which require installation of the run-time profiler)? Will these all FAIL depending on Windows build versions that customers have? This is completely UNACCEPTABLE. I have submitted a bug report already, but there has been no response.

Doesn't anyone at NI monitor these posts?

[Hosmer]

Hello Wolfgang,

I updated my Windows 10, but that didn't help. The problem was that the Profiler version needs to be 1.1.1.

Inexplicably the NI Package Manager downloads the older version 1.1 which doesn't work. NI also makes it really difficult to find version 1.1.1 on their website. All of the links refer to the old version 1.1.

[Wolfgang]

Hi,

which version of NI Package Manager do you have? I think the latest version is 19.6, in my case (with profiler 1.1 installed) it automatically found version 1.1.1 - actually that's how I found out about the patch.

Good luck!

[carlox]

Hi Wolfgang, with NI Package Manager 19.6 I see 1.1.1 in the details view of profiler 1.1, but trying to install it all I got is the message:

"Unable to locate the package 'ni-cvi-execution-profiler-toolkit (>= 1.1.1.49152-0+f0) with a compatible version and architecture"

Win10 x64 1909, CVI 2019 & 2017 installed.
😞
Edit: I'm downloading the offline installer as I'm writing... 
Edit/2: installed the offline package, it's 1.1.149152 version. I can't figure out why package manager does not find it.

[Hosmer]

Wolfgang,

I also have Package Manager 19.6.0. I had also done the painful Win10 update and still no luck. I did finally find and install Profiler Version 1.1.1 (just like carlox explained in his post) and that worked. I also notified support at NI and they will look into this.