LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Web Service will not work on Windows 10 latest update. Worked fine a dew months ago. Using port 8002. Any ideas?

Solved!
Go to solution

We have an application we deploy to the production floor.  It utilizes a web service.  It installs, it just does not communicate.  The Firewall is not even trying to block it.  You know how when the initial run of the application pops up the firewall utility to allow the access?  It does not do this.  We all so have ESet.  The fire wall is off.  Like I said in the subject, this installer worked fine a few months ago.  Any ideas would be greatly appreciated!

 

Thanks,

Rich

0 Kudos
Message 1 of 5
(1,828 Views)

There's several ways to interpret this.  Let's first try to get the problem statement clarified so it's easier to help troubleshoot.

 

If I'm making the right guess, "update" here means you freshly installed the most recent build of Win10 on a machine.  With the freshly formatted machine, you're trying to use an installer you've successfully used in the past.

 

Is that correct?

 

Or, was this working on the machine prior to updates and now it is no longer working.  You're attempting to fix the problem by running the installer again?

0 Kudos
Message 2 of 5
(1,777 Views)

On a fresh Windows install it will not work. 

The installer does it thing with no complaints.   The webservice is not accessible.  

If I update a previously installed version of the application with this current versions of the application it works fine.

 

Upto a few months ago the same installer worked the application worked the web service worked on latest updated version of Windows. 

 

0 Kudos
Message 3 of 5
(1,768 Views)

Another bit of information.  The startup vi is not starting.  I used the old school technique of adding dialog box stating the "Webservice Starting."  It does not pop up... 

0 Kudos
Message 4 of 5
(1,746 Views)
Solution
Accepted by topic author rwelch

Go to the bottom of it.  It was the FTDI drivers in my application.  They were installed, however until a device is enumerated they were not fully installed.  Therefore the Webservice Startup Vi would not even load into memory.  The application engine would run without a complaint.  Thanks to all.

0 Kudos
Message 5 of 5
(1,727 Views)