LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Closing CVI -> "the index passed is out of range"

Hello,

 

Just recently, I've been getting popup messages (2 or 3) when I close CVI saying that "the index passed is out of range."  There is no way to debug this since all I can do is hit OK and CVI closes after two or three popups.  Any suggestions?

 

Thanks

 

Judy Harrigan

0 Kudos
Message 1 of 15
(5,301 Views)
which version of CVI are you using ? i had the same problem for a long time with CVI 8.1. fortunately, it does always happen after having saved all files correctly, so it seems to have no consequence. i don't have this problem anymore since i installed CVI 8.5: i don't know if it has really been corrected or if it is only a consequence of reinstalling all the environment.
0 Kudos
Message 2 of 15
(5,284 Views)

Hi,

 

I have CVI 9.0 installed.

 

Thanks,

 

Judy

0 Kudos
Message 3 of 15
(5,258 Views)

Hi Judy,

 

A few questions to help troubleshoot the issue:

 

1. Does this happen every time you close CVI?

2. Does this only happen with a certain project or any project/workspace that is loaded when you try and close (even a blank project)?

 

And a few steps to get some more information:

3.  CVI rebuilds its own registry key every time it opens, so to see if that is corrupted, let's hide the registry key and have it rebuild it.  Open your registry (Start Menu»Run menu»type "regedit" without the quotes) Navigate to HKEY_CURRENT_USER\Software\National Instruments\CVI\9.0 and rename the key (the folder) "9.0backup" or something like that.  Open CVI and try and close it and see if you get the same message pop-up

4.  Create a log file by configuring your logging.  Open the utility at C:\Program Files\National Instruments\CVI90\bin\ConfigCVILogging.exe .  Check all of the checkboxes to log all message types and change the "Log output to" to log to a file.  Open and close CVI and make sure you get the error message.  Zip up the text file and you can post it on the forum so we can check it out.

Eric B.
National Instruments
Message 4 of 15
(5,234 Views)

Hi Eric,

 

Whatever set it off must have changed state because I cannot replicate the behavior.  It was definitely NOT happening when I closed out every project.  Seemed to be only when I was working on DLL/Static library code.  I spent today cleaning up that code and have not seen it at all.  Such is life.

 

Judy

0 Kudos
Message 5 of 15
(5,230 Views)

Judy,

 

Thanks for letting me know...that's odd that it just went away.  If it comes up again, let us know and we can try and get to the root of the issue.  Glad to hear it is working again.

Eric B.
National Instruments
0 Kudos
Message 6 of 15
(5,228 Views)

[18:03:55.830] [WARNING] [RegGetStringValue] [..\mgsource\registry.c:654] MgErr = 77
[18:03:55.901] [WARNING] [RegGetStringValue] [..\mgsource\registry.c:654] MgErr = 77
[18:03:57.421] [WARNING] [CheckForAutoRecover] [..\james\AutoSave.c:363] Err = -101
[18:03:58.301] [WARNING] [WorkspaceFileProc] [..\james\jn_work.c:626] Trying to load current workspace UFR.
[18:03:58.381] [WARNING] [WorkspaceFileProc] [..\james\jn_work.c:626] Trying to load current workspace UFR.
[18:04:13.341] [WARNING] [LWGetValueFromIndex] [..\james\ui_lctrl.c:1177] Err = -55
[18:04:13.421] [WARNING] [LWGetValueFromIndexById] [..\james\ui_lctrl.c:1156] Err = -55
[18:04:13.451] [WARNING] [GetValueFromIndex] [..\james\ui_lctrl.c:1141] Err = -55
[18:04:13.471] [WARNING] [DeleteErrorsInErrorWindow] [..\jon\errorwin.c:976] Err = -55

This is my error infomation.

0 Kudos
Message 7 of 15
(4,578 Views)

So what is the relation of your post with the topic "index passed is out of range"?

0 Kudos
Message 8 of 15
(4,568 Views)

I have the same question.Posted for help.

0 Kudos
Message 9 of 15
(4,558 Views)

Hey Lan4,

 

There are several reasons why you might be seeing that error, so I'm going to suggest a few possibilities and hopefully one of these will apply to you.

 

First, do you use the EnableExtendedMouseEvents() function? In one previous case, that function was causing the error dialog to appear when CVI closes.

 

Second, does this happen every time you close CVI, or just with a particular file? If it's just a particular file, it'd be great if you could attach a stripped-down version that still exhibits the same behavior. That might help us narrow it down.

 

Finally, we could try reinstalling CVI. Let's try the other steps first, but if those don't resolve the issuse, a reinstall would be the next step.

 

Look forward to hearing back from you!

0 Kudos
Message 10 of 15
(4,544 Views)