NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Deployment log

When I want to build a deployment package, I have this in the log window :

 

Warning: This problem will cause an error when building a deployable image or an installer. The following file(s) were not found:

DLL_AFDX.prj in step 'Init AFDX Board', sequence 'Init AFDX', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\SvTB Tools\AFDX Tool.seq'

DLL_AFDX.c in step 'Init AFDX Board', sequence 'Init AFDX', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\SvTB Tools\AFDX Tool.seq'

 

In my AFDX Tool.seq I call a function within a DLL (DLL_AFDX.DLL), the DLL_AFDX.DLL is in the workspace. I do not understand why TestStand deployer warns on DLL_AFDX.prj and DLL_AFDX.c. What can I do to remove this warning ?

 

Thanks. 

 

0 Kudos
Message 1 of 7
(3,563 Views)

Hi sfl,

 

How do you call your dll? Do you use a relative path or an absolute one?

Could you attach us a small example which reproduce your issue?

Best Regards.

Romain D.
National Instruments France

0 Kudos
Message 2 of 7
(3,534 Views)

I use relative path.

 

I notice that I have no problem with an other DLL. The DLL with wich I have a problem is a DLL wich includes an other DLL (labwindows). 

0 Kudos
Message 3 of 7
(3,522 Views)

sfi,

 

Can you check if "source code files" has been specified for the step, which calls DLL_AFDX.DLL.

The warning can be removed by either providing the files specified in the step or clearing out the "Source File" and the "CVI Project"specified in the step.

 

Regards

Anand Jain

National Instruments

Message Edited by Anand Jain on 02-26-2010 11:50 AM
0 Kudos
Message 4 of 7
(3,509 Views)

Could you please tell me how can I check if "source code files" has been specified ? I do not want to provide the files specified but how can I clear out the "Source File" and the "CVI Project" in the step ?

 

Thanks a lot. 

0 Kudos
Message 5 of 7
(3,492 Views)

Sfl,

Depending on the version of TS you are using,  you might have to refer to different documents.

In TS 4.1.1 or earlier - please refer to section - "Source Code Buttons" in page 2-3 of the  "UsingLabWindowsCVIwithTestStand.pdf"

In TS 4.2 or later - please refer to section - "Source Code Buttons" in page 11-3 of the "UsingLabVIEWLabWindowsCVIwithTestStand.pdf" 

 

Regards

Anand Jain 

National Instruments

Message Edited by Anand Jain on 03-02-2010 01:32 AM
0 Kudos
Message 6 of 7
(3,478 Views)

Ok, thansk a lot, the warnings have disapeared.

 

Nevertheless, I have another type of warning to resolve :

 

Warning: You may need to add any sequence file(s) referenced by the following expression(s):

"reportgen_" + Parameters.ReportOptions.Format + ".seq" in step 'Initialize the On-The-Fly Report Generator Object', sequence 'Configure Post Result Callbacks', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Cfg\TestStandModels\ModelSupport.seq'

"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'SequenceFilePostResultListEntry', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'ProcessModelPostResultListEntry', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Set ReportOptions based on ReportStyle', sequence 'Get Report Options', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Footer', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Header', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Body (Sequence)', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Get Report based on ReportStyle', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Set Report Disabled Message', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test PEPDC', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\Product\Image\target\Product\Model_A400M.seq'

"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'SequenceFilePostResultListEntry', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"reportgen_" + RunState.Root.Locals.ReportOptions.Format + ".seq" in step 'Process Step Result', sequence 'ProcessModelPostResultListEntry', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Set ReportOptions based on ReportStyle', sequence 'Get Report Options', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Footer', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Header', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Get Report Body (Sequence)', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.ReportStyle + ".seq" in step 'Get Report based on ReportStyle', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"ReportGen_" + Parameters.ReportOptions.Format + ".seq" in step 'Set Report Disabled Message', sequence 'TestReport', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

RunState.ProcessModelClient in step 'MainSequence Callback', sequence 'Test PEPDC', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Model_A400M.seq'

"reportgen_" + Parameters.ReportOptions.Format + ".seq" in step 'Initialize the On-The-Fly Report Generator Object', sequence 'Configure Post Result Callbacks', sequence file 'H:\Sere\07 - Test tools\11 - TestStand\03 - Sources\Product\Cfg\TestStandModels\ModelSupport.seq'

--------------------------------------- 

 

What can I do for them ?

 

Regards. 

0 Kudos
Message 7 of 7
(3,472 Views)