Publishing web service fail with error -67404 (LV2020)

[Olivier-JOURDAN]

Hi there,

I'm upgrading an application from LV2017 to LV2020 that has a web service.

I try to use the new NI Web server instead of the old Application Web Server but I got issues.

To do some tests, I try to build and install the weather Simulator that comes with the examples. Installing the EXE with package gives me the following error: 

Note that I also have a related problem when I start the Web Service from the LabVIEW project:

I'm working on a fresh install of Windows 10 Enterprise with only LV2020 32 bit installed.

Thank you in advance for any idea that could help me fix that issue.

[MarkBlack]

Hi Olivier, 

I quickly opened up the weather example and was able to build the exe, build the package, and install it locally without any errors. I didn't make any modifications to the project. I basically just built the various Build Specification and installed the resulting package. Are you doing anything different? 

[Olivier-JOURDAN]

Thank you, Mark, for getting an eye on this.

I did it exactly as you describe.

[Olivier-JOURDAN]

Updates:

- I tried a LabVIEW repair

- I deactivated the firewall

- I try 2 on 2 other computers with fresh LV install

... and I'm still having the same behavior 😞 

[JoshuaP]

You may need to run the NI Web Server Configuration utility and configure the web server before the example will work.

[Desruelle_luc]

Hi olivier 🙂

I opened up the weather example, under LV2020 EDI 20.0.1, and was able to build the exe and install it locally without any errors.

1) I didn't make any modifications to the project. (Web Services used the NI Web Server) -> ok

2) i updated the Weather Simulator (Server) specifications to used "Web Services : Application Web Server" (not the NI Web Server). I use the 8002 port.

Si je peux t'aider je suis dispo.

Téléphone moi si tu veux plus d'info 🙂

A+

Luc

[Olivier-JOURDAN]

Hello Joshua

@JoshuaP wrote:

You may need to run the NI Web Server Configuration utility and configure the web server before the example will work.

---

I have it running (I also tried different configs). Each time I got the same error.

Here is an animated gif to demonstrate the issue in the LV project -->

I had a screen sharing session with Luc, and I can give the following information on what's happening:

• NI Web Server is working on his machine (EXE and Development)
• Thanks to UAC dialogs that pop when launching EXE or starting webserver from the project, we think that the applications that publish the web services are not called
• We look into the differences between our machines.
  • Windows configuration is quite identical (UAC params, user permissions...) 
  • The real difference, IMO, is that
    • he has a lot more things installed compared to me (TestStand, SystemLink...)
    • I also have one thing he doesn't have: NI System Web Server 2020 SP1

We made almost every possible test we could with our knowledge of how NI products manage web services. We really need to have NI inputs on the 2 errors (-67404 and -67415) to figure out what's happening here.

Thank you in advance for your help.

Olivier

[Olivier-JOURDAN]

Update on my issue:

I installed the all new G Web Development Softaware and the following additional items NIPM offered me to install 

Now when I try to start the webservice through the lvproj I got the following dialog asking for administrator privilege 

and... a new error, the -67016 😞

[Olivier-JOURDAN · Accepted solution]

I finally got it to work.

I uninstalled all NI software and reinstall LabVIEW 2020 SP1 from NIPM keeping all the additional packages offered in the step following the LabVIEW stuff to install step. I'm used to unchecking the things I'm not using like database toolkit, report generation, and so on.

It seems that in this list something related to the web service is installed but it's far from being obvious...

[aartjan]

I wouldn't consider re-installing the complete development environment a solution..

I am also running into installation issues with a web server. I posted it in this thead. I have yet to solve it, but it did help me find the error explanations.