TestStand deployment utility crashes

[flaborde]

All right, thanks for all the details, we will look at this 🙂

[steve05ram360]

Roger that, thanks!

[steve05ram360]

TTT...

Any updates on this issue?

[Al.B]

Hi Steve,

I set up your files on a clean machine and noticed that your workspace statically includes the entire NIReport.llb.  I was not able to test the case of this being included since the paths are different on my test machine, but I was able to build successfully when I removed this folder from the workspace.  Are you seeing the same behavior if only the sequence file is included in the workspace?

[steve05ram360]

I had the bare minimum, then with the library included... same results both ways

[steve05ram360]

OK, I went back to try to figure out what is going on and re-created the class from scratch thinking it is something I am doing.  Apparently when building, it does not like the report class object to be within another class.  There was a reason for doing it this way and of course I do not recall what it was.  So, I believe I will have to find a new method for generating the report.

Attached is the last effort in trying to duplicate/fix the problem, new class object with the report object as part of the class and the new report.VI.  About as bare minimum as I can get it.  Still fails to build.

Can I ask that you try the attached testreport.zip files and let me know if it builds or not?  If it is OK then I'd have to assume there is an issue with this LabView install.

[Al.B]

Hi Steve,

I am able to build this successfully so it may be an install issue.  One thing we can try is to build these files into a source distribution in LabVIEW directly, and see if you still encounter problems.  In some cases LabVIEW will provide a more descriptive error.

[steve05ram360]

Ok thanks... I will try that next and report back when complete...

[steve05ram360]

Update:

I have another problem to toss out there that is probably not related...  When booting the system I get the "Please Wait" message for 30-40 minutes before I get the log in screen.  I have narrowed this problem down to the TestStand 2012 install after LV 2010 is installed.  I removed all software this morning, reloaded LV 2010 (stuck with it) and rebooted, no problems, no long delays before the login screen.  Load TestStand and the problem comes back.

Last week I did a quick app to collect data and discovered while setting up the target system for use that the installer I created was asking for the Feb 2013 NI Device Drivers disc during the build.  ...OK... ?  Found the disc, finished the installer and the target computer then had the long startup problem my dev comp had.  Soooo, I removed everything back off and installed 1 piece at a time, rebooted as needed and did not have a problem UNTIL after I installed the Feb 2013 driver disc, then the target had the slow bootup again.  Sooo... cleared out the Feb 2013 drivers and re-installed using the disc that came with LV 2010 (Aug 2010 NI Dev Driver disc).  Rebooted and NO long bootup... Yeah...

Sooo... since my dev comp had that problem I decided to take the same steps in an attempt to fix it's long bootup problem.  With TestStand and LabView un-installed, I started from scratch.  Loaded LV 2010 & all the supporting files to get back to where I was but with the Aug 2010 drivers and without TestStand.  Reboot once again, no problems... cool!  Next I load back in TestStand and reboot, problem returns, slow boot up.

So now I've reloaded all the software and I go back to the to the original problem of the TestStand deployment utility crashing when I use the report gen class object and that failure also is still there.

I already successfully deployed the TS Test Exec along with a dummy sequence file, what would be the suggested route to take to get the report VIs on the target computer?

thanks...

[freighTrain]

The boot up issue does seem unrelated. Starting a separate thread on it might be a good idea. But I would check the Event Viewer to see if there are any errors or events that have especially long boot times.