importing from a newer version of NISE to an older

[taft220]

Anybody know a way to export from NISE 3.0 to NISE 2.0.1?  I mean its just 'routes' after all right - there's got to be a way besides having to manually input the routes into the older one - right?  All I know is that v2.0 only accepts XML files so when I EXPORT from v3.0, the older version throws an error stating that the import failed and blames it on me using an evaulation version of the deployment engine -- which is not the case.  These are two separate hardware setups, the older hardware just happens to have v2.0 from a few years ago. 

Any ideas?

Thanks

[Paul-D]

Hello Taft, this is Paul with Applications Engineering at NI

Have you already tried the steps outlined in this KB?

http://digital.ni.com/public.nsf/allkb/56F406007D4FB191862574710069A480

I know it is for 3.0 to 2.1, but the same process should work for 2.0.1 also.

Also, from this previous forum post, you will need to verify that your IVI configurations match on your deployment and target machine once you are able to perform that import.

http://forums.ni.com/t5/Switch-Hardware-and-Software/Switch-Executive-2-0-and-Deployment-3-0/m-p/914...

Also, if you need some more importing/exporting, check out the help files listed at Programs>>National Instruments>>NI Switch Executive>>Documentation

Let us know how this works out for you.

Thanks,

Paul

[EricS.]

Hello taft,

The information the the knowledgbase article Paul mentioned is valid for NISE 2.1, however it is not compatible with NISE 2.0.1.   The Excel spreadsheets inlcluded with NISE 2.1 and NISE 3.0 use the NI Switch Executive Configuration API, which will not be present on your computer that only has NISE 2.0.1.

The reason the normal import fails and gives that error is because the NISE 3.0 XML export has several more attribute IDs that have been added over the years.  NISE 2.0.1 does not know how to interpret these new attribute IDs and is not able to import the configuration file.

The easiest method to import your NISE 3.0 configuration to NISE 2.0.1 is actually to uninstall NISE 3.0, and then install NISE 2.0.1 on the same computer.  The MAX database that contains your NISE virtual device configuration files will remail intact.  When you install NISE 2.0.1 it will look to the database and read the configuration settings that it recognises.  There were a few new options in NISE 3.0 that will not be available in NISE 2.0.1, but all of your routes, aliases, exclusions, and hardwires will be properly converted.

If you do not want to do this process yourself, send your exported NISE 3.0 configuration file to Justin, the applications engineer here at NI who I believe you have been working with through email (I saw he received an email about NISE file conversion the same day you posted this question, so I assume it is you as well).  We will be able to convert it to NISE 2.0.1 and send back a 2.0.1 configuraiton file.