Jump to content
News about the LabVIEW Wiki! Read more... ×
lvb

LabVIEW 2018 SP1 Released

Recommended Posts

I had a hard time downloading this, but it could be an IT issue on my side.  The download would stall, and I'd pause, then resume to get it going again.  After installing with default settings, I launched it and got an error "error unable to open resource files".  I'll be performing a full uninstall and reinstall.  It could be an issue on my end or an issue with the release.  I probably should have tested this in a VM first...

EDIT: Uninstall and Reinstall fixed it, not sure if that means there is an issue with upgrade or just me.

  • Like 1

Share this post


Link to post
Share on other sites

Did they fix your issue here?

https://forums.ni.com/t5/LabVIEW/TDMS-Excel-Add-in-18-Crashes-Excel-2013/td-p/3796275

I ended up just removing all of 2018 and reinstalling the driver set because I couldn't make that stupid plugin revert properly (in part because I had NIPM installed)

Edited by smithd

Share this post


Link to post
Share on other sites

Thanks for reminding me.  I just tested it and yes the TDM Importer Version 18.0.1.7167 (as reported in Excel) now imports my TDMS files without crashing.  That was a major pain because I'd uninstall TDM 18.0.0, reinstall TDM 17.x, but in the uninstall some other dependencies were removed which then needed to be reinstalled...which by default installed 18.0.0 again.  Oh and it looks like the download page to this add-on was updated yesterday to the new version too.  Other fixes in SP1 I've heard are related to VIMs but am unaware of the details.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Yeah VIMs are pretty buggy although I'm still back in 17.5. For one particular set (using classes of course) I've had to just convert every instance to static manually, else the exe won't compile. Fortunately I just use them as helpers at the very top level, and drjd's json ones haven't caused any issues.

Share this post


Link to post
Share on other sites

I shot my installation too! Be sure to create a backup or test it in a VM!
=> Really NI?!  :-(

Edited by Cloedu72

Share this post


Link to post
Share on other sites

Can you describe the issue you had after your upgraded?  Maybe we can help NI in finding the issue.

Share this post


Link to post
Share on other sites

I got the same error as you (error unable to open resource files).
I did the installation as an upgrade over the existing installation. After that the licensing and LabVIEW didn't work anymore! I then switched to a previous snapshot in my VM and could continue working.

Share this post


Link to post
Share on other sites

Link is now dead, they got the feedback I guess.

Well, the feedback that this particular install is bad.

Not the feedback of "maybe you should test these installers before uploading them" ?

Edited by smithd
  • Like 1

Share this post


Link to post
Share on other sites

It would be a communication practice to publish the problem. Just turning off the link is a bit too easy! :oops:

Share this post


Link to post
Share on other sites

Yeah there are several reasons why NI's mistake here isn't as bad as Microsoft's.  LabVIEW 2018 SP1 wasn't automatically pushed.  An uninstall and reinstall fixed the issue, doing something like that in Windows is a lot more difficult.  And NI's issue isn't deleting data (that I know of).  Still crappy and NI is clearly looking into it.  That being said I have 2018 SP1 running on a couple machines already just fine. 

But yeah having the 2017 SP1 example doesn't instill much confidence.  Fool me once kind of situation here.  That being said I don't mind being a test subject when it comes to these things.  I updated as soon as I could and took the risk on a machine I didn't care too much about.

Share this post


Link to post
Share on other sites

So if it wasn't clear, this release had issues.  It wasn't intended to be the final LabVIEW 2018 SP1 and was an version between SP0 and SP1 for testing.  It was unintentionally released to the public and wasn't intended for the general public to use, and likely won't activate.  The release was pulled and if you did download it you are better off not using it until the actual SP1 release.  On top of not being intended for an actual release, and not activating, it also has a bug with upgrading from 2018 f2 to 2018 SP1 which is being addressed for the actual SP1 release.

  • Like 1

Share this post


Link to post
Share on other sites

Wow, quite a bit of activity on this “release”.  Glad some others were able to notify about issues.  I also got word from NI that this release shouldn’t be used as it was accidentally published to the official downloads page.

Share this post


Link to post
Share on other sites

It would be nice to have a changelog accessible before having to download the installer first.... All I see is a critical patch link, but this doesn't look like a changelog to me at all. Have I missed something?

Share this post


Link to post
Share on other sites

There is also already an SP1 f1 installer out....(3rd of December is the release date) Here: http://www.ni.com/download/labview-development-system-2018-sp1/7889/en/

So is that an update to SP1 that needs to be applied after SP1, or is it included in the "new" (hopefully) SP1...or?

Anyone who has been brave (or virtual) enough to install these already?😉

Share this post


Link to post
Share on other sites

Still broken, don't install

 

To be clear I used the standalone installer for 32 bit since that took 3 minutes to download and the web installer would have taken 28 hours. 

Edited by smithd

Share this post


Link to post
Share on other sites
20 hours ago, BramJ said:

Looks like it is actually released now:

http://www.ni.com/download/labview-development-system-2018-sp1/7843/en/

http://www.ni.com/download/labview-development-system-2018-sp1/7849/en/

 

I see the release data is still 11/14/18, hmm...  

It now shows "Release date: 12-03-2018"

Share this post


Link to post
Share on other sites

Also, NXG 3.0 is available through NI Package Manager.

Share this post


Link to post
Share on other sites

Just compared the MD5 checksums of the 32 and 64bit 2018 SP1 I downloaded yesterday, they don't match what is listed on the download page now (with the new release date)

Also, the buildInfo.txt content of both the 32 and 64bit is exactly the same as the version I downloaded last month

 

(I must say, I have been running the 2018 SP1 the last weeks, have not run into any problems)

Edited by BramJ

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use.