uday, EULA files are not installable by design, and NIPM should be copying the files to the EULAs directory when software is installed.
The purpose of fixing the feed in the EULAs directory was to allow NIPM to see the eula-ni-standard file so that you can retry the original LabVIEW publishing operation that previously failed. If you are still unable to publish, you should get us a new copy of the log files.
Hi Scott Richardson, the issue still persists after the changes. Not able to publish when Include all dependencies in Systemlink feed option checked. Unchecking this works and publishes the package to feed without any error.
Attaching the log files for reference.
Let me know if you need further information.
uday, I will try to reproduce your issue here and let you know how it goes.
Just curious, are you able to build a feed using the project Package build specification, without publishing to SystemLink, and are you able to manually upload the feed to the named repository using the SystemLink server web interface? Is that a viable workaround until we can figure out the underlying cause of the error?
Hi Scott, iam able to build package, manual publish works without any issue. In automatic:
uday, can you share the full text of the Details section of the Build Error prompt in your first image?
Hi Scott, please find the error details:
Click the link below to visit the Application Builder support page. Use the following information as a reference:
Error 1 occurred at NIPKG.lvlib:NIPKG.lvclass:Create Package Installer Core.vi -> NIPKG.lvlib:NIPKG.lvclass:Create Package Installer.vi
LabVIEW: (Hex 0x1) An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
uday, I could not reproduce your specific error, however, in my tests with the latest SystemLink and your LabVIEW version and newer, I am seeing unacceptable delays to publish packages to SystemLink where the LabVIEW build process appears to be hung but eventually finishes. It appears that LabVIEW is trying to determine what packages are in the repository in SystemLink and many of the calls to do this are timing out, so even though my package I wanted to upload was very small, it took up to an hour to publish.
FWIW, I opened a bug with an ID of 2350808 internally to track what I was seeing for both LabVIEW and SystemLink to debug. Once I know more, I can post back.
Unfortunately at this point, I do not have any LabVIEW specific workaround that you can do other than to manually upload the packages using SystemLink web interface, or look into automation for utility program to upload files from a directory to a specific SystemLink feed.