12-09-2021 06:52 AM
I am working on webservices that run with the NI web server. I noticed that updating a webservice with NIPM mostly fails with some incomprehensible error. I can prevent the error only by (manually) disabling the NI webserver.
Is there a way that this error can be prevented without having to first manually disable the NI web server?
12-11-2021 10:32 AM
Aartjan, I would expect that NI Web Server should be able to shutdown any services prior to installing, but that may not be working in youir case. More details are needed for others to give any guidance on debugging the issue.
12-20-2021 12:36 PM
Version NIPM: 21.3.0
The error:
An error occurred while installing a package: ricardo-office (1.0.0-0)
Additional error information:
The executable returned error '-67033' after running the custom execute command 'path='"\\?\C:\WINDOWS\SysWOW64\cmd.exe"', options='/c ""%ni-paths-NISHAREDDIR%\LabVIEW Run-Time\2020\LVWS\NIWebServicePublisher.bat" /c "%ProgramData%\ricardo.lvws""''.
This error occurs during installation of the webservice package.
12-21-2021 11:27 AM
aartjan, I am not familiar with LabVIEW Web Services, but I believe the error that you are seeing is "LabVIEW Web Services: A Web service already exists with the input name", see https://zone.ni.com/reference/en-XX/help/371361R-01/lverror/web_services_error_codes/.
If you are upgrading something it appears that "input name" already exist so the custom execute is erroring and hence the package installation fails. If this error is expected, you will need to handle the error in your script call or you will need to update the package with the custom execute to ignore errors.
I am not sure how you are creating your package,
12-22-2021 04:01 AM - edited 12-22-2021 04:06 AM
Great! That was already very helpful. I do have several other webservices running on that NI Web server. Now I am wondering what that "input name" is and if I can set a unique name. It was the first time I tried to install this particular webservice, so I cannot be the name of the webservice itself.
I forgot to mention that, this time, the issue is not resolved by disabling the NI web server. It won't install at all, even after a reboot.
Apparently the NI webserver is not the issue.
Feedback for NI: NIPM did not lead me to these error descriptions when it displayed the error. That would have been very helpful.
12-23-2021 10:15 AM
Glad you're able to move a little bit forward; at this point I assume that there is not anything to investigate regarding NIPM.
Regarding your feedback, unfortunately NIPM has no knowledge of error codes other than itself, so there is no way for it to redirect you to "third party" error codes help.
12-25-2021 04:37 AM
I continued developing and now the package installs without issue. Not a clue what changed.
12-25-2021 01:09 PM
Glad to hear that your package is now installing. Just a thought, if you are now ignoring the error from the custom execute, it might now be able to continue if and when the script fails.