TS 2010 Deployment Utility internal error code 97

[GreggRupp]

I am currently getting the following message and I am wondering what I might be missing or where to look to try to fix this. This is the first time using the TS2010 deployment. All of the users are transitioning from 4.2.1 and I am trying to get a deployment for all of their computers that are getting updated.

+++++++++++++++++++++++++++++++++++++++
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
12:18 PM
Internal error code 97 Updating File Links
Unknown System Error in TestStand - Check Linkages in Step.vi->TestStand - Check Linkages in SubSteps.vi->TestStand - Search Sequence and Fix Linkages.vi->Fix Linkages in Sequence Files - TestStand.vi->TestStand - Fix Linkages.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
An installer was not created due to an error
The build is finished
12:18 PM
Aborted
---------------------------------------
Warning: Absolute paths were found in the following substep(s):
Edit_OI_CN
---------------------------------------
Warning: The following dependencies were detected but not selected; you must decide if they should be included:
C:\Windows\system32\wininet.dll
C:\Windows\system32\urlmon.dll
C:\Windows\system32\iertutil.dll
+++++++++++++++++++++++++++++++++++++++

[Shawn_S.]

Hello,

Have you checked the suggestions at the following forum post?

http://forums.ni.com/t5/NI-Applications-Engineers/Internal-error-code-97-Updating-File-Links-in-Depl...

I would try some of the suggestions in that forum and let me know how it goes!

[RayFarmer]

Hi Shawn,

that link doesn't appear to work

[RayFarmer]

I would guess that you have included the DLL's or dependant DLL's as part of your Deployment.

You can use something like Dependany Walker to check want your DLL's require.

[Shawn_S.]

I'm sorry that the link did not work.  That is my mistake, as it was an internal forum.  I've attached the relevant information below:

      My first suggestion would be to try mass compiling all of the VIs with LabVIEW 2010.

      Other than that, I found one mention of this error occuring when the Sequence Context is not being passed correctly into a VI. I would expect this situation to present the error at edit time, but it's worth mentioning. The text I found is

      below:

      "The step that calls the VI may be passing the wrong sequence value.  Select the step and configure the input value for the "Sequence Control".  The value of the Sequence Context parameter needs to be "ThisContext".  Note that

      selecting the "default" input will use the default value of the VI control, which is normally a blank context."

If the mass compile does not work, let me know and we can investigate this further.

[Rick_Francis]

Gregg,

Here is a bit more information to help debugging:

This code is looking at the sequence files in the image directory TestStand - Check Linkages in SubSteps.vi get all the substeps of a user defined step type and TestStand - Check Linkages in Step.vi checks for absolute paths in the code modules of those substeps.  Error code 97 means a property or invoke node got a null reference.  I reviewed the code and I only see one place the error could be occurring, ultimately StepType.Getsubstep is returning a null reference for some substep.  

If I can get files to reproduce the error here I can find out exactly what is causing it.  Since I'm sure you don't want to post your entire system, but we can narrow it down.

First this error will only happen with a user defined step type, so I would make a test sequence that contains an instance of each user defined step type you have in your system and see if deploying the test sequence also produces the error.

If you have a large number of step types I would try to narrow it down by deleting half of the steps and saving the sequence to a new path.   If the new sequence still has the error you reduced the size by half.  If it doesn't the other half should have the error and you still reduced the size by half.   You can keep iterating until you have a reasonable number of step that reproduces the error.    At that point you could post that sequence and it's dependencies, and I will find the exact problem.

-Rick Francis

[GreggRupp]

We do not have any LabVIEW vi's in our program. We are using C# for our step types. I will work through these suggestions and try to rectify the problem. Thanks

[RayFarmer]

I believe the VI references are related to the Deployment Tool not to your Code Modules.

But you probably want to checkout the DLL references or related DLLs to those DLL's quoted in the error message.

[Manooch_H]

This issue is fixed in the TestStand 2010 f1 Patch. For details on all the issues fixed in the TestStand 2010 f1 Patch, please see the KnowledgeBase Article: TestStand 2010 f1 Patch Details

Thank you.