Deployment Utility - log file errors/warnings not clear

[Rafi2003]

Hi,

I'm doing my first deployment and have few questions:

1) I tried to deploy ONLY the TS user directories. I checked the 'Deploy Files in TestStand User Directories' option and did not check 'Install TestStand Engine' since I deploy it into a system with TS3.0+CVI7.0 software(same as the source).

The process was successful by I get the following warnings in the log file.

Starting Log.
Building...
5:47 PM
An installer is being created.
The installer is finished
The build process is done.
5:48 PM
---------------------------------------
Warning: You may need to add any sequence files referenced by the following expressions:
"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'SequenceFilePostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'ProcessModelPostResultListEntry', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Footer', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Header', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Body (Sequence)', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Set Report Disabled Message', sequence 'TestReport', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Single Pass', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test UUTs', sequence file 'C:\Program Files\National Instruments\TestStand 3.0\Components\User\Models\TELRAD_SequentialModel.seq'
+++++++++++++++++++++++++++++++++++++++


What does it mean? What to do about it?

2) The utility does not include the cfg/TypePalettes where I have a my own file.
Is there a reason to it? Do I need to include it manually?

3) When I included workspace in the utility I get the following errors:

Starting Log.
Processing Workspace...
Done processing workspace file
+++++++++++++++++++++++++++++++++++++++
Processing Workspace...
Done processing workspace file
Building...
6:08 PM
Error could not open LabVIEW
Distributing VIs requires the LabVIEW Development System
Class not registered
in TestStand - Get LV Reference.vi->TestStand - Package VIs.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 process is done.
6:08 PM
Error Code:-2147221164
Class not registered
in TestStand - Get LV Reference.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
+++++++++++++++++++++++++++++++++++++++

In order to eliminate the problem source I un-checked the files presented by the 'Analyze Source Files' until all of them are un-checked. Even in that case I get the error message.

What does the message mean?
What to do about it?
I don't use any LV in my system!!!!!

Thanks and my apology for the long message

Rafi

[RajivG]

Hi Rafi,

Here are the answers for your questions:

Issue 1: Warning message during deployment
Reason: You see that warning because TestStand cannot identify the sequence that the expression might be calling beforehand, which is known during run-time. So dont worry about this warning. It's for your information.

Issue 2: Including the cfg/TypePalettes
Solution: You need to include the cfg manually and the Typepallettes are included by the utility.

Issue 3: Error "could not open LabVIEW"
Solution: The deployment utility is made in part with LabVIEW files. The error lists the files that are giving the error. It looks like you are using a vi in your sequence, which might be calling LV on the development m/c to compile that vi. If you use a vi in the sequence then you need LabVIEW.

I hope it helps,
Rajiv G

[Rafi2003]

Hello Rajiv and thanks for answering

Issue 3 - please note again what I wrote regarding it:

"In order to eliminate the problem source I un-checked the files presented by the 'Analyze Source Files' until all of them are un-checked. Even in that case I get the error message."

So, not only that I don't use any vi (never did), I un-checked all the files. I'm doing a deployment with no files!! It still gives me the error?!!

You mentioned in your answer that the deployment utility is made partially with LV. Could that be a reason? (I would doubt that...).

Could you point out in the error message which are the files it complains about ?

"Error could not open LabVIEW
Distributing VIs requires the LabVIEW Development System
Class not registered
in TestStand - Get LV Reference.vi->TestStand - Package VIs.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 process is done.
6:08 PM
Error Code:-2147221164
Class not registered
in TestStand - Get LV Reference.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi"

Thanks Again

Rafi

[SAS]

Hi Rafi,

Some time back when we tried deployment, we also faced this error (Error 3). Later we found out, that it was due to Station Options-->User Manager-->Check User Privileges was unchecked. When we deploy it with the option checked, we didn’t face the error. Now we could able to deploy without issues. But then our system has LV installed in it.

Thanks
Sasi

[Rick_Francis]

Hi Rafi,

On #1 the warnings appear whenever you have an expression that specifies a sequence file because many expressions are not valid until runtime, you can ignore it as long as ALL sequences that expression may evaluate to are included in the Workspace.

>2) The utility does not include the cfg/TypePalettes where I have a my own file.
>Is there a reason to it? Do I need to include it manually?

No it does not include it because it is not needed unless you plan to edit on the deployed sequence (generally not recommended). If you add a custom type to a sequence the sequence file will have a copy of the type. You can include the types palettes manually in the workspace if desired.

>3) When I included workspace in the utility I get the following errors:
>What does the message mean?

The deployment utility thinks you have a VI to deploy, it is trying to load LabVIEW and failing because LabVIEW is not installed.

>What to do about it? I don't use any LV in my system!!!!!

Somewhere there is a .vi or .llb in the system. Find the VI(s) and uncheck them. I did find a bug that the deployment utility caches the flag indicating if a VI is present, but it is easily worked around: Save a tsd file, Press the New button and then reload the tsd.

-Rick Francis

[Rafi2003]

Thank you Francis

Still, how can you explain it if I unchecked all files before the deployment?

Thanks
Rafi

[RajivG]

Hi Rafi,

Can you try removing the steps that call that VI. After you remove the step from the sequence that is calling VI maybe it might solve the problem. Let me know what you find.

Rajiv

[Rafi2003]

Remove from where?

Nothing is selected for deployment (when you use the 'analyze files' I unchecked everything!!!). If I knew where those vi steps are, I would have deleted them myself.

This is exactly my problem. I don't know were vi steps are coming from....

Thanks for any idea

Rafi

[RajivG]

Hello Rafi,

I am not very sure what might be happening on your computer, but would suggest the following things:

1) Try what Sasi suggested earlier regarding the user previleges.
2) Try looking at the adapter configuration: Configure->Adpaters->LabVIEW->Configure->LabVIEW Run-Time Engine.
3) Try deploying some example program or any other simple sequence. If that does not work then try running a sequence with no LabVIEW adapters.
4) Try creating a new workspace and include the sequence freshly. If that does not work, try copy-pasting steps from the sequence to a new sequence and deploying at each step to find the source of problem.
5) Try deploying it on a different computer. If you dont have a multi-license, I would suggest you post your sequence file with the associated file for review by someone else.

I guess these are some of the things you could try and I can think of. If it looks like a problem on your computer only then maybe you can repair TestStand (the risk is that you might loose any changes you made to the shipped files - if any).

I hope it helps,
Rajiv G

[Rick_Francis]

---

@Rafi2003 wrote:
Thank you Francis

Still, how can you explain it if I unchecked all files before the deployment?

Thanks
Rafi

---

Rafi,

Sorry I hadn't replied earlier but I've been out sick. There is a bug with the deployment utility when it comes to keeping track of if a VI is present or not. The bug can be worked around using the following steps:

1 Uncheck ALL VIs present (you can use Windows Search function to look for *.vi and *.llb to find all possible VIs).
2 Save the deployment to test.tsd
3 Press the New button to clear the currently loaded file
4 Load test.tsd

At this point you should be able to build without the error. If you still see the problem I can build a version of the Deployment Utility that has the bug fixed, however it would be rather large download (8MB).

-Rick Francis