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.

Similar Messages

  • 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

  • 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. 

  • 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

  • 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 -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.... 

  • 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

  • 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

  • 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

  • "-17005 - System Level Exception" when adding extra results

    Hi,
    I can't find an answer to the following problem:
    I defined a complex data type and used it in custom step. Further on I configured TestStand to add to results the previously defined parameters.
    When running this step the execution is abnormally aborted.
    The attached sequence file reproduces the error.
    The environment used is TestStand 3.0 under WindowsXP.
    Debugging with MSVC++ 6.0 I can see an Access Violation in TSTOBJ2.DLL, which I suspect is not handled.
    Please help me out here solving this problem.
    Thank you,
    Silvius
    Silvius Iancu
    Attachments:
    Error.seq ‏33 KB

    Silvius -
    I remember a problem that was fixed in TestStand 3.1 and it had to do with multiple levels of types causing the problem. I tried your sequence file on TestStand 3.0 and it occurred. I tried it on TestStand 3.1 and the problem did not.
    I suspect that if you do not use three levels of types and instead use two or one large type only, the problem will not occur in TestStand 3.0.
    Scott Richardson (NI)
    Scott Richardson
    National Instruments

  • System level exception

    We are having an issue with TestStand 4.0 generating an error from the frontendcallback.seq.  The current problem doesn't let us login so we can not do anything with TS.  We have uninstalled TestStand a few time and also deleated the whole TestStand directory and reinstalled and the problem still doesn't go away.  Also, TS is lock and will not close without using the task manager.
    Does anyone have any suggestions to fix this?
    See attached .doc for a picture...
    Paul
    Attachments:
    Doc12.doc ‏100 KB

    Do you have TestStand 2.0 installed on the system? If yes, look at the TestStand Readme.html document - it describes the problem and solution. To summarize: To restore the TestStand 4.0 installation after failing to install TestStand 2.0.1, you must perform a repair operation on the LabWindows/CVI RTE by using the National Instruments Software maintenance utility located in Add/Remove Programs in the Windows Control Panel and then use the TestStand Version Selector application to reselect TestStand 4.0 as the active version.
    Jim C.
    Message Edited by TStester on 11-16-2007 01:02 PM

  • Deployment '18600003' to target 'Production' encountered a system level dep

    Hi Experts,
    Please help me in resolving the error while i am doing full deployment from BCC to staging / production server instances , i am getting below error.
    It would be great if u help me resolving this error.
    <Dec 5, 2012 1:48:26 AM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    **** Warning Wed Dec 05 01:52:33 PST 2012 1354701153339 /atg/epub/PublishingRepository Using default JDBC type for: project:tar1557 could not find this column in the table's meta data
    **** debug Wed Dec 05 01:52:43 PST 2012 1354701163290 /atg/epub/DeploymentServer Run first apply phase: true
    **** debug Wed Dec 05 01:52:43 PST 2012 1354701163292 /atg/epub/DeploymentServer Target not configured for switch. Skipping switchable datasource verification.
    **** debug Wed Dec 05 01:52:43 PST 2012 1354701163407 /atg/epub/DeploymentServer DistributedDeploymentAdapter:DAF Deployment with ID: 18600003 previously deployed.
    **** debug Wed Dec 05 01:52:43 PST 2012 1354701163410 /atg/epub/DeploymentServer DistributedDeploymentAdapter:Deploy Data
    **** debug Wed Dec 05 01:52:43 PST 2012 1354701163410 /atg/epub/DeploymentServer DistributedDeploymentAdapter:Resuming DAF deployment with ID: 18600003
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer --- CONTAINER:atg.deployment.common.DeploymentException: Deployment '18600003' to target 'Production' encountered a system level deployment error during data transfer.; SOURCE:atg.deployment.DistributedDeploymentException: Cannot resume deployment 18600003 because it was cancelled before the deployment data and markers were saved.
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.common.ResourceUtil.exception(ResourceUtil.java:414)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.adapter.DistributedDeploymentAdapter.deployData(DistributedDeploymentAdapter.java:1399)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.adapter.DistributedDeploymentAdapter.transferData(DistributedDeploymentAdapter.java:278)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.server.Deployment.run(Deployment.java:1951)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at java.lang.Thread.run(Thread.java:662)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer Caused by :atg.deployment.DistributedDeploymentException: Cannot resume deployment 18600003 because it was cancelled before the deployment data and markers were saved.
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.DeploymentManager.deploy(DeploymentManager.java:1069)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.adapter.DistributedDeploymentAdapter.resumeDafDeployment(DistributedDeploymentAdapter.java:1944)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.adapter.DistributedDeploymentAdapter.deployData(DistributedDeploymentAdapter.java:1307)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.adapter.DistributedDeploymentAdapter.transferData(DistributedDeploymentAdapter.java:278)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at atg.deployment.server.Deployment.run(Deployment.java:1951)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer at java.lang.Thread.run(Thread.java:662)
    **** Error Wed Dec 05 01:52:43 PST 2012 1354701163792 /atg/epub/DeploymentServer
    **** Warning Wed Dec 05 02:03:14 PST 2012 1354701794489 /atg/dynamo/service/ClientLockManager The useLockServer property of: /atg/dynamo/service/ClientLockManager is false and so global locking is disabled
    **** Warning Wed Dec 05 02:04:43 PST 2012 1354701883454 /atg/epub/PublishingRepository Using default JDBC type for: project:tar1552 could not find this column in the table's meta data
    **** Warning Wed Dec 05 02:05:41 PST 2012 1354701941339 /atg/epub/PublishingRepository Using default JDBC type for: project:tar1557 could not find this column in the table's meta data
    Thanks ,
    Sharif.

    Hi,
    I faced the same issue while opening the merchandiser tab in the BCC(after providing the credentials error dialog appearing the UI side and log showing the error whatever you mentioned). But issue resolved after initiating a full deployment and the restarting the publishing server.:)))))

  • System Level deployment.properties on https Server

    We want to use the system level deployment.properties (
    http://java.sun.com/j2se/1.5.0/docs/guide/deployment/deployment-guide/properties.html#location )
    which is placed on our https server.
    For Java Webstart applications this works perfect.
    But applets wont start.
    Applet console output when deployment.properties is placed on https server:
    Java Plug-in 1.5.0_06
    Using JRE version 1.5.0_06 Java HotSpot(TM) Client VM
    User home directory = C:\Documents and Settings\xxxFinalizer, called close()
    Finalizer, called closeInternal(true)
    network: Loading user-defined proxy configuration ...
    network: Done.
    network: Loading proxy configuration from Internet Explorer ...
    network:     Auto config URL: http://proxy.xxx.com/pac/proxy.pac
    network: Done.
    network: Loading auto proxy configuration ...
    network: Downloading auto proxy file from http://proxy.xxx.com/pac/proxy.pac
    network: Done.
    network: Proxy Configuration: Automatic Proxy Configuration
         URL: http://proxy.xxx.com/pac/proxy.pac
    basic: Registered modality listener
    liveconnect: Invoking JS method: document
    liveconnect: Invoking JS method: URL
    basic: Referencing classloader: sun.plugin.ClassLoaderInfo@1efb836, refcount=1
    Exception in thread "Thread-2" java.lang.ClassCastException: sun.net.ProgressMonitor
         at sun.plugin.util.GrayBoxPainter.beginPainting(Unknown Source)
         at sun.plugin.AppletViewer.initApplet(Unknown Source)
         at sun.plugin.AppletViewer.appletInit(Unknown Source)
         at sun.plugin.viewer.LifeCycleManager.initAppletPanel(Unknown Source)
         at sun.plugin.viewer.IExplorerPluginObject$Initer.run(Unknown Source)
    Applet console output when deployment.properties is placed on http server:
    Java Plug-in 1.5.0_06
    Using JRE version 1.5.0_06 Java HotSpot(TM) Client VM
    User home directory = C:\Documents and Settings\xxx
    network: Loading user-defined proxy configuration ...
    network: Done.
    network: Loading proxy configuration from Internet Explorer ...
    network:     Auto config URL: http://proxy.xxx.com/pac/proxy.pac
    network: Done.
    network: Loading auto proxy configuration ...
    network: Downloading auto proxy file from http://proxy.xxx.com/pac/proxy.pac
    network: Done.
    network: Proxy Configuration: Automatic Proxy Configuration
         URL: http://proxy.xxx.com/pac/proxy.pac
    basic: Cache is enabled
    basic: Location: C:\Documents and Settings\xxx\Application Data\Sun\Java\Deployment\cache\javapi\v1.0
    basic: Maximum size: unlimited
    basic: Compression level: 0
    c:   clear console window
    f:   finalize objects on finalization queue
    g:   garbage collect
    h:   display this help message
    l:   dump classloader list
    m:   print memory usage
    o:   trigger logging
    p:   reload proxy configuration
    q:   hide console
    r:   reload policy configuration
    s:   dump system and deployment properties
    t:   dump thread list
    v:   dump thread stack
    x:   clear classloader cache
    0-5: set trace level to <n>
    basic: Registered modality listener
    liveconnect: Invoking JS method: document
    liveconnect: Invoking JS method: URL
    trustStore is: C:\PROGRA~1\Java\JRE15~1.0_0\lib\security\jssecacerts
    trustStore type is : jks
    trustStore provider is :
    init truststore
    adding as trusted cert:
    X509KeyManager passed to SSLContext.init():  need an X509ExtendedKeyManager for SSLEngine use
    trigger seeding of SecureRandom
    done seeding SecureRandom
    basic: Referencing classloader: sun.plugin.ClassLoaderInfo@fc9944, refcount=1
    basic: Added progress listener: sun.plugin.util.GrayBoxPainter@1256ea2
    basic: Loading applet ...
    basic: Initializing applet ...
    basic: Starting applet ...
    # and so on ...I guess that the trusted jssecerts is not regarded until the system level deployment.properties has been downloaded.
    Whereas the deployment.properties can not be downloaded from my https server when the trusted certs are not known at this time.
    Or any other presumptions?
    Maybe it helped you ;-)

    I did something very similar. I am using jre 1.5.0_01.
    And it seems to work!
    The deployment.config is:
    deployment.system.config=file:/c:/jws/deployment.properties
    deployment.system.config.mandatory=true
    and the deployment.properties is (at the location above):
    deployment.system.cachedir=cache
    To load the cache I start javaws as follows:
    javaws -import -system -codebase file:/c:/cd file:/c:/cd/notepad.jnlp
    This results in creating the cache in
    file:/c:/jws//cache
    To start the app I did:
    javaws -system http://java.sun.com/products/javawebstart/apps/notepad.jnlp
    The -system seems to be neccessary but I am not quite sure. If it is omitted
    the app also starts, but javaws stores just the jnlp in the default user cache!

  • Java system error: Exception in method processFunction in BEX Broadcaster

    Hi All,
    We are trying to broadcast a BI7 Webtemplate with our enterprise portal. While clicking on "Create New setting " iam getting the error " Java system error: Exception in method processFunction ".
    Detailed error description is
    *Diagnosis
    An error occurred in the BI components on the SAP J2EE Engine.
    System Response
    Procedure
    Contact your system administrator to have the error analyzed in detail.
    Procedure for System Administration
    Start the Visual Administrator, log on to the SAP J2EE Engine and choose "<J2EE_SID>" ->"Server" -> "Services" -> "Log Viewer".
    The file "defaultTrace.trc" includes detailed information about the error that occurred. In Windows, you can find this file in the Log Viewer under "Cluster <computer name>" -> "Server <server number>" -> "<drive>:\usr\sap\<SID>\JC<INSTANCE>\j2ee\cluster\server<NUMBER>\log". ". In Unix, the file is located under "/usr/sap/<SID>/JC<INSTANCE>/j2ee/cluster/server<NUMBER>/log".
    If the file does not include enough detail about the error, you can increase the log level to obtain more information. To do this, choose "<J2EE_SID>" -> "Server" -> "Services" -> "Log Configurator". On the "Locations" tab page, choose "com" -> "sap" -> "ip" -> "bi" -> "webapplications". Using the selection list on the right side of the screen, you can increase the log level, whereby "DEBUG" represents the log level with the most information. You can save your settings by choosing the "Save" icon. The change to the log level is active immediately. Once you have successfully analyzed the error, you should set the log level back to its default value using the appropriate pushbutton; continuous writing to the log file negatively affects the overall performance of the system.
      Notification Number RSBOLAP 018  *
    Please let us know how to proceed

    Hi,
    This is a configuration issue. All components on the J2EE stack have to
    be on the same SPS level. Please make sure of this as a first step.
    For special requirements of BI with regards SPS levels please see SAP
    Notes 873996 and 1013369.
    Please run the latest version of the support desk tool as per SAP note
    937697 and ensure that there is no error and then check for the issue
    again.
    Otherwise, I suggest you open a BW-BEX-ET-BC msg with SAP.
    Rgds,
    Colum

Maybe you are looking for