RUN TIME error - Error code: system level exception -17502

1. During running of my sequence in a TestStand Operator Interface   i got following run-time error:
    Details: Error executing substep 'Post'.Parameter 'Input cluster 6 [OUT]': System Level Exception.
    Location: Step 'sequence 'SequenceFilePostStep' in 'Sequence X.seq'
    In my SequenceFilePostStep i transfer some information between the LabVIEW 8.0 and TestStand 3.5.
    In my xxx.vi I have 6 clusters and every cluster from 14 to 20 variables.
   The cluster #6 has 70 variables.
   Perhaps, the error that i got is from cluster #6 due to 70 variables? is it to much for cluster?
2. What can i check? How i can fix it?
Please ask questions if you do not understand something, i am want to resolve it!
   Thank you to all!
Message Edited by Yuri_IL on 07-30-2006 10:54 AM
Thank you & Best Regards
*I use LabVIEW 8.X & TestStand 3.5/4.0.1 versions only

Thank you Sam R,
I think that error caused due the overflowing of some string that i have in my cluster.
Because i also get I/O open file error and the name of that file i hold at my cluster.
Do you think that the incorrect string can caused to that system level exception error?
p.s. screenshot is attached
Thank you & Best Regards
*I use LabVIEW 8.X & TestStand 3.5/4.0.1 versions only
Attachments:
io_error.JPG ‏11 KB

Similar Messages

System level exception -17502

Hello,
I get the following error, when I want to execute a labwindows dll step in testsystand 3.1:
"system level exception -17502"
The strange thing is that on 2 other PCs this step is working with same version of teststand and LabWindows
what could be the problem?
regards samuel

That is strange.. The other PC's do not have this error although they have the same dll's...
My experience with that error code has been "array or buffer out of bound". The buffer size was not sufficient to hold the data that was passed to it. Interesting, indeed... hummm....

Gets error "-17502; System Level Exception" while running the custom Step in NI TestStnad 2010

I have a custom teststand step which works like For loop in TestStand. Previously I was using LV 2009 and NI TestStand 4.2.1 and this step was working fine. Recently I upgraded my system to LV 2010 and TestStand 2010, since that it is not working.
When I run the step it gives error "-17502; System Level Exception". I have attached error screenshot.
I am using NIFlowControl.dll in this step.
Please do the needful.
Attachments:
System Levle Exception error.JPG ‏25 KB

The source code for NIFlowControl.dll ships with TestStand. Did you perhaps
1) modify the code and rebuild this dll in teststand 4.2.1, but did not move your changes into the 2010 version and recompile the 2010 version?
Or
2) Move your 4.2.1 version of this dll to 2010 in which case it might be missing important code that exists only in the 2010 version. It's best to redo your code changes to the 2010 version and recompile that if needed.
Also ideally your modified version of NIFlowControl.dll should be located in the teststand public directory rather than the program files directory.
-Doug

System Level Exception. Error code -17502

Hi,
I have an initialize test step which is written in LabWindows/CVI and I call
that step from TestStand.
In that test step I initialize one dll, first I load DLL (the handle goes to
the global variable) and finally I get the function pointers. When this step
ends, I go back to the TestStand and I got this error. Do you know what is
wrong and how should I do this dll loading because I need this handle later?
TIA,
-Harri

I think something must be happening in either the DLL_PROCESS_ATTACH: of DLL main in the loaded dll. It might be trying to do something which can be causing the system level exception.
System level exception can also be caused because you are calling a dll function incorrectly ie passing a I16 instead of a I32 in the parameters.
I might also be trying to call/release a function reference which is not valid.
I would suggest you to step into your code and make sure that all your reference are valid if and when you call/release them.
You might want to try to trap the 17502 error by following the Knowledge Base link given below
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/a92cf6b69941b35d862568d900693df5?OpenDocument
Anand Jain
Applications Eng
ineer
National Instruments
http://www.ni.com/ask

System Level Exception, error -17502 when running VI with RunTime Engine

My sequence conains a single Labview VI. The sequence functions correctly with the Labview RunTime engine NOT selected in the "Advanced Setttings" tab. When I enable the check box to always run the VI with the Runtime Engine, TestStand generates the following error "System Level Exception, error -17502. My teststand version is 3.5, with LV 8.2.
Thanks
Peter V.

Hi,
Are you sure you have LV 8.2 RTE on your system?
Regards
Ray Farmer
Regards
Ray Farmer

LV2011 run time engine error

Somebody knows why I hit a run time engine error when I select runtime adapter in teststand? If I choose dev environment, there is no error and the vi executes.
Attachments:
RunTimeError.png ‏194 KB

Hello JoVMo,
I think the reason and solution for the issue can be found in this KB:
http://digital.ni.com/public.nsf/allkb/24A8C9552C01D7368625735600768095?OpenDocument
Please let me know if it resolves the issue.
Kind Regards,
Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
CLD, CTA
If someone helped you, let them know. Mark as solved and/or give a kudo.

