Error 1335 When Installing Compact RIO Module Software 2.1.4 From Hard Drive

[Mohoyt]

I’m having issues with the installation of the CompactRIO Module Software 2.1.4.

Initially, problems were occurring when trying to communicate with the device, as it was denying access to it from the Development PC. Various things were tried such as adding a ‘*’ to the fields and making sure 'Allow' was selected in the communication properties on LabView RT. This didn't seem to work. A post relating to our problem is here: http://forums.ni.com/ni/board/message?board.id=170&message.id=269809&query.id=18752#M269809

As none of this was working, we decided to format the disk on the Compact RIO and reinstall the software to it. The software downloaded from Ni.com was the CompactRIO Module Software version 2.1.4 (dated May 2007). This file was unzipped using WinZIP 9.0 (on a PC running Windows XP Pro SP2 5.1.2600) and then transferred with a USB stick to the Development PC.

We attempted to install the file on the Development PC (running Windows 2000 SP3 5.00.2195) by running setup.exe. This started normally, but then proceeded to come up with an error message saying: ‘Error 1335. The cabinet file ‘Cabs.w1.cab’ required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.’

Attached are screen shots of the error message that appears.

As a result of this error, the installation could not be continued and the module software was not installed.

What is going wrong with the installation and how can I go about sorting it out?

Thanks very much,

Moses

RT target cRIO-9012, NI-RIO 2.1.3, LV 8.2, RT 8.2, FPGA 8.2, host ip 150.150.10.15, cRIO IP 150.150.10.4

Message Edited by Mohoyt on 09-10-2007 04:03 AM

[TheWay]

Hi Moses,

Can you transfer all the files from the USB drive to the development PC and locally running the setup.exe file?  I am assuming that you ran setup.exe from the USB drive (while it was connected to the dev PC).  I've heard that error sometimes occurs when running the setup from a remote source.

Let me know if that works!

Way S. 

[Mohoyt]

Way S.,

When I was trying to install the module software I had already copied the complete unzipped file to the development PC, so it was running locally when I encountered the error.

It must be something else causing the problem then...

Thanks for the help so far,

Moses

[TheWay]

Hi Moses,

It sounds like the installation files were somehow corrupted during the transfer to the dev PC.  Can you try running setup.exe on the PC you downloaded the file from? If it doesn't work, then you'll need to download the file again from the NI website (as it is corrupt).

If that works, then the problem lies between the file transfer from that PC to the dev PC (and not the downloaded file itself).  You might want to try a different way of transferring the file to the dev PC (eg. over the network, burning a CD) instead of using the USB drive.

Here is a post of someone who had the same error and it seems it was a faulty CD drive in his case:

http://forums.ni.com/ni/board/message?board.id=170&message.id=46258&requireLogin=False

Let me know if you have any questions.

Way

[Mohoyt]

Way,

Due to admin issues, I can't install the Module Software on the original PC at the moment, so I'll have to wait till Monday when I might be able to do it. Meanwhile I will try what I can and see what happens....

Thanks for the help so far,

Moses

[Mohoyt]

Way,

Thanks for the help overall, I finally worked it out. The problem was initially present in the unzipping of the original archive that had been downloaded from the NI.com website. When I had previously unzipped it, I had done so to a network drive which for some reason stopped autorun.inf and autorun.exe from functioning properly and so when I tried to install it on the Dev PC I got the aforementioned error. To overcome this problem I unzipped it to a local drive and (surprise!) there were no faults, so when installing the actual software, no errors appeared and it was installed correctly.

This however was not the only problem, the version that had now been installed did not want to co-operate with the RIO at all, and came up with various software errors in addition to not having all of the available software modules for the RIO available to install. The solution was then to install the newest RIO software, which is very badly labelled on the NI.com website by the way (its packaged as RIO software, so if you're looking explicitly for CRIO software you've got no chance of finding it). The newest version, 2.3 (Aug 07) as opposed to the 2.1.4 (May 07) that I was previously trying, worked fine and I was able to get all the software modules installed. So for now the problem is solved!

Thanks again for all the help.

Cheers,

Moses