I’m trying to import a method package that has file dependencies set up, with recovery option and the import original Hamilton files option is enabled. The import completes successfully but looking at the import logfile the file dependency is skipped. I confirmed that the file location for the file dependency isn’t created either.
Any thoughts on what went wrong? I’m suspecting a file folder creation issue, but wanted a second opinion before I go to my IT.
Thanks for the suggestion, Gareth! A log file is created in the Hamilton\LogFiles directory for every import and export. Sort by date modified and look for a prefix “Import_of_[Method Name]…”.
You can upload to the file to the shared temp folder here.
Did a deeper dive and it turns out the package files I was given did not have the “export original Hamilton files” option selected. That’s why when I tried imported with the option checked or not I was seeing the same result.
Other background information: this a completely new computer, so it was really apparent when those files were missing/not imported.
For future people with this issue, make sure that the option to export original Hamilton files is selected and the import option is also selected when importing methods into a brand new computer.
Glad you sorted it. Don’t forget that some of the files may have been installed with installers that also add registry components etc, and won’t work on the new computer until you run the installers on the new system.
Be aware that when using the option to export/import original Hamilton files, this will allow for read-only VENUS files as well as configuration files to be overwritten on the target installation. These files are typically VENUS-version specific, so if you are transferring methods after an upgrade, or from STAR to VANTAGE, this can cross-contaminate the target installation with files not intended for that VENUS build. In these cases, this can cause issues which may require a software repair.
In instances where source and target installation between export/import are the same version of VENUS or running replicate systems, this is not really an issue.
Just FYI. This comes up as a point of confusion sometimes and just wanted to provide some additional clarification.
Thanks for letting me know the caveats!
For the read-only VENUS files, could you give some examples? I was given the option to overwrite library files, labware files, and dependency files that I recalled.
Noted! I run the installers before importing methods on new computers! I realize that might not be a thing everyone thinks to do when setting up a new computer.
Default library and labware files (the ones that install with VENUS) are the most prominent examples. Most of the time this isn’t an issue, but there are some libraries/HSL files that were written or updated for a particular version of VENUS (smart steps, power steps, method editor supporting files etc). In some instances, cross contamination of dependencies for such libraries can cause syntax issues or step errors that otherwise wouldn’t occur normally.
Overwriting default labware files is generally less of a concern.
Thanks for the clarification!