CS6 Error message: "A low-level exception occurred in: Blackmagic Design (recorder) "

Hi,
I have problem when install Adobe Pr Pro CS6 with DeckLink HD Extreme 3D
My workstation have configuration as following:
Supermicro workstation
Super Micro x8DAL-i
Intel Xeon E5645 2.40Ghz
4GB DDR3-RAM x 2
NVIDIA Quadro 2000 1GB Graphics
250GB SATA 7200 RPM
2TB 7200 RPM SATA x 2
DVDRW
Window 7 Pro 64bit
I can capture with Media Express but when I try to capture from CS6 with Decklink HD Extreme 3D, the Error message: “A low-level exception occurred in: Blackmagic Design (recorder) “
Any one can help me urgent please
Thank you,
Dragonhn

I have seen an issue with the latest Blackmagic driver and capturing with the current version of Premiere. I would use Media Express to capture and then just import the files.
Eric
ADK

TestStand 4: 17502 System Level Exception

I attempted to run an TestStand 3.1 Sequence file on my new computer in TestStand 4. And I had a 17502; system level expection run time error for a particular function call. The sequence access the function or module from a .dll that was developed in LabWindows/CVI 7. However, this code module works on my other station that runs TestStand 3.1. I also attached the example of the code that's causing this run-time error in TestStand 4.
KE2
Attachments:
Scope Module.txt ‏4 KB

I did step through the code to see which function call was causing error. However, when I save the sequence file at a TestStand 4.0 sequence file and executed the sequence this system level exception error did not occur again.

17502 System Level Exception

Hi Everyone,
I've done the searches and read all the posts related to the"-17502; System Level Exception" error message.
I've quadruple checked the CVI function and the function call in TestStand to make sure the data types matched and that pointers were indeed pointers and not passed by value.
Since the error stayed, I decided to do a mock code where I removed the parameters in the CVI function to the point where the only parameter is now the CAObjHandle thisContext, as shown in the image below.
Even with a single parameter, I continue to get that error. And yes, the error is related to the function 'MemTest'.
Since I narrowed the list of parameters to this single one, is there something I'm over-seeing with the CVI function and the way it is called by TestStand? (I am rusty at TestStand.. I didn't think I was that rusty )
It does not make it inside the function since the first step is a message saying that it got in (kinda like Hello World).
- sigh -
R
Message Edited by Ray.R on 09-24-2009 03:10 PM
Attachments:
what-the.PNG ‏14 KB

Hi RayF,
I knew I could count on you...
I get the error when I run the sequence. I had a fully working sequence and added this one additional step, which is a new test.
The Adaptor should be okay as it has not changed from the original code. I can check, but ut should be fine. As a matter of fact, if I choose continue instead of terminate, the program continues happily afterwards. So I think I did something stupid which is small and should be easy to fix.. It just evades me at the moment.
I'm "old school". I created the function prototype from within LW-CVI from scratch. I didn't think of using the Create Code button. I will try that.
I will also try removing everything else from within the function and simply have an "Hello World" message popup.
Thanks RayF,
RayR

Intermittent -17502; System Level Exception

Running Test Stand 4.2.1, Labview 2009
In my test stand sequence I launch a Labview VI. Usually it works just fine, but occasionally I get a -17502; System Level Exception error. Once it happens it keeps occuring until I open the Labview Vi, re-save it, and then reload it in Test Stand. I don't change anything about the VI or the Test Stand step, I just open the VI, save and close it.
Any ideas what is happening?

~jiggawax~ wrote:
What drivers are you calling in your VI? What is your VI doing? Can it potentially take different paths through the VI different times that it is called? Can you consistently reproduce the issue?
Here is a link that might be useful: http://forums.ni.com/t5/NI-TestStand/17502-System-Level-Exception-in-Run-Time/td-p/1892207
Can you reproduce it with other VIs? Or is it just this one VI?
Regards,
The VI is using OPC via serial to talk to another device. It just reads a variable for its current status and compares it to an expected value. There are a couple different paths it can take depending on if an error is present, the value read is the same as the expected value, etc. but all the paths do very similar things. The error only occurs with this VI and cannot be reproduced consistantly.

System Level Exception -1702 with TestStand2.0

Hi everyone,
I usually use Labwindows/CVI and TestStand product.
On a new PC I have just installed Measurement Studio 6.0 and after TestStand 2.0
To check if all install are OK, I tried to run the example ..\examples\demo\c\auto.seq and the error System Level Exception Error Code : -1702 appears randomly, It's exactly the same with my sequence application
I don't understand why ? Could Help me
PC configuration :
Windows XP Pro version 2002, service pack 1
Penium(R) 4 CPU 2.8 GHz
RAM 512 Mo
Software installed
Measurement Studio 6.0 with LabWindows/CVI
TestStand 2.0
Thanks a lot in advance.
Glou.

Hi,
this link may help
http://digital.ni.com/public.nsf/allkb/901B5E1C33A102A18625671C007C501F
Is your teststand version 2.0 or 2.01f1?
Regards
Ray Farmer
Regards
Ray Farmer

How to change Crystal Reports XI database name at run time from ASP code using ADO

Dear All,
I need advises regarding to my problem below
I have two database in same SQL 2005 SERVER for TEST01 and LIVE01 Environtment, and I've created more than 100 reports with Crystal Reports 11 and call it from ASP classic page.
The problem is how can I change a database from TEST01 to LIVE01 at the run time from ASP code as I already using TEST01 database on Crystal Reports and I do not want to set a new database location inside crystal for each reports
Thanks and wait for your reply soon.
Below is my code, which has no effect to crystal reports although I've change the database from TEST01 to LIVE01:
<%
Dim oADOConnection, oRptTable, oADORecordset, sql
Dim struser, strpwd, strdriver, dblocation, dbname, strConnect
struser = "sa"
strpwd = ""
strdriver = "{SQL SERVER}"
dblocation = "SQL200501"
dbname = "LIVE01"    ' Changed from TEST01 to LIVE01
strConnect = "User Id=" & strUser & ";"
strConnect = strConnect & "PWD=" & strPwd & ";"
strConnect = strConnect & "DRIVER=" & StrDriver & ";"
strConnect = strConnect & "SERVER=" & DBLocation & ";"
strConnect = strConnect & "DATABASE=" & dbName
sql="Select * from Employee"
Set session("oApp") = Server.CreateObject("CrystalRuntime.Application.11")
Set session("oRpt") = session("oApp").OpenReport("C:\REPORTS\RPT01.RPT", 1) 'USING TEST01 DATABASE
session("oRpt").MorePrintEngineErrorMessages = False
session("oRpt").EnableParameterPrompting = False
session("oRpt").DiscardSavedData
Set oADOConnection = Server.CreateObject("ADODB.Connection")
oADOConnection.Open (strConnect)
Set oADORecordset = Server.CreateObject("ADODB.Recordset")
Set oRptTable = session("oRpt").Database.Tables.Item(1)
oRptTable.SetDataSource oADORecordset, 3
session("oRpt").SQLQueryString = CStr(sql)
session("oRpt").ReadRecords
%>

Did you ever find a solution to this problem? I have the same problem when moving reports from development to Test to Production environments. If the DBName is not the same the report ignores the name provided at runtime.

Diagram Disable produces "-17502 System Level Exception" with TS 4.2 + LVRTE 8.6.1

I had a labview VI that had a diagram disable structure on it. TestStand loaded it all right, but threw a -17502; System Level Exception at runtime.
TS 4.2, using labview 8.6.1 RTEW adapter.

Jed -
Could you please attach files that reproduce this behavior?
Manooch H.
National Instruments

Error Msg -A Low-level exception occurred in: Adobe Player

I have CS6 installed, all the latest patches, etc. It's been working fine for months.In the last week Pr is unable to playback all of my footage (Native 5D mark III h.246 and Canon xf305 footage). Whether it is on the timeline or in the source panel.
The Error message i get it this: A Low-level exception occurred in: Adobe Player (player).
Using Adobe CS 6.0.3
Windows 64 Bit 8 GBs RAM
Happens in new projects and old.
New timelines also affected, it appears.
Was not happening as recently as two days ago.
No changes made to the computer.
Only changes is that I have combined timeines (Imported) from one project to another.
Video shows yellow or Green.
I have rerendered the footage to show all green on timeline.
Only way around it is to reboot the computer, it comes back after a while. The problematic timelines work fine for a while, then this starts happening.
I deleted the media cache database folder after exiting Pr.
Didn't seem to change anything. I just got the error again. Things seem to be curiously messed up. I tried to render a sequence out to MXF. The headless crashed each time, (not totally unusual, but it couldn't complete even once). I also got an error message when I bypassed the Media Encoder and just went strait to rendering it out within Pro. It managed to continue to render it to MXF but when I got done and imported it into Pro, it didn't play the clip when I clicked on it.
The interesting thing to me is that to totally clear Adobe from RAM, I have to go into Task Manager and kill the process after exiting the program (in lieu of rebooting). So it's not closing properly, it appears. Once I kill the process and reopen the app, I can then play the sequence, for a while. It's very curious. Task manager also shows lots of RAM open, no memory leaks at work, nothing unusual. It appears, to be just choking on footage, sort of like it can't quite process the audio (like when you bring in new footage and it has to process that audio). What's happening is like it sees the audio at first when I bring it in at startup of the app, then loses it. If I exit without killing the Premiere process (or shutting down the machine), then it still exhibets the behavior on startup again.
So this project is large, for me. It is showing as 34 MBs. I have a wide variety of clips at play here, but only MXF Canon from the xf305 and MOV from the Canon 5D. The MXF are the default sequence(s) unless I shot nothing but MOV.
I have tried rendering the visualization, all green lines on top but that doesn't seem to fully help. It does play the footage for a while.
There are no special effects added, yet.
Is it worth re-installing Premiere? This has cost me the better part of a day screwing around with this.
Let me detail this again:
Premiere is installed on C There hundreds of GBs of storage avaialble there.
All project files are on F which is a RAID 1 array. It appears to be functioning normally. 800 GBs free space on 2TBs.
All Renders are taking out to an external drive like I always do. Lot s of space available there too.
Anyone have an idea how to fix this?

Is this any better? Cut and pasted plain text.
I have CS6 installed, all the latest patches, etc. It's been working fine for months.In the last week Pr is unable to playback all of my footage (Native 5D mark III h.246 and Canon xf305 footage). Whether it is on the timeline or in the source panel.
the Error message i get it this: A Low-level exception occurred in: Adobe Player (player).
Using Adobe CS 6.0.3
Windows 64 Bit 8 GBs RAM
Happens in new projects and old.
New timelines also affected, it appears.
Was not happening as recently as two days ago.
No changes made to the computer.
Only changes is that I have combined timeines (Imported) from one project to another.
Video shows yellow or Green.
I have rerendered the footage to show all green on timeline.
Only way around it is to reboot the computer, it comes back after a while. The problematic timelines work fine for a while, then this starts happening.
I deleted the media cache database folder after exiting Pr.
Didn't seem to change anything. I just got the error again. Things seem to be curiously messed up. I tried to render a sequence out to MXF. The headless crashed each time, (not totally unusual, but it couldn't complete even once). I also got an error message when I bypassed the Media Encoder and just went strait to rendering it out within Pro. It managed to continue to render it to MXF but when I got done and imported it into Pro, it didn't play the clip when I clicked on it.
The interesting thing to me is that to totally clear Adobe from RAM, I have to go into Task Manager and kill the process after exiting the program (in lieu of rebooting). So it's not closing properly, it appears. Once I kill the process and reopen the app, I can then play the sequence, for a while. It's very curious. Task manager also shows lots of RAM open, no memory leaks at work, nothing unusual. It appears, to be just choking on footage, sort of like it can't quite process the audio (like when you bring in new footage and it has to process that audio). What's happening is like it sees the audio at first when I bring it in at startup of the app, then loses it. If I exit without killing the Premiere process (or shutting down the machine), then it still exhibets the behavior on startup again.
So this project is large, for me. It is showing as 34 MBs. I have a wide variety of clips at play here, but only MXF Canon from the xf305 and MOV from the Canon 5D. The MXF are the default sequence(s) unless I shot nothing but MOV.
I have tried rendering the visualization, all green lines on top but that doesn't seem to fully help. It does play the footage for a while.
There are no special effects added, yet.
Is it worth re-installing Premiere? This has cost me the better part of a day screwing around with this.
Let me detail this again:
Premiere is installed on C There hundreds of GBs of storage avaialble there.
All project files are on F which is a RAID 1 array. It appears to be functioning normally. 800 GBs free space on 2TBs.
All Renders are taking out to an external drive like I always do. Lot s of space available there too.
Anyone have an idea how to fix this?

Custom Run-Time Menu error when named "FileMenu.rtm"

Discovered an interesting "feature" (error?) in LabVIEW 2009 when using custom run-time file menus.
If you create a custom run-time menu (.rtm) and name it "FileMenu.rtm" the menu will not function correctly in executable format.
In my LabVIEW Project, any VIs which called this custom file menu worked correctly in the project, but when I built an executable, the VIs defaulted to the default file menu. This was not due to a corrupted .rtm file or the file not being included in the executable. Instead after extensive debugging I determined that the name "FileMenu.rtm" is somehow reserved in LabVIEW and any executables that are built have the custom run-time menu overwritten by the default. The tricky part of this error is that it goes unnoticed while the code is still in development and only presents itself after being built into an executable.
Simply changing the name of the file fixed the executable run-time menu.

Chris,
Thanks for trying it out. It seems that my forum post may have been a bit rushed.
I tried to duplicate the problem in a new project from scratch and similarly was unable to reproduce it. I will try more soon, and in doing so perhaps reveal the true underlying problem. I would post the original code but it is proprietary.
I was running LabVIEW 2009 and Windows XP when the problem first presented itself. I updated to LabVIEW 2009 SP1 as part of my debugging and the problem still presented itself.
V/R,
~David

RUN TIME error - Error code: system level exception -17502

Similar Messages

Maybe you are looking for