Jump to content

"Not enough memory to complete this operation" issue


Recommended Posts

When I enable VIPM That it show me "Not enough memory to complete this operation"  as the enclosure ...

Is there someone can help ??

My resource as the enclosure when I enable VIPM :

 

OS: Windows 10 64-bit

CPU: Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz   1.19 GHz

RAM:12.0 GB 

HD: 512GB

Memory has 40% free

HD has 91.3 GB free

2022-11-15_12-05-06.jpg

2022-11-15_12-05-30.jpg

2022-11-15_15-44-39.jpg

2022-11-15_12-06-07.jpg

2022-11-15_12-06-25.jpg

2022-11-15_12-07-18.jpg

  • Upvote 4
Link to comment
Share on other sites

I have the same issue on windows 11 so does my colleague.
The process grows in size up to 3.3gb before the error pops up. 
Running version 2022 and colleague version 2021 both versions pop the error. 
Reinstall or running program as admin results in same issue. 

Reinstalled package manager downloaded from: 
https://www.jki.net/en/vipm-2021-download

Note it says version 2021 while the downloaded file installs 2022. 

System specs : 
OS: windows 11 -22H2
I7-9850H
Ram: 32gb 
 

Link to comment
Share on other sites

Same problem. Tested and confirmed with VIPM 21.0.2750, 21.1.2754, 22.0.2371.

The latest version which works is 20.0.2302, but it does not know about the newest LabVIEW versions.

 

According to Process Explorer, VIPM process hits ~3.2 GB and crashes (see couple of screenshots below).

PC configuration:

Processor    AMD Ryzen Threadripper 2950X 16-Core Processor    3.50 GHz
Installed RAM    64,0 GB (63,9 GB usable)
Edition    Windows 10 Pro
Version    22H2
OS build    19045.2251
Experience    Windows Feature Experience Pack 120.2212.4180.0

 

Installed LabVIEW versions: 2018 and 2022 Q3 (both 64 bit).


 

Screenshot 2022-11-15 180853.png

Screenshot 2022-11-15 175240.png

Screenshot 2022-11-15 175146.png

Screenshot 2022-11-15 175130.png

Link to comment
Share on other sites

Same error here on multiple computers. At first we thought our IT department rolled out something that caused the issue, but based on what I am seeing here it looks like something is corrupt with one of the AWS servers. I suspect the JKI crew is diligently working on it as it is effectively a worldwide outage for VIPM until they get to the bottom of it.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.