10-02-2020 11:30 AM
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
Solved! Go to Solution.
10-04-2020 10:09 AM
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?
10-04-2020 10:54 AM
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.
10-05-2020 01:26 PM
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...
10-07-2020 08:28 AM
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